03-06-2015 05:17 AM
Maybe I will put this specific question in another thread as it does not have specifically to do with the motor. I will report tomorrow if that worked (provided I am able to build the right string ;)).
03-07-2015 11:19 AM
So, after another session with the motor, I came to this conclusion.
You are right, the motor moves indeed really slow (approx. 48 min for 1 mm). Other commands like setting the origin or getting the position work. Even the "Change Velocity" command seems to work. If I query the status of the motor, the velocity value conicides with the value I set.
The "only" problem is, that the motor moves really slowly regardless of the set velocity. I assume that there is another problem, which cannot be solved using LabView. That is the reason why I contacted the manufacturer again.
Nevertheless, thank you for your advice! 🙂
03-07-2015 11:28 AM
Glad to hear you have figured out part of it at least. Are you sending the velocity command before you send the move command?
03-07-2015 12:55 PM
Yes and I am checking if the velocity is set via the status report!
03-14-2015 07:32 AM
The problem seems to be solved now.
I got some Vis frome the supplier and compared the code to my code. Every string I sent was correct, but the velocity values were too big! I am pretty sure that I tried out lower velocities as well, but maybe the motor was moving while I was sending these new values. The highest velocity which can be set has a value of 1300 instead of 50000, which the reference manual implies.
Now everything works even with my VIs and the motor moves! Thank you again for your suggestions 🙂