Brian

PMAC Panel is not needed to run with the Vi's I developed using pcommserver. Only pcommserver needs to be installed, which installs with the PeWin32Pro2 package.

Commands I was not aware of. I had to get the latest Turbo SRM to find them. That seems like a good option.

Since battery-backed RAM isn't an option for Clippers, along with other controllers, is it OK it issue a CMD "sav" from within a PLC(as a one shot) when you want to save variables? I am currently saving variable with a PC based application using pcommserver, but am looking to eliminate the PC, and just have a connection to an HMI or A-B PLC.

Make sure it is wired correctly. With the drive disabled, push the carriage against an end stop and note the position. Move the carriage, and see if the same position reading occurs at the end stop to determine which channel might be losing counts. The encoder error you are getting, though, is more like you are "gaining" counts. In other words, a count is occurring when it shouldn't be. Is your encoder optical or magnetic?

OK, now I understand. I still think that your step needs to be bigger. If you have vibration issues, then lower the proportional gain, then slowly raise it.

I think you need to solve your commutation and encoder problems before you attempt to tune.

What I am saying is that the results you get from the step move tuning are a good starting point for tuning for another type of move. Your real world application won't be using a step move. Use another type of move that is like the type of move you will be making, and tune to that. When you are all done tuning to that type of move, and you happen to do a step move again, don't be surprised if the step move doesn't look good. That is OK, though.

You will want to make a bigger step move. At least 5 times bigger, probably more, though.

I mostly answer these questions here: http://forums.deltatau.com/showthread.php?tid=847. Yes, once you tune for the move you want, the step move will probably not look good. Tuning is as much art as it is science, so it is hard to say what parameters need to be adjusted. If it were pure science, then the autotuning would work perfectly.

The difference is probably due to the bearing mechanism. I assume you are using recirculating ball linear bearings. When they are new, they will be rather tight. Also, the first move after they have been sitting for a while will break things free. What distance(mm)=1000 counts? I almost always keep integral gain at zero and I134=1 for the step move. The step move, if it is large enough, allows you to get a good starting point for tuning. After you have a good step response, select a tuning profile that most resembles the move your axis will be making in the real application. You can then set I134=0 and start to add integral gain, and adjust the other parameters.

All that information is in the Turbo Software Reference manual. It is under the section for the online command "?".

Can't remember if you have to, but I think you do. Your motor must be phased before you get to this step. Also, we(in the USA) know nothing about the IMAC FLEX, but I believe it is just a packaged Clipper sold only in Asia. You must follow the PWM setup for the analog outputs that is in the manual, or you will have poor performance. This should be done first before you attempt to tune. You will also want to save your configuration before tuning, take note of what tuning I-variables you change while tuning, then don't save your configuration after tuning. Issue a $$$ to restore your configuration, manually change the tuning I-variables, then save to flash. The tuning utility make a bunch of changes, and if you happen to save while the utility is open your configuration will be messed up. At the very least, you will lose your coordinate system configuration. Do you have a local distributor that can help you?

Yes, I believe so.

This is not an I-Variable, but just the motor status word(should be Y:$0000C0 for motor#1). The word is broken out into bits using M-Variables, typically Mx30-Mx49. If you want, you can query the word with the online command "?", for the currently addressed motor.

I believe that the command sent for that is "#1J/". Both an "O" and a "J/"(or other J commands, and other commands like "A") will enable the motor and keep them enabled until they are killed by user command or by some error. The "J" commands will also close the position/velocity loop(if it doesn't have a phasing error).

From the Turbo Software Reference Manual: Bit 8 Phasing Reference Error: This bit is set to 1 on power-up/reset for a PMAC-commutated (Ixx01 bit 0 = 1) synchronous motor. It is also set to 1 at the beginning of a phasing search move or phasing absolute position read for such a motor. It is set to 0 on the successful completion of a phasing search move or phasing absolute position read. If this bit is 1, the position/velocity servo loop cannot be closed for this motor. This bit is set to 1 if the phasing search move for a Turbo PMAC-commutated motor has failed due to amplifier fault, overtravel limit, or lack of detected motion. It is set to 0 if the phasing search move did not fail by any of these conditions (not an absolute guarantee of a successful phasing search).

By default the bit is set at power up. The only way to clear it is to perform the phasing search. I am sure this is by design so that the motor can't be enabled without being phased.

I believe that only a static IP address is possible. The configuration utility is used by Delta Tau internally for other functions, and I believe that the "Store_IP" button is the only one that has any function for end users.

That error bit is set on controller power-up or motor reset($). It is cleared after a successful phasing search. What you are seeing is normal with I180=6. You must issue a "#1$" command to begin the phasing search. If it is successful that error bit will be cleared. You can then normally enable and disable the motor without having to do another phasing search until the next power cycle(or if feedback is lost somehow).

What PLCs are enabled at power on? Is any motion being commanded automatically? Is that axis getting enabled automatically?

Why are there 2 DWELL0's? How are you determining that the move is starting? If you have any TS time(s-curve accel/decel) of significance, then it may appear that the move start is delayed. Are you able to plot commanded move and see what is happening? Can you post a section of your code?

What values of "xxxx" are you using? A value of 2047 should give you 0 volts.

I believe those are test points for the power, and not a place for the connector. Be sure you have inserted the ACC-1P on the headers properly. It is easy to not get all the pins lined up in the socket. Also make sure you have it in the correct orientation.

Glad to help. I have thought about putting together a LabVIEW driver set based on PcommServer, but I am not sure if there would be much of a market for it.

Check Ixx29 for each axis and make sure it is 0.