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 32Float Problem
#1
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:
.json   Kamstrup_Multical403_prove.json (Size: 307 bytes / Downloads: 21)

ReadTest:    
ReadTestOK:     
Reply
#2
Do you mean that the value is not read at all or that the value is not correct?
Reply
#3
(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!
Reply
#4
Do you have anything in error log or modbus error log?
Reply
#5
(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.
Reply
#6
Have you deleted your old device? When uploading new profile you must create new device. Otherwise old profile data will still be used.
Reply
#7
(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
Reply
#8
Hi
"read_delay":1, should be in the profile description not in mapping.
BR
------------------------------
Ctrl+F5
Reply
#9
(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
Reply
#10
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
    }
]
}
------------------------------
Ctrl+F5
Reply
#11
(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)
Reply
#12
Can you still read it via RTU test?
Try reboot.
------------------------------
Ctrl+F5
Reply
#13
(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.
Reply
#14
(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.
Reply


Forum Jump: