adccommunitymod (AutomationDirect) asked a question.
Any example code for DoMore and GS2 drive Modbus?
Created Date: February 08,2013
Created By: trimixdiver1
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Anyone have any example code for the above? The manual is a little sketchy with the rs485 modbus coms. The whole HEX conversion thing had got me stumped. Other drives I just entered the 400201 or the like, but it seems like this is not the case for the GS2. Thank You!
Created Date: February 08,2013
Created by: bcarlton
After using 'Configure ' to set the serial port to 'modbus RTU Client ' and setting the port parameters the MWX and MRX commands should provide all the interface you need. The GS2 manual (starting at page 108 - PDF version) gives you all the addresses in Modbus format. Can you give more detail to the problems you are having?
I haven't used these yet. I believe you can ignore the 'modbus Server ' addresses. The MWX and MRX, since YOU control them, read and write to/from the standard memory. I would use stages (at least two) placing one communication instruction in each, and JMPing on success or error to the next stage. The last stage could JMP back to the first stage.
Created Date: February 08,2013
Created by: trimixdiver1
I guess I didnt read deeply enough, but is there a word or somethng for the control (start, stop...)
Created Date: February 08,2013
Created by: bcarlton
The addresses for commands are at the bottom of the table on page 5-8 (112 PDF version)
Specific information for these commands starts on page 4-59 (101 PDF).
They aren't individual bits in a word as in AB Powerflex drives.
Created Date: February 08,2013
Created by: plcnut
Did you get the program opened that I posted before?
If you got it then you should be able to cross over the memory using the drive manual to see which bit controls start/stop, like V2004:0.
Where have you gotten so far? Can you communicate with the drive(s) at all?
Created Date: February 11,2013
Created by: plcnut
I have attached three screenshots for you to show all necessary configurations for 1 drive.
In your drive:
P3.00 = 03
P4.00 = 05
P9.00 = 0
P9.01 = 03
P9.02 = 05
P9.03 = 01
P9.04 = 01
If you are not sure about the drive parameters you may want to reset it to factory defaults to begin with by setting P9.08 = 99, then you can go in and set the motor nameplate settings, and those that I have listed above.
Once you have done that much, all you will need to do is write the speed reference (600 = 60 hz.) to V2003. and put V2004:0 as an OUT coil to turn the drive on and off.
This should get you going. If I left something out please let me know.
Created Date: February 13,2013
Created by: trimixdiver1
Thanks for the screenshots!!
Created Date: February 13,2013
Created by: plcnut
Thanks for the screenshots!!
Are you making progress?
Created Date: February 13,2013
Created by: trimixdiver1
Not yet, I got side tracked with the TB Woods drive, but Im going to start the GS2 this weekend.
Created Date: February 13,2013
Created by: franji1
Are you making progress? Mr. Nut :D,
Based on your screen shots, it appears you do not need the OPENDEV/CLOSE instructions/stages since you are referencing the Hard Device (@VFD_COMMS - the @ sign implies hard device) in both MRX and MWX instruction, and not the Device Reference structure (the Output parm of the OPENDEV instruction), VFD1 (note the missing @ sign).
Device references just give you one level of indirection in various device instructions where you want to dynamically change at runtime which device you are referencing on a situation basis.
That doesn't mean it won't work, or isn't useful (you may be monitoring the device reference's .Open or .Success or .Error member in another code-block), but all of that information is implicity available from the MRX/MWX instruction and/or the code-block's stage logic.
I just wanted to communicate that the OPENDEV/CLOSE is not required.
Created Date: February 13,2013
Created by: plcnut
Mr. Nut :D,
Based on your screen shots, it appears you do not need the OPENDEV/CLOSE instructions/stages since you are referencing the Hard Device (@VFD_COMMS - the @ sign implies hard device) in both MRX and MWX instruction, and not the Device Reference structure (the Output parm of the OPENDEV instruction), VFD1 (note the missing @ sign).
Device references just give you one level of indirection in various device instructions where you want to dynamically change at runtime which device you are referencing on a situation basis.
That doesn't mean it won't work, or isn't useful (you may be monitoring the device reference's .Open or .Success or .Error member in another code-block), but all of that information is implicity available from the MRX/MWX instruction and/or the code-block's stage logic.
I just wanted to communicate that the OPENDEV/CLOSE is not required.
I won't use them if I don't need them. That will make things even simpler.
Thanks. :)