Hello everyone, I am currently experiencing challenges with setting up the Hilscher Gateway for the first time. While I have previous experience with RTA Gateways, the Hilscher product is proving to be a bit more complex. I am specifically working on sending data from a Micro Epsilon Laser scanner to an AB PLC. Since the Laser scanner uses Modbus TCP, the Gateway plays a crucial role in facilitating communication between the PLC and the scanner. I have made progress using Sycon.net, but I am encountering an issue with the data type. The data type is currently set to byte in Sycon.net, but I need it to be INT for proper transfer to the PLC. I attempted to change the data type to SINT in the Ethernet module on the IO tree, but this did not resolve the communication fault due to an Input number mismatch. Any assistance or guidance on resolving this issue would be greatly appreciated.
Do gateway devices typically provide exportable data for importing into the ACD system? Is this feature available?
Cheeseface inquired about the possibility of exporting data from gateway devices for importing into the ACD system. Is there an EDS file available for this purpose? If so, that was the initial step I took.
Hey there! It sounds like you're on the right track with your setup, but the data type mismatch can definitely be a headache. Have you checked if the Hilscher Gateway configuration allows for changing the data type directly within the Modbus settings? Sometimes, you'll need to ensure that both the source (Laser scanner) and destination (PLC) expect the same type. Also, look into the possibility of using a data mapping feature if available, as that can help you convert the bytes to INT before sending them over. If you're still running into issues, you might want to reach out to Hilscher's technical support—they're usually pretty helpful with these types of setups! Good luck!
Hey! It sounds like you're on the right track with Sycon.net, but those data type mismatches can be tricky. Make sure that both the Hilscher Gateway and the PLC are configured to interpret the data type consistently; for instance, if you're sending INT data, confirm that the PLC expects that same format instead of SINT. Sometimes it's also helpful to check the Modbus mapping settings to ensure everything aligns correctly, and don’t hesitate to check the version of your firmware on both devices, as certain updates might address compatibility issues. Good luck, and I hope you get it sorted out soon!
✅ 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: 1. How do I change the data type from byte to INT in the Hilscher Gateway configuration for proper transfer to an AB PLC? - To change the data type from byte to INT in the Hilscher Gateway configuration, you need to adjust the data type settings within the Ethernet module on the IO tree. Changing it to the correct data type, such as INT, ensures proper transfer of data to the PLC.
Answer: - A communication fault due to an Input number mismatch when configuring the Hilscher Gateway for Modbus TCP communication could be caused by incorrect data type settings, mismatched input configurations between devices, or improper mapping of data points. Double-checking these settings and configurations can help resolve the issue.
Answer: - To troubleshoot communication issues between a Micro Epsilon Laser scanner using Modbus TCP and an AB PLC through the Hilscher Gateway, ensure that the Gateway is properly configured with the correct data types, input configurations, and data mappings. Additionally, checking for any error messages or communication faults can help pinpoint the issue for resolution.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.