Nash Kaminski

I do not have a Teptron MOVE unit to test/debug this with. @t0mas is the only active contributor who does to my knowledge.

The behaviour you are seeing (characteristic values are written but the device does not respond) is also consistent with an invalid packet. One parameter of the protocol that is still...

@tomas is the only developer who I am aware has a Teptron Move unit. I can certainly try to help with protocol issues however I only have a series of...

Might be worth seeing if there is an actual or effective "no-op" or heartbeat command that you can send before the set position command to workaround this issue. Take a...

You would want to modify the line beginning with "cmd=" such that it reads: cmd="gatttool -t random -b %s --char-write-req -a %s -n %s" % (dest, p_handle, strdata) On November...

I do not have a MOVE unit, however I am aware of some previous issues related to MOVE connectivity that were thought to be a result of the MOVE unit...

Can you make sure that the move is the only BT device connected and post a packet capture / HCI snoop log resulting from sending one or more commands to...

I will take a look at it this weekend. Also, what is the 4 digit network PIN you used when you created this log? FYI if you want to see...

I had gotten sidetracked with a few other priorities. Will look at this tonight. - Nash On March 12, 2018 9:39:30 AM CDT, beanian wrote: >@nkaminski Did you get a...

OK so this still looks like CSRMesh traffic, which is good. Possibly the format of the payload is what has changed. Going to revise my decryption tool slightly to make...