Hello compressor expert, I am in need of assistance! I am currently working on connecting an Elektronikon MKIV controller to a Yaskawa GA800 VFD, replacing an ABB ACS800 VSD through Modbus communication. The MKIV controller, serial number 1900 0710 32, is connected to the ACS800 through its RMBA-01 module via a DB9 on 2X2 configuration, without a ComBox-S. The MKIV has a Node ID of 31, which I believe is its Modbus Node ID. To enable communication between the MKIV and the Yaskawa GA800, I have set up a RedLion gateway to relay the register data via Modbus TCP/IP. However, I am facing difficulties in establishing communication between the MKIV and the RedLion gateway through RS485 Modbus. I have tried swapping the TxA and TxB lines, but it did not resolve the issue. I have provided the communication parameters and pinouts for your reference. Unfortunately, I am unable to access the MKIV settings to verify them without the necessary software. Could you please provide guidance on how to connect the RedLion gateway to the MKIV and share any information on the internal Modbus Holding Registers used by the MKIV to control the ACS-800? Your insights would be greatly appreciated. Thank you.
Most drives operate as Modbus server/slaves, with Node ID 31 typically assigned to the old ACS800 as the slave node. A Modbus master does not require a node ID. The Red Lion device acts as a Modbus RTU/Modbus TCP converter or gateway. Configuration of the Red Lion includes setting the slave node ID to 31 and adjusting serial settings such as baud rate, parity, word size (8 bits), and stop bit. Are the serial settings mentioned the default settings or those from the previous RTU network? To communicate with the new drive, the client side of the Red Lion must be configured with the target IP address, Modbus Function Code, and register address(es). The new drive will need its own IP address and potentially a slave node ID. Register addresses on the new drive may differ from the old drive, requiring reference to the respective documentation for comparison. The Red Lion device may offer various hardware configuration options such as Ethernet using a default IP, USB connectivity, or alternatives to the RS-485 bus.
If you're unsure about the MkIV's actions on Modbus, I recommend using a Windows Modbus slave utility program (such as ModSim, Modpoll's slave, or Simply Modbus RTU slave) with a USB/RS-485 converter. Set the slave as node ID 31 with the appropriate serial settings. Analyze the traffic from the master to identify the Function Codes and registers being accessed.
While most drives operate as Modbus server/slaves, the Node ID 31 serves as the slave node ID for the old ACS800. It is important to note that a Modbus master does not have a node ID. The Red Lion device likely functions as a Modbus RTU/Modbus TCP converter or gateway. Configuration of the Red Lion is necessary, specifically setting the slave node ID to 31 and adjusting the serial settings such as baud rate, parity, word size, and stop bit. On the client side of the Red Lion, information required includes the target IP address of the new drive, the Modbus Function Code, and the register address(es). The new drive will need an IP address and possibly a slave node ID. It is crucial to verify the register addresses on the new drive as they may differ from those on the former drive. The Red Lion may have a hardware configuration bus such as Ethernet on a Default IP, USB, or RS-485. In cases where communication issues persist, it is essential to determine if Node 31 on the MKIV Controller is a Modbus or CAN address. If the MKIV is the Modbus master, ensure that the RL RS485 side is configured as a Modbus RTU Slave with the appropriate address. Despite using serial settings from the old RTU network, communication may still be problematic. Consulting documentation and seeking assistance from experts like@Ken Roach or technical support may be necessary to resolve communication challenges effectively.
kay_gsr13 mentioned that most devices can act as protocol converters, allowing communication between RL and VFD (Modbus TCP/IP). The challenge lies in determining if Node 31 in the MKIV Controller is a Modbus or CAN address, hindering communication from RL. Despite setting the RL RS485 side as a Modbus RTU Slave with address 1, there is still no communication. Research suggests using a Combox-S for PLC communication with the MKIV via Modbus. Can anyone advise on the issue of communication between the FC302 Danfoss drive and the GA22 VSD compressor, with the MKIV showing Node ID 31 and the micromaster displaying address 1?
Hello, I am encountering an issue with a GA22 VSD compressor where the faulty drive was replaced with a FC302 Danfoss drive. However, the new drive is not communicating through RS485 communication. Despite trying various options, I have been unsuccessful in resolving this issue. The MKIV is displaying a NODE ID of 31, while the Micromaster parameter is showing an address of 1. Can anyone advise on where I may be going wrong in this situation?
It sounds like you're quite deep into the configuration process! First things first, make sure your RedLion gateway is perfectly set-up to use RS485 communication protocol; incorrect settings can easily interrupt the communication process. Since you mentioned you're not able to access the Elektronikon MKIV settings for verification without the software, I'd suggest getting in touch with the manufacturer's support service - they might be able to provide you with a temporary software access or guide you through the process remotely. Regarding your question about Modbus Holding Registers used by the MKIV to control the ACS-800: To my knowledge, Elektronikon controllers usually use standard Modbus protocol with input registers starting at 30001 and holding registers at 40001. The detailed register map may differ based on the model and the configuration. Remember: Hardware issues can often mimic software or configuration issues. Double check all your connections, terminations, grounding, and cable specifications. Sometimes the smallest oversight can save you hours of programming frustration. Good luck!
It sounds like you've got quite a complex setup going on there! Although I can't give you a definitive solution without examining the specific details of the communication system, I can suggest a couple of things. First, double check the Modbus ID you've assigned. Every device on a network needs to have a unique ID and it's quite easy to make a mistake or duplicate. Also, you might want to evaluate the baud rate and parity settings of all your devices to ensure they match with the MKIV's. As far as the Modbus Holding Registers, normally, you would require a comprehensive manual or communication protocol document from Elektronikon. I'd strongly recommend reaching out to Elektronikon's support if you haven't done so already, they should be able to provide you with the needed information. Good luck with your project!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: Ensure correct wiring connections, verify communication parameters, and check for any software configuration requirements.
Answer: Answer: The RedLion gateway can be used as a relay for register data transmission via Modbus TCP/IP.
Answer: Answer: Verify correct pinouts and wiring connections, and consider checking the configuration settings on the RedLion gateway.
Answer: Answer: Contact the manufacturer or supplier for the required software or tools to access and verify the settings on the MKIV controller.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.