search

HebiRobotics / hebi-matlab-api

Public download and issue tracker of the latest HEBI API for MATLAB
http://docs.hebi.us/tools.html#matlab-api
0 stars 0 forks source link

Error when running getting feedback. #16

Closed daverolli closed 5 years ago

daverolli commented 5 years ago

When running a demo using 1.5.1-SNAPSHOT I got this error message. I was running in macOS Mojave, Matlab R2016b. System was a 3-DoF arm running with fixed IP addresses using an Anker USB to Ethernet Adapter.

Module did not respond with mac address!
Failed to parse an incoming message: us.hebi.sdk.lib.bm: While parsing a protocol message, the input ended unexpectedly in the middle of a field.  This could mean either than the input has been truncated or that an embedded message misreported its own length.
Module did not respond with mac address!
Module did not respond with mac address!
ennerf commented 5 years ago

Was there anything else on the network that may be acting weird? Maybe experimental retrofit snake firmware or some Android/iOS app development?

daverolli commented 5 years ago

Nope. Modules running latest firmware doing the teach-repeat demo in Github. Scope was also running at the same time, FWIW. This was a demo offsite, where I had wifi turned off on my laptop so the only things were my laptop and the 3-DoF arm with static IPs.

daverolli commented 5 years ago

Also the error pasted above was spewing continuously until quitting Matlab. Not just a onetime error.

ennerf commented 5 years ago

Sorry for being embarrassed in front of a customer :(

I don't have a good guess on what would cause this. Can you reproduce it on your computer? Did it work correctly with an older API version?

ennerf commented 5 years ago

One thing I can do is to at least remove duplicate lines

daverolli commented 5 years ago

Trying to reproduce here with no luck at the moment. Removing the duplicate lines over and over would at least help debugging if it comes up again.

ennerf commented 5 years ago

I'll also add the source IP address so we at least know where it came from

ennerf commented 5 years ago

The message was actually malformed, so the messages were sent by some firmware issue. I changed it to remove duplicate lines.