![]() ![]() Offset - manufacturers sometimes provide a numerical offet to be used with a value in a register.Only input this if the manufacturer's documentation provides a value Multiplier - manufacturers sometimes provide a multiplier to be used with a value in a register.For state registers, use the shorthand to tell the Critical Labs app what you would like to name the states Unit - For numerical values, this is the unit.Name - the name of the register (or description of the data it contains).Starting register - the register you are trying to access.Function code - this explains what type of data is found in the register and, if standards are followed, where the register is located.Critical Labs provides a number of different options when creating Modbus register mappings to accommodate manufacturer specifications, including: The key here is to find the manufacturer's documentation on how the equipment's Modbus registers are implemented. Some will support signed integers (negative numbers) and others won't. Some manufacturers will provide the value as a float. ![]() Some manufacturers will provide an integer (a whole number) and then a corresponding "multiplier" (such as 0.1) to convert that whole number to a decimal. Depending on the manufacturer of the equipment and how they chose to implement Modbus, these data types can vary. Each register is 16-bits long and can hold a signed integer, an unsigned integer, or a float. Registers in the 3xxxx and 4xxxx range are considered numerical, meaning that they can hold large number values. This is currently done using a special shorthand in the sensor's unit. In the Critical Labs web app, you can give the 0 value a state name and the 1 value a state name. Registers in the 1xxxx range are for reading state. Critical Labs does not support controlling equipment, so we typically do not deal with registers in this domain. Examples of this would include starting a piece of equipment or changing its state. The first 9999 registers are designed to handle control input. The table below describes the Modbus standard for different register addresses in the protocol (table information courtesy of Simply Modbus): Let's take a look at the Modbus standard to understand what to expect from different Modbus register locations and how they can help you get more information out of your equipment with Critical Labs. ![]() Did you know that Modbus has standards for numbering registers? It turns out, if you access register 10004, you should expect to get different information than if you access the register at 30392. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |