Closed ozeta closed 6 years ago
Hi @ozeta, apologies for the confusion, I realize that I'd asked you to create an issue on our GitHub repo, but I had no specified to use the pycom/pycom-libraries repository! If you wouldn't mind copy/pasting this to https://github.com/pycom/pycom-libraries/issues as that's where I'm handling the Pytrack/Pysense issues!
I'll close this now so as not to confuse Daniel/the team working on the LoPy/WiPy 2.0/etc. firmware!
Thanks!
ops, sure no problem!
Hi, I'm playing with the wipy2 + pytrack.
os.uname()= (sysname='WiPy', nodename='WiPy', release='1.7.5.b2', version='v1.8.6-694-g25826866 on 2017-06-29', machine='WiPy with E SP32')
pytrack dfu ver: 0.0.3
I used the turorial script from github to get the accelerometers data in a while loop:
I think I got some bugged response
laying on the bench it seems all regular:
but if I roll the pytrack, both pitch and roll reads some values:
if I pitch the pytrack, pitch and yaw reads some values:
if i yaw the pytrack ( Holding it vertically), it's pitch and yaw again
but if i turn it 90°, yaw decreases and roll increases:
is that a known bug or I do I have to parse the output data or else?