You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the tool for an iHSV42 motor (which has v606 firmware). In principle it works, I can change tuning parameters, plot the graph and optimise the parameters. When I remove the power from the motor though all parameter values are lost and everything reverts to default values on the next start. I am not sure whether this is really a problem of this nice tool, because I cannot get the original software to work at all (sees no connection, maybe it doesn't like my serial USB adapter).
Any hints are welcome!
EDIT: Maybe this is caused by the newer V606 controller?
The text was updated successfully, but these errors were encountered:
I faced the same issue and finally seem to have solved it - testet with iHSV57 v603 and v606.1 motors that did not store the parameters permanently before.
After comparing the Modbus communication from the JMC software on Windows and iHSV-Servo-Tool on Linux on a logic analyzer the only difference I could see is that the JMC software re-reads the registers after writing new parameters to the servo. For whatever reason this did the trick for me - my updated fork is public at https://github.com/simonkuehling/iHSV-Servo-Tool if someone else stumbles over this as well.
I am using the tool for an iHSV42 motor (which has v606 firmware). In principle it works, I can change tuning parameters, plot the graph and optimise the parameters. When I remove the power from the motor though all parameter values are lost and everything reverts to default values on the next start. I am not sure whether this is really a problem of this nice tool, because I cannot get the original software to work at all (sees no connection, maybe it doesn't like my serial USB adapter).
Any hints are welcome!
EDIT: Maybe this is caused by the newer V606 controller?
The text was updated successfully, but these errors were encountered: