Applying parameter "aliveTimeoutMsg 3 816" in section [mod] in "config file" cause following problem.
The edited config file has invalid entries. Please check your changes! Would you like to edit the file again?
WinCC 3.16 P011
Settings for the Modbus driver
- adaneau
- Posts:310
- Joined: Tue Feb 21, 2012 9:49 am
Re: Settings for the Modbus driver
Hi,
As any config entry, you must use = sign
So use aliveTimeoutMsg = 3 816 instead of "aliveTimeoutMsg 3 816"
BR
Alex
As any config entry, you must use = sign
So use aliveTimeoutMsg = 3 816 instead of "aliveTimeoutMsg 3 816"
BR
Alex
- atrejman
- Posts:7
- Joined: Wed Feb 22, 2017 9:20 am
Re: Settings for the Modbus driver
Thanks for your answer. it's works 
And by the way, you can tell me,
may I use different settings for each modbus drivers?
E.G.
[mod1]
aliveTimeoutMsg = 3 816
[mod2]
aliveTimeoutMsg = 3 100
till now common settings were enough for my config
[mod]
And by the way, you can tell me,
may I use different settings for each modbus drivers?
E.G.
[mod1]
aliveTimeoutMsg = 3 816
[mod2]
aliveTimeoutMsg = 3 100
till now common settings were enough for my config
[mod]
- adaneau
- Posts:310
- Joined: Tue Feb 21, 2012 9:49 am
Re: Settings for the Modbus driver
Hi,
Yes you can use different settings for different instances of the driver, I am myself using it for endianity.
Correct syntax is :
[mod_xx] where xx is the driver number. So for you [mod_1] and [mod_2]
BTW this is valid as well for any manager
.
Br
Alexandre Daneau
Yes you can use different settings for different instances of the driver, I am myself using it for endianity.
Correct syntax is :
[mod_xx] where xx is the driver number. So for you [mod_1] and [mod_2]
BTW this is valid as well for any manager
Br
Alexandre Daneau