Created Date: January 28,2018

Created by: Ridgeline Mach

Have done it many times, and it works well. But the commands are Modbus Read and Modbus Write in PSuite. Just a word of caution, your writes have to be limited to three registers. Follow chapter 5 of the GS drive manual for help. I use the cable listed for Click port 3. I 've also controlled 3 drives from the same P2K, and a nice feature of the P2K is you can set times for automatic polling in the read and write commands.

Created Date: January 28,2018

Created by: kewakl

Have done it many times, and it works well. ...

Just a word of caution, your writes have to be limited to three registers.

Is this a documented rule or an observed limitation?

Do you know if this applies to other configurations (comms protocol, cable length, net configuration, termination, message length, comms delays, baud...) than what you have used?

I see in CH5 that the CLICK example has three registers in some of the SEND instructions, but that may be coincidence.

Also, in the DL example has three registers in some of the MWX instructions. Again, that may be coincidence.

The only thing that I can find in the manual that says why in the examples they only SEND three registers is respect for the Keypad STOP button:

Separate Run Command Write Instruction

Why do we write the Run Command with a separate write instruction? If we

write the Run Command to the drive along with the Speed Reference, Direction,

External Fault, and Fault Reset Commands, we can keep the parameter addresses

in sequence, and we can update all five of the commands with one write

instruction . This method is valid only if we disable the drive’s keypad STOP

button (P3.00 = 04).

Typically, the keypad STOP button will be enabled (P3.00 = 03), and we need to

prevent a change in one of the other commands from overriding a keypad Stop

Command by causing a previous Run Command to be rewritten to the drive. By

using a separate Run Command write instruction, only a deliberate Run

Command change by the program will run the drive again after a stop.

Created Date: January 28,2018

Created by: Ridgeline Mach

I called tech support when I was having an issue of the drive(s) ignoring my run command, and I was asked "how many " registers was I writing to at once, and I said, "four. " That was when I was told to write to no more than three. So I have one Write for Speed, Run, and Direction, and a 2nd for Drive Reset.

Edit: My Reads are looking at the first eight of the read-only status addresses.

Created Date: January 28,2018

Created by: kewakl

I called tech support when I was having an issue of the drive(s) ignoring my run command, and I was asked "how many " registers was I writing to at once, and I said, "four. " That was when I was told to write to no more than three. So I have one Write for Speed, Run, and Direction, and a 2nd for Drive Reset.

Edit: My Reads are looking at the first eight of the read-only status addresses.

Hmm, If you had only answered the techsupport guy "FIVE ", then your answer may have had merit. J/K

Makes me wonder though, if you had answered FIVE, would you have been negotiated in to trying just FOUR, then THREE, until it worked?

The MANUAL Programming example eludes to being able to write to FIVE registers. we can update all five of the commands with one write instruction .

Created Date: January 29,2018

Created by: kewakl

The GS2 manual has the SAME SENTENCE fragment as the GS3. Ch5 - pg 29

If we write the Run Command to the drive along with the Speed Reference, Direction, External

Fault, and Fault Reset Commands, we can keep the parameter addresses in sequence,

and we can update all five of the commands with one write instruction.