Hello,
I have two modbus drivers running, one with little littleEndianRegister=0 and another one with littleEndianRegister=1 in the config file as my polling devices are defined in this way.
But when i poll the device with littleEndianRegister=1 the values are not coming properly as it is behaving like we set it as 0.
In my config file i have put the entries in below way
[mod_1]
littleEndianRegister = 0
MaxGap = 100
[mod_2]
littleEndianRegister = 1
MaxGap = 100
Please let me know if any solution available to run 2 modbus driver at the same time and polling of data should come properly based on the littleEndianRegister.
Thanks in Advance.
Regards,
Raj
Two modbus driver with littleEndianRegister as 0 and 1 not giving value properly
Search
-
- Posts: 20
- Joined: Fri Mar 07, 2014 2:46 pm
-
- Posts: 20
- Joined: Fri Mar 07, 2014 2:46 pm
Re: Two modbus driver with littleEndianRegister as 0 and 1 not giving value properly
Hello,
Explanation in more detail
We have created two Modbus drivers for running one with little littleEndianRegister=0 and another one with littleEndianRegister=1 in the config file (like below) as my polling devices are defined in this way.
[mod_1]
littleEndianRegister = 0
MaxGap = 100
firstRequestDelay = 100
pollOptForBlob = 0
[mod_2]
littleEndianRegister = 1
MaxGap = 100
firstRequestDelay = 100
pollOptForBlob = 0
tcpServerPort = 510
Scenario#
1. We have created two devices one should communicate through driver 1 and other with driver 2.
2. Both the Modbus drivers are running.
3. Start communication and poll the device.
4. Device with littleEndianRegister = 0 communicates and retrieves the value properly.
5. Device with littleEndianRegister = 1 is not polling.
Additionally we have tried the below topics,
• Giving new poll groups for the second driver data points as suggested.
• Giving new TCP Server port number as mentioned in the help file.
Queries#:
1. Do we need any license for creating second Modbus driver the log file shows modbus = 1
2. What other settings needs to be done for communicating with second Modbus driver.
Note: If we run only one Modbus driver with littleEndianRegister =1 then the device is polling and communicating properly.
[mod]
littleEndianRegister = 1
MaxGap = 100
firstRequestDelay = 100
pollOptForBlob = 0
tcpServerPort = 510
Thanks in advance.
Regards,
Raj
Explanation in more detail
We have created two Modbus drivers for running one with little littleEndianRegister=0 and another one with littleEndianRegister=1 in the config file (like below) as my polling devices are defined in this way.
[mod_1]
littleEndianRegister = 0
MaxGap = 100
firstRequestDelay = 100
pollOptForBlob = 0
[mod_2]
littleEndianRegister = 1
MaxGap = 100
firstRequestDelay = 100
pollOptForBlob = 0
tcpServerPort = 510
Scenario#
1. We have created two devices one should communicate through driver 1 and other with driver 2.
2. Both the Modbus drivers are running.
3. Start communication and poll the device.
4. Device with littleEndianRegister = 0 communicates and retrieves the value properly.
5. Device with littleEndianRegister = 1 is not polling.
Additionally we have tried the below topics,
• Giving new poll groups for the second driver data points as suggested.
• Giving new TCP Server port number as mentioned in the help file.
Queries#:
1. Do we need any license for creating second Modbus driver the log file shows modbus = 1
2. What other settings needs to be done for communicating with second Modbus driver.
Note: If we run only one Modbus driver with littleEndianRegister =1 then the device is polling and communicating properly.
[mod]
littleEndianRegister = 1
MaxGap = 100
firstRequestDelay = 100
pollOptForBlob = 0
tcpServerPort = 510
Thanks in advance.
Regards,
Raj
Re: Two modbus driver with littleEndianRegister as 0 and 1 not giving value properly
Hello,
normally it should be possible to start several modbus-drivers in one project.
The license keyword modbus is defined as boolean 0/1 and not as a counter. If the value 1 is set the modbus-driver can be used.
Does it work if the modbus-section in the last example is renamed to [mosd_2] and only the modbus driver with number 2 is started?
Have you defined the correct manager number as startup option for the drivers?
Best Regards
Leopold Knipp
Senior Support Specialist
normally it should be possible to start several modbus-drivers in one project.
The license keyword modbus is defined as boolean 0/1 and not as a counter. If the value 1 is set the modbus-driver can be used.
Does it work if the modbus-section in the last example is renamed to [mosd_2] and only the modbus driver with number 2 is started?
Have you defined the correct manager number as startup option for the drivers?
Best Regards
Leopold Knipp
Senior Support Specialist