How to communicate with Compax3 via RS232

[Vijay_Karthick]

Please note that there will be two "no stop" bits. Both should be enabled (i.e. high) for motion to take place!

[Vijay_Karthick]

Try writing O 1100.3 = $4007

[davecyli]

I have an S100V2F12 I12T11 M12

I'm pretty sure I've tried $4007, that's from the manual correct? For manual motion?

I have also noticed that in the optimization window under error history we get Tracking Errors, undervoltage Errors, and DC link voltage too low. Wondering maybe that has something to do with it.

To try to fix that I've set the "Error Reaction" to Ignore Tracking Error and Undervoltage

In my serial terminal I've read 

O550.1 which returns a 1

and

O550.2 which returns $7320 in decimal which is the tracking error.

I tried to clear that by "Acknowledging the Error" using o1100.3=0 and o1100.3=$4003. Maybe I'm not doing it fast enough?

And last thing..

So pg 295 of the manual has an example. It is an "Entry of a motion set in set 5"

I just have to know.  This set 5. is that in the motion profile table? And are those "sets" anyway related to bit8 to 12 in the control word 1100.3 on pg 292?

I just can't figure it out and it's killing me!!

//EDIT//

HOLY MOLEY

Ok, so there is 5 bits in the control word.

Setting all 5 bits to 1 is 11111 which is decimal for 31.... AND THERE ARE 31 SETS PLEASE TELL ME THIS IS IT!

Well 32 sets technically.. with the 0th set.. but still 00000 = 0

[Vijay_Karthick]

DC Link voltage too low error comes due to no supply voltage. Have you given the 230 V AC?

Also, during configuration of the compax drive, in a window, which asks for position tracking error and position tracking window, set the values to very high values.

For eg. if I were to configure the movement in degrees, I would keep the position tracking window as 100 degrees and window as 10 seconds, and then later tune it and optimize the window...

Undervoltage and DC link voltage too low errors are solely due to non availability of AC voltage only!

[davecyli]

Thanks Vijay!

I will try that on Monday.

I don't know how the DC Link voltage occurs. In setup mode in the optimization screen I can energize the motor just fine though. And can jog+ and -

O wait.. I think our wall voltage might be less from what I heard.. I will check on that too.

[Highland_Controls]

Make sure that you are able to completely control the drive from the Optimization program.  Fully configure and tune the drive so you have good performance.  Low DC link voltage means that you try to enable(or is enabled) without line voltage.  This is typically configured to be a low setting, so you shouldn't see the alarm unless you have no AC voltage coming to the drive.  The other low voltage error on the extra I/O means you are trying to run with the second stop input on.

Have you seen this: http://www.parkermotion.com/dmxreadyv2/faqsmanager/faqsmanager.asp?question=1283

[davecyli]

No I have not read that.

Thanks!

[davecyli]

The link shows a visual basic gui with leds indicating the status of the controller.

Which reminds me of a question I had.

Is it ok to be constantly polling the controller of its status? And at what rate would be ok?

Or is this something I should experiment with?

Thanks again,

David Li

[Highland_Controls]

You can poll it as fast as you want.  Just make sure each query waits for a respsonse before you send another query.

[davecyli]

Well I got my labview program to constantly poll the status and control words as well as o550.1 and o550.2 which are "Read last error" and "Read last but one error"

Read last but one error returns to me 29472

Which is 7320 in hex

Which corresponds to this error:

Anybody have any experience with this error?

I did increase the window to 100 deg and 10ms. Is this not enough?

I also have the "error reaction" set to 0 - no response, so that should completely ignore it anyways right?

Thanks.