+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10)
+--- Thread: ModBus 32Float Problem (/showthread.php?tid=2203)
ModBus 32Float Problem - adiaz - 20.08.2019
Hello guys!
I have a problem with Modbus Profile.
When i try reading a register with Read Test, I can read the register with no problem. But when I create a profile and attach variable to the register, it's not working. I don't know what's happening.
I attach photos of ReadTest and the profile.
Very thankfully.
Profile:
Kamstrup_Multical403_prove.json (Size: 307 bytes / Downloads: 21)ReadTest:
ReadTestOK:
RE: ModBus 32Float Problem - admin - 20.08.2019
Do you mean that the value is not read at all or that the value is not correct?
RE: ModBus 32Float Problem - adiaz - 20.08.2019
(20.08.2019, 08:02)admin Wrote: Do you mean that the value is not read at all or that the value is not correct?
The value is 0. Not changing.
Thanks!
RE: ModBus 32Float Problem - admin - 20.08.2019
Do you have anything in error log or modbus error log?
RE: ModBus 32Float Problem - adiaz - 20.08.2019
(20.08.2019, 08:33)admin Wrote: Do you have anything in error log or modbus error log?
Before this profile I had another with read_count, and with value 1 on this parameter, we got ilegal data adress, changing it to value 2, no error. Now without read_count no error in error_log.
RE: ModBus 32Float Problem - admin - 20.08.2019
Have you deleted your old device? When uploading new profile you must create new device. Otherwise old profile data will still be used.
RE: ModBus 32Float Problem - adiaz - 20.08.2019
(20.08.2019, 08:55)admin Wrote: Have you deleted your old device? When uploading new profile you must create new device. Otherwise old profile data will still be used.
Yes, the procedure is:
1. Delete device
2. Delete Profile
3. Add new profile
4. Create new device
RE: ModBus 32Float Problem - Daniel - 20.08.2019
Hi
"read_delay":1, should be in the profile description not in mapping.
BR
RE: ModBus 32Float Problem - adiaz - 20.08.2019
(20.08.2019, 09:36)Daniel. Wrote: Hi
"read_delay":1, should be in the profile description not in mapping.
BR
Changed. Also Not working
RE: ModBus 32Float Problem - Daniel - 20.08.2019
try with just necessary parameters
Code:
{
"manufacturer": "KAMSTRUP",
"description": "MULTICAL 403",
"mapping": [
{"name": "Temp.1 Inlet",
"bus_datatype": 14,
"type": "register",
"datatype": "float32",
"address": 6
}
]
}RE: ModBus 32Float Problem - adiaz - 20.08.2019
(20.08.2019, 10:15)Daniel. Wrote: try with just necessary parameters
Code:{
"manufacturer": "KAMSTRUP",
"description": "MULTICAL 403",
"mapping": [
{"name": "Temp.1 Inlet",
"bus_datatype": 14,
"type": "register",
"datatype": "float32",
"address": 6
}
]
}
Still not working,
No error log but value is not changing.. (0.000)
RE: ModBus 32Float Problem - Daniel - 20.08.2019
Can you still read it via RTU test?
Try reboot.
RE: ModBus 32Float Problem - adiaz - 20.08.2019
(20.08.2019, 10:35)Daniel. Wrote: Can you still read it via RTU test?
Try reboot.
Okai.. That was the problem -.-
Rebooting Logic now working. Thanks for your patience!
Very thankfully.
RE: ModBus 32Float Problem - Hugo - 13.12.2020
(20.08.2019, 10:44)adiaz Wrote:(20.08.2019, 10:35)Daniel. Wrote: Can you still read it via RTU test?
Try reboot.
Okai.. That was the problem -.-
Rebooting Logic now working. Thanks for your patience!
Very thankfully.
Hi Daniel,
are you happy with the 403? Like the 603, does the 403 also have its own data logger? Well, i will conect thrugh TCP / IP modbus so it will be different however you are you satisfied?
Update: Sorry, today i got the info, just the 603 model has TCP / IP however, its orderd and will arrive soon.