Add system.device.setDeviceProps function to change properties of a device (to communicate to Siemens 400H)
planned
s
stefano.tagliapietra
Up to version 7.9.2 the only function available to change device parameters is:
system.device.setDeviceHostname(deviceName, hostname)
This way, only ip address (hostname) of a device can be modified. It would be useful to have a function like:
system.device.setDeviceProps(deviceName, deviceProps)
to change other properties of a device.
This would be very useful to manage a redundant communication to a Siemens 400H changing parameters hostname (ip address) and rackNumber through scripting in case of a communication fault.
Log In
Kathy A.
planned
Kathy A.
We're planning some enhancements for 8.0 that should get you what you want here.
L
Lynn.Martineau
Also, please add device Description to the properties that can be changed via setDeviceProps or applied via system.device.addDevice when creating devices.
After adding dozens of devices with a generic naming convention, the description is very useful in finding the device you want but updating the description has to be done manually, one-by-one after the devices are created.
s
stefano.tagliapietra
We could communicate with a redundant 400H if there was a script function to change the rack number. Unfortunately, there is just the possibility to change the address. I don't see the problem to add another function to change any other parameter, there should be no technical issues.
I hope my idea gets some votes and will be implemented soon...
l
lionel MAZEYRAT
Yes, s7 400h is a bit tricky and not really possible with ignition s7 driver.
Need to minitor 2 devices with a different ip and rack number.
Mimic the kepserver media level redundancy to anage the failover between 2 redundant device, s7 r other plc redundant with 2 distincts ip would be great !
l
lionel MAZEYRAT
the more generic and powerfull solution for the redundancy of device or the redundancy of driver would be able to add a new couple opcServer/opcItem for each tag with a rules like take better quality.
The tag provider will have subscribe to 2 devices on the seame opc server or the same device from 2 opc server. The valued of the tag will be the "better" one.