Hey all,
I’ve been noticing that my hexy doesn’t work right when using PoMoCo version df86d0d5ff. Whenever I click on the actions on the left(e.g. walkForward) the Hexy twitches and locks and has what appears to be a seizure.
I’ve been starting to look at the source, and I’m learning python as I go, but from what I can tell(after having enabled the debug flag and also putting a sleep statement into servotorComm.py, it looks like the data that is being sent from PoMoCo.py may not be properly calibrated? I’m going to go and experiment some more, but wondered if anyone else had a similar experience(maybe the carriage return isn’t properly parsed in a Mac OSX or something?).
If I connect directly to the Servotor32 and start issuing commands, like #24P1500T0, the servo moves properly - but when I click on a pre-defined action, Hexy loses it.
Also, after clicking on a button, Hexy seems to be locked - clicking on the other buttons don’t do anything or PoMoCo GUI gets locked and I have to close it. When I DO close it, only the GUI closes and I have to force kill the instance in order for it to let go of the device so I can start it up again.
Anyone have similar/better experience with PoMoCo(maybe my MBA’s environment is messed up?)