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 profiler app
#41
(06.03.2025, 09:42)admin Wrote: You will have to edit each device separately. Each device uses a local copy of profile mapping.

That's not good at all! I have 36 devices with the same profile and now I have to edit one by one... a very wast of time! Sad

I 'll better save time deleting and recreating them with the new updated profile.


Peppe
Reply
#42
(02.04.2025, 09:17)oliver.brown.knx Wrote: I will ask for help with the following.

When changes are made in the modbus profiler in the value multiplier to 0,1, the changes are made in the json file, but the value is not changed in the group address. The change is only made when a new object mapping is made.

Example:
1. The value written in the group address (e.g. 1/1/1) is 250.
1. There is a temperature value at address 1 that is displayed as 250.
2. Modify the value of the value multiplier to 0.1.
3. The value in the group address is still 250 and will not change even if the value at address 1 is changed to 260, for example.
4. Only when we perform a new mapping does it change to 25.0 or 26.0.
5. Value delta is set to 0.001.
6. Write to bus is checked.

So is the condition that we always need to perform a new mapping when changing in json using modbus profiler?

You can try restarting it. It often works.
Reply


Forum Jump: