![]() ![]() ![]() ![]() ![]() ABB drives are the best solutions that will help you save considerable energy particularly in applications such as pumps, fans and compressors. ABB drives ensure that energy is consumed only to the extent required by the process and thus reduce your energy costs. Give it a shot.The world leader in technology, ABB is the top manufacturer of variable-speed motor drives with its wide range of products and technology.ĪBB low-voltage motor drives offer you the motor control solutions that you need in industrial, building and OEM sectors thanks to their safety, easy-to-use features, flexible operating conditions and long service life. By changing the syntax of the ADDM block we are explicitly driving our message with that device ID in it. Manufactures often do this because it's easier on them and then they also don't have to write an entirely new Modbus driver. DMG800) still expects to see the device ID in the message even though (technically) this should be 255 for Modbus/TCP. implement their Modbus protocol simply by taking the Modbus/RTU message and placing it inside of an Ethernet frame. Even though device IDs aren't truly applicable for TCP, some manufactures of devices/instruments/etc. In the case above you'll replace NODE_ID with the actual numerical value that you can enter on the DMG800 for the Modbus device ID (1-247). You might try adjusting your ADDM syntax to the following: I also read where it specifically states to read the register address -1 just as u/PLC_Matt suggested. I did verify that this device is accepting of the Modbus function codes available to us in the READ_VAR FB (FC1, FC2, FC3 & FC4). I Googled for the manual on your DMG800 and found a document where it talks about how they implement their device with Modbus. So I don't think it's an hardware problem. I have tried to test the VFD (from which I can read/write) with every port of the plc rack. I have tried to use a modbus master simulator to see if I can read from the Analyzer (start address 50, 2 words) and it works immediately. On PLC startup it returns 1 for like 10 seconds and then it changes to 7. The function READ_VAR returns always error code 7 on the Gest "communication report" byte. RECP = array long enough to save read values in it. = 0 (I saw that changing this parameter is useless) If I want to read, for example, the frequency from the DMG (which is linked to the NOC0401) I have to refer to address 50 and 2 words. I know that I have to use "0.0.3" for "pointing" to PLC and "0.1.0" for NOC0401. I have zero problems (for now ahaha) reading from and writing to the VFD. I have this M340 equipped with a NOC0401 (4 eth ports) which have to communicate with an ABB VFD (acs380) and with an Analyzer dmg800 equipped with an ethernet module (EXP 10 13). Hi guys! I hope some of you can help me solving this problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |