Hello, I am currently facing some challenges with a 16-bit integer value 41001 I that I am trying to read using InTouch. My goal is to read each 16-bit segment individually, but I have been unable to do so thus far. The documentation I came across mentions accessing it as 41001:1 for bit 0. To troubleshoot, I have tried working with two bits to ensure there is no offset causing issues. However, my attempts with 41001.1 have been unsuccessful. It seems like I can input any value in OCMC without triggering any errors, making it a frustrating trial-and-error process. This could potentially be a syntax issue with the OCMC input, or it might be related to the Modbus ProSoft configuration settings for reading single or multiple values. I am prioritizing resolving the OCMC syntax problem first. Thank you for any insights or help you can provide.
The problem turned out to be the Bit Order Format, at least from my perspective.
Hey there, it definitely does sound like a syntax problem with OCMC. You should try addressing the 16-bit word as 41001 and each bit in those words as 1 through 16 to avoid an offset issue. In your case, if you're trying to look at the 1st bit, you might want to use 41001.0 (instead of 41001:1). If you're still having trouble, the issue could potentially be in the ProSoft configuration settings. It might be worth looking into adjusting the settings so that you're reading it as multiple values. Hope you find this helpful!
Hi there, dealing with these issues can indeed be frustrating. It sounds like you have a handle on the potential problems, which is a good start. Concerning the OCMC syntax, have you made sure to keep the leading zero on your short integers? It's an often overlooked detail, but it can make a big difference. As for Modbus, I recommend checking your start address and making sure it aligns with the device's addressing. And if you're reading multiple values, make sure you've set registers in sequences. Hopefully, this points you in the right direction.
It sounds like a tricky issue you're navigating. Based on what you've described, it indeed seems like the problem might be related to the OCMC syntax. When you're inputting the address, remember that Modbus uses zero-based addressing, meaning that you might have to subtract one from your intended address. Thus, to read bit 0 of 41001, you should try accessing it as 41000:1, instead of 41001:1. As for ProSoft configuration, I would recommend ensuring that your data types and register addressed are correctly aligned. Syntax and addressing issues are common in similar scenarios, but I hope this advice helps you with your debugging process.
Hey there, it indeed sounds quite puzzling. My first thought would be to double-check your OCMC syntax. Make sure to follow the correct format: if you're using Modbus, your address should look something like MB1:41001. Now, if you're trying to read the first bit specifically, you might want to use: MB1:41001.0, where the ".0" represents the first bit. For InTouch, you can sometimes use ItemName.1 to access the first bit of a word. However, it seems like your issue begins in your Modbus setup. Check your ProSoft Modbus configuration to see if the registers are defined correctly, and whether the data type set there matches with what you're trying to access.
✅ 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: To read 16-bit integer values in InTouch, ensure you are accessing the correct segments using the syntax provided in the documentation, such as 41001:1 for bit 0. Double-check your OCMC input syntax and consider the Modbus ProSoft configuration settings for reading single or multiple values.
Answer: Answer: If you are having trouble reading individual 16-bit segments, verify that your syntax is correct, such as using the correct format like 41001:1 for accessing bit 0. Additionally, check if there are any configuration settings in Modbus ProSoft that could be affecting the reading process.
Answer: Answer: To troubleshoot OCMC syntax problems, start by verifying the input syntax matches the documentation, such as using the correct segment notation like 41001:1 for specific bits. Additionally, ensure there are no configuration conflicts in Modbus ProSoft that could impact the reading process.
Answer: Answer: When facing OCMC syntax issues
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.