Modbus profile automatic mapping with GA

[fleeceable]

Hi!

I have made additional modbus profile tool to make integrations faster. 
I import other controller xml file into my tool and it makes LM modbus profile. 
I can import that modbus profile to another tool to make GA-s esf file what I can import to LM with same names and correct datatypes.

Right now I need to add mapping for modbus device and group addresses manually.
Is it possible to make additional script what takes modbus datapoint name (from profile) and then tries to find variable with same name (from LM). If found then it gonna link this variable group address to element from modbus device?

Most time consuming is to link these manually in whole proccess when making integrations.

Big thanks if this is possible!

[Daniel]

I'm guessing you spend a lot of time on this but did you see this?
https://forum.logicmachine.net/showthread.php?tid=5911

[fleeceable]

I'm guessing you spend a lot of time on this but did you see this?
https://forum.logicmachine.net/showthread.php?tid=5911

I'm using my tool about few years from now. 
LM Modbus Profiler was nice update from you guys to edit live devices and make minor changes from profiles. But to create new modbus points, it still needs that name and address is defined manually. Lets say I have 10 devices with 50 custom datapoints then it takes quite a lot time to input everything. 
If you guys want I can share privately what I've done. Maybe there is something what LM team wants to integrate into Modbus profiler.

Since I try to optimize every my step in programming then my goal is to make custom integrations within 1-2min even with 100+ modbus points.
 
damn, I didn't see the "bus_address" in manual. That's the key...

[Daniel]

You can share it via PM, we are always eager to learn and if possible to improve our tools.

[AEK]

I'm guessing you spend a lot of time on this but did you see this?
https://forum.logicmachine.net/showthread.php?tid=5911

I'm using my tool about few years from now. 
LM Modbus Profiler was nice update from you guys to edit live devices and make minor changes from profiles. But to create new modbus points, it still needs that name and address is defined manually. Lets say I have 10 devices with 50 custom datapoints then it takes quite a lot time to input everything. 
If you guys want I can share privately what I've done. Maybe there is something what LM team wants to integrate into Modbus profiler.

Since I try to optimize every my step in programming then my goal is to make custom integrations within 1-2min even with 100+ modbus points.
 
damn, I didn't see the "bus_address" in manual. That's the key...

bus_adrdress does not create new knx object, only make mapping, if it exists

[fleeceable]

I'm guessing you spend a lot of time on this but did you see this?
https://forum.logicmachine.net/showthread.php?tid=5911

I'm using my tool about few years from now. 
LM Modbus Profiler was nice update from you guys to edit live devices and make minor changes from profiles. But to create new modbus points, it still needs that name and address is defined manually. Lets say I have 10 devices with 50 custom datapoints then it takes quite a lot time to input everything. 
If you guys want I can share privately what I've done. Maybe there is something what LM team wants to integrate into Modbus profiler.

Since I try to optimize every my step in programming then my goal is to make custom integrations within 1-2min even with 100+ modbus points.
 
damn, I didn't see the "bus_address" in manual. That's the key...

bus_adrdress does not create new knx object, only make mapping, if it exists

Yes, I know. I have tool what allows me to download ESF and json profile based on modbus points. With ESF file, group addresses are imported to LM. With json profile I can import profile where mapping is already done to GA-s what is in ESF.
I import two files (esf and json profile), create modbus device and datapoints are already mapped.