Modbus profiler app

[Daniel]

Please see our new Modbus profile app. Manual JSON creation is finally over.  You can easily create Modbus profiles and upload them to LM profiles. You can also edit live Modbus device and directly send changes to it. No need to remove and add devices again. The app is just profile creator/editor. Any work must be saved either to LM or as file on the PC.

   

1. Import profile of live device already added to LM Modbus tab.
   
2. Import profile from profiles in LM.
   
3. Import JSON profile from PC.
   
4. Edit device global parameters.
   
5. Save device will save it ether to live device(if live device is edited) or to profiles (if imported from profiles or JSON).
   
6. Download profile to PC in JSON format.
   
7. Link to documentation.
   
8. Link to this thread for help.
   
9. Actions - see below.
   
10. Edit local parameters of register. The same action will happen by simply clinking on register table.
    
11. Duplicate a register, see below.
    
12. Delete register.
    

   

If no register selected or only one, then only Add mapping will be visible. If more then one register is selected, then the fallowing options are present:

1. Add new registry mapping
   
2. Duplicate all selected registers
   
3. Delete all selected registers
   
4. Shift selected address by a given number
   

   

1. The number which duplicated object address will be added to original value.
   
2. If selected read_offset is changed instead of address.
   
3. Specify the text which should be replaced in object name.
   
4. Specify the text which will replace text from point 3.
   

See the documentation for description of each parameter.

Editing live devices is a new features and we highly advice to make a backup before

Installation: On the main apps screen click the + icon when logged in as admin. Click the menu in the top left side and select "Install from file". Enable "Allow to install package without signature" option.

[ivob]

Looks nice! Could you please add the signature file which is needed for installation.

[RomansP]

Just mark checkbox "Allow to install package without signature"

[myg]

If i have several devices created from the same profile, and i want to edit few parameters, what is the best approach here? If i edit profile, will it propagate to all current devices, or once device is imported it is a complete copy and i need to edit each device?

[admin]

You will have to edit each device separately. Each device uses a local copy of profile mapping.

[Erwin van der Zwart]

Cool! I like it (:

[guillermo]

Simplemente marque la casilla de verificación "Permitir instalar paquetes sin firma"

¿Dónde está ese botón? No lo encuentro.

[admin]

See Installation note in the first post.

[domotiqa]

great

[oliver.brown.knx]

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?

[admin]

Use Menu > Devices to edit existing devices.

[Chandrias]

Please see our new Modbus profile app. Manual JSON creation is finally over.  You can easily create Modbus profiles and upload them to LM profiles. You can also edit live Modbus device and directly send changes to it. No need to remove and add devices again. The app is just profile creator/editor. Any work must be saved either to LM or as file on the PC.

1. Import profile of live device already added to LM Modbus tab.
   
2. Import profile from profiles in LM.
   
3. Import JSON profile from PC.
   
4. Edit device global parameters.
   
5. Save device will save it ether to live device(if live device is edited) or to profiles (if imported from profiles or JSON).
   
6. Download profile to PC in JSON format.
   
7. Link to documentation.
   
8. Link to this thread for help.
   
9. Actions - see below.
   
10. Edit local parameters of register. The same action will happen by simply clinking on register table.
    
11. Duplicate a register, see below.
    
12. Delete register.
    

If no register selected or only one, then only Add mapping will be visible. If more then one register is selected, then the fallowing options are present:

1. Add new registry mapping
   
2. Duplicate all selected registers
   
3. Delete all selected registers
   
4. Shift selected address by a given number
   

1. The number which duplicated object address will be added to original value.
   
2. If selected read_offset is changed instead of address.
   
3. Specify the text which should be replaced in object name.
   
4. Specify the text which will replace text from point 3.
   

See the documentation for description of each parameter.

Editing live devices is a new features and we highly advice to make a backup before

Installation: On the main apps screen click the + icon when logged in as admin. Click the menu in the top left side and select "Install from file". Enable "Allow to install package without signature" option.

Great application. Thank you for the implementation.

[stianj]

I have a Grundfos circulation pump with CIM200 Modbus RTU adapter. I can read and write values just fine - but have issues with one register.

https://api.grundfos.com/literature/Grun...012947.pdf

Page 18 has this:

   

Page 36 says this:

   

(I'm pretty sure there is a typo in the "stopping" section - it should be 0 in bit 1 for stopping - which is kind of confirmed with the value being set. But that's not the point.)

I have made a profile that connects bit 0 and bit 1 to separate group adresses. This works fine - ish. Problem is that even if I have enabled bit 0 - and I can read the status in register 201 bit 8 - that remote control is enabled - when I later makes changes to bit 1 - the value of bit 0 is not taken into account. So 0x0002 is sent, which disables the remote control bit (bit 0). And thus won't let me turn the pump on or off.

Sending 1 and 3 to the register works as expected - and I understand I can make a script that does the right thing, but is it really not possible with modbus profile directly to make sure that all bits are sent to a register when using bitmask - not just the one I'm changing?

Hope this was understandable.

[admin]

Do you have "Write bitmask" option enabled for writable registers that use "Value bitmask"?

[stianj]

Thanks for your reply! Yes, I think I have. I think I have tried every possible setting...

Attached is the profile from "Modbus profiler". It's both a "work in progress" and a test-bed, so excuse the mess. It's register 100 that is the issue if you would have a look at it...

[Daniel]

Seems your device expect both bits written at the same time, in this case you should map both bits to 1 byte and write 0 or 3

[stianj]

Yeah, that's kind of what I was thinking as well. Just thought that maybe Grundfos wasn't the only device that expects all bits in one register written at the same time, and that there was a solution for this already...

---

Btw, I have two more questions.

1: Would it be possible to have a column for the group address as well in Modbus Profiler?

2: When you enter group address on a mapping, it would be nice with similar search as in other places, like Visu. That you can search for name or have choices when you start entering group address.

Actually one more thing, when you have custom values in a mapping - why would I do that? They are not visible anywhere as far as I can see?