I've created a datapoint type (type A) with a master datapoint (power configs). This datapoint type includes DPEs with periphery address power configs for modbus. I then created another datapoint type (type B) that has DPE's of the type previous created with the master datapoint. This new datapoint has a master datatpoint (power configs) of it's own.
When I look at the DPEs of type A inside the master datapoint type of type B, they look correct. Specifically, the driver number is correctly set to 2. However when I create a datapoint of type B, and check the periphery address settings for the DPEs the driver number is 1. Since there is a mater datapoint, I can't change this back to the proper number 2.
Problem with Datapoint type nested in another Datapoint type
- johna_ssa
- Posts:21
- Joined: Wed Jan 28, 2015 6:14 pm
Problem with Datapoint type nested in another Datapoint type
- Gertjan van Schijndel
- Posts:634
- Joined: Mon Aug 02, 2010 10:37 am
Re: Problem with Datapoint type nested in another Datapoint type
Which modbus power config have you configured?
Have you tried the power config option 'Transfer to all DPEs' or 'Transfer selected config...'?
Have you tried the power config option 'Transfer to all DPEs' or 'Transfer selected config...'?
- johna_ssa
- Posts:21
- Joined: Wed Jan 28, 2015 6:14 pm
Re: Problem with Datapoint type nested in another Datapoint type
I believe I am using Modbus Simple Input and Modbus Simple Output.
I tried the 'Transfer to all DPE's' yesterday and that pushed the driver number down to the DPE's and disabled the periphery address on all the related DPE's. I was able to re-enable the DPE addresses relatively easily. Things are now functional for me. I am guessing I modified the driver number in the root Master Datapoint after I created it. I don't recall the order of events.
I am a little confused when it's required to manually push the power config values down to the DPE. With other power configs on different periphery addresses/drivers, I modify a config that is not a variable (like the driver number) and those are pushed down automatically. But, I assume that's when the Data Types are not nested. I'm also confused why pushing down the config to the DPE's modified the 'active' state and not the 'reference' or other variable configs.
Either way things are now working for me.
I tried the 'Transfer to all DPE's' yesterday and that pushed the driver number down to the DPE's and disabled the periphery address on all the related DPE's. I was able to re-enable the DPE addresses relatively easily. Things are now functional for me. I am guessing I modified the driver number in the root Master Datapoint after I created it. I don't recall the order of events.
I am a little confused when it's required to manually push the power config values down to the DPE. With other power configs on different periphery addresses/drivers, I modify a config that is not a variable (like the driver number) and those are pushed down automatically. But, I assume that's when the Data Types are not nested. I'm also confused why pushing down the config to the DPE's modified the 'active' state and not the 'reference' or other variable configs.
Either way things are now working for me.