This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

Modbus - AEROTEMPER
#1
Hi,

Attached you'll find a MODBUS RTU manual for an AEROTEMPER.

I did integrate a couple of Modbus devices before but the register list for this device is different from what I'm used to. 
Can you advise on how I can determine the function of each register, whether it's a coil, discrete input, holding register, or input register? Additionally, can you provide information on the address of each register?

Thankful in advance

Attached Files
.pdf   r674008-manual_volcano_wing_modbus_hy_en.pdf (Size: 788.5 KB / Downloads: 21)
Reply
#2
Holding register with uint16 data type. Use Read test to check that the values that you read are correct. You might need to do address - 1 for each register.
Reply
#3
(12.05.2023, 07:18)admin Wrote: Holding register with uint16 data type. Use Read test to check that the values that you read are correct. You might need to do address - 1 for each register.

Hi, 

The read test works fine and I can read the registers but when i added the device  the lm5 show it as its not found, please see attached

Attached Files Thumbnail(s)
   
Reply
#4
Provide your profile and check what you get in Modbus Error log.
Reply
#5
(21.06.2023, 10:25)admin Wrote: Provide your profile and check what you get in Modbus Error log.

No errors , attached the profile

Attached Files
.json   mittet.json (Size: 1.42 KB / Downloads: 5)
Reply
#6
What parameters did you use in Read test, it is not visible due to result.
------------------------------
Ctrl+F5
Reply
#7
(21.06.2023, 10:34)Daniel Wrote: What parameters did you use in Read test, it is not visible due to result.

Attached Files Thumbnail(s)
   
Reply
#8
Are you sure about the Error log? There's a log specific to Modbus, not global Error log.
   
Reply
#9
(21.06.2023, 10:37)admin Wrote: Are you sure about the Error log? There's a log specific to Modbus, not global Error log.

Oups, this is the errors then

Attached Files Thumbnail(s)
   
Reply
#10
Map only the first register to an object and see if you get a reading.
Reply
#11
(21.06.2023, 10:43)admin Wrote: Map only the first register to an object and see if you get a reading.

yes it worked
Reply
#12
See this: https://forum.logicmachine.net/showthread.php?tid=4718
Reply
#13
(21.06.2023, 11:01)admin Wrote: See this: https://forum.logicmachine.net/showthread.php?tid=4718

I increased the pool interval to 20s and timeout to 5 also add read_delay to all the register by 0.1 . nothing helped
Reply
#14
read_delay is a global setting: https://forum.logicmachine.net/showthrea...3#pid13343
Reply
#15
(21.06.2023, 11:46)admin Wrote: read_delay is a global setting: https://forum.logicmachine.net/showthrea...3#pid13343

Thanks a lot
Reply


Forum Jump: