Hello everyone, I am currently dealing with issues regarding a Modbus meter. I am not receiving any meaningful data back from it, despite following the instructions in its datasheet. I am wondering if this meter is actually a Rayleigh instrument. The data I am receiving is as follows: XMT: [100][000][000][000][000][006][012][003][019][191][000][004] and RCV: [100][000][000][000][000][003][012][131][002]. Can anyone provide guidance on troubleshooting this issue?
Do you have more details about the specific device you are using as the Modbus Master? It's important to note that when dealing with Modbus Communications, if you encounter strange data, consider whether the devices on each end are using 0 or 1 based data addressing. Also, when working with 32-bit values, you may need to swap the word order.
I am perplexed by the XMT and RCV packets displayed, as they appear to be Modbus/TCP packets while the meter only supports Modbus RTU. Are you also utilizing a Modbus/TCP to Modbus RTU converter? Your XMT packet indicates a request for 4 holding registers starting at register address 5055, with the RCV packet receiving an exception response of code 02 ILLEGAL DATA ADDRESS, signifying that the requested registers do not exist on the device. Upon reviewing the device's Modbus table, available at https://hager.com/intl-en/products/...le/190724_MODBUS_TABLE_FOR_ENERGY_METERS.XLS/, and comparing the Address DEC with Address HEX columns, it appears that the correct starting register address should be 45056 instead of 5055. This discrepancy is due to the document using a 0-based register addressing system, where B000 hex equates to 45056. It is worth noting that 45056 does not correspond to Holding Register 5056 in Modbus notation; instead, it represents a 0-based register address. For more insights on Modbus register numbering schemes, you can refer to my post on Modbus Register Numbering at control.com. Different Modbus vendors utilize varying notations for documentation, making it essential to understand the differences in numbering schemes. If you inputted 45056 into your client to generate the XMT packet, you may need to input 445057 for the master/client to correctly request register address 45056.
Thank you, jshilze, for your assistance in addressing this issue. I will be visiting the site tomorrow to determine if the suggested solution is effective. Your help is greatly appreciated, as this particular problem had proved challenging for me.
Hey there, I'm thrilled that it worked for you! Your time is valuable, and this solution has definitely saved you a lot of time. However, I can't shake the feeling that I might encounter this issue again in the future. What led you to realize that an extra register was necessary?
I'm pleased that everything is functioning properly. I would recommend revisiting my earlier post, as I am confident that it addresses your inquiry. In particular, refer to the Modbus register numbering guide I referenced, which mentions that the document follows a 0-based register addressing system, as evidenced by the statement "B000 hex equals 45056." It is noteworthy that hexadecimal register addresses consistently start from 0 (I have yet to come across any instances where this is not the case).
I've worked with Modbus meters before and this indeed could be tricky. It's hard to confirm if it's a Rayleigh instrument just based on data. A couple of things that may help: First, double-check your Modbus settings and configuration, they should be in line with the datasheet. Second, verify your cable connections, a simple loose wire can cause issues. Lastly, the issue might be in the data format or addressing. You could use a tool like Modbus Poll or similar to debug the values you are getting or to simulate them to rectify the problems. Just some thoughts off the top of my head, hope that helps!
It definitely seems like you're facing quite a challenge there. Based on the data you provided, it's not necessarily clear if the lack of meaningful data is due to the meter being a Rayleigh instrument or just an issue with the Modbus configuration itself - both can create complications, particularly when it comes to working with data communications. One thing you might want to consider is checking your wiring and connections thoroughly, a slight misplacement often causes this type of problem. Also, ensure that your software is correctly configured and that you're using the right function codes. If these steps don't help, there is a possibility the issue could lie deeper within the Modbus protocol or the meter itself, in which case you may need more specialized assistance. But let's hope for now it's just a minor glitch that can easily be rectified!
It looks like you may be dealing with a communication problem. Make sure your request is correctly formatted and the register address is correct. The return code [131][002] on your received data (RCV) suggests an acknowledgment with an exception code - typically indicating an illegal data address. I would first verify the device ID and data you are trying to access. You can refer to modbus exception codes for further diagnosis. Also, if you suspect it's a Rayleigh meter, confirm the unit's modbus parameters do match those specified for Rayleigh instruments. It could be a question of compatibility.
Hi there, it seems like you're dealing with a head-scratching issue. Based on the received data it appears there’s been a Modbus exception code returned, 131 (or 0x83 in hexadecimal). This usually indicates there’s an issue with the command you're sending, possibly a mismatch with function code or data address. I'd cross-check the documentation to confirm you're sending the right information. Also, you can try reaching out to Rayleigh Instruments' customer support. This problem could also occur due to a loose or faulty connection, so it's worth double checking your wiring as well.
Hey there! It sounds frustrating not getting the right data from your Modbus meter. One thing you might want to check is the wiring and connections to ensure they're secure and properly configured according to the meter's specifications. Also, double-check the baud rate and other settings in the Modbus configuration—sometimes a small mismatch can result in garbled data. If you're able to, try testing the meter with another known working device to see if the issue persists. Lastly, if you suspect it might be a Rayleigh instrument, it might help to reach out to their support team for specific insights related to your model. Good luck!
✅ 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: - The user suspects that the Modbus meter may be a Rayleigh instrument. However, based on the provided data XMT: [100][000][000][000][000][006][012][003][019][191][000][004] and RCV: [100][000][000][000][000][003][012][131][002], it is not explicitly confirmed whether it is a Rayleigh instrument or not.
Answer: - There could be various reasons for not receiving meaningful data from the Modbus meter, such as incorrect configuration settings, communication protocol mismatches, wiring issues, or potential hardware problems. Troubleshooting these aspects may help in resolving the issue.
Answer: - To troubleshoot issues with the Modbus meter, it is recommended to check the configuration settings, ensure the communication protocol settings match between devices, verify the wiring connections, and inspect for any potential hardware faults. Seeking guidance from the manufacturer's technical support or documentation can also be beneficial.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.