more quick actions
minimize quick actions
Communication interfaces
7
Posts
4
Users
0
Likes
47
Views
Hi All,
Does anyone know how to implement automatic backfeed restoration in PcVue? I tried on our trend viewer and i noticed that the historical data is based on the real time value logged when the communication between the rtu and supervisor is online. I'm still figuring out how to replace the logged data by the data stored from RTU when the communication goes offline through dnp3 automatic backfeed features by the time the communication resumes since dnp3 has it's own time stamping.
I also want to ask do we have any configuration on DNP3, that the value or data we recieved should be floating point, swapped ft. etc. as i encounter one scenario where rtu is passing raw value(2 words) and i need to convert it to swapped floating point to get the actual value readable by the end user same as modbus tcp.
Kind Regards,
Michael
Posted : 01/02/2016 6:08 pm
Hi Michael,
I requested from Cesar replying to your questions. Personnaly I dont have knowledge on DNP3 but I guess the replies to your requests will be: Cannot and cannot 🙁
Nico
Posted : 02/02/2016 9:20 am
Hi Nico,
Thanks, i'm thinking of a way to extract the data on rtu device through dnp3. There should be some command registers on the RTU in order to pass us their logged data from their own memory. I need to browse for the file type then if it's not encrypted i could find a way to extract it, On excel type etc. then i'll just display data on datagrid on our PcVue side. From there i can use an activex chart for visualization. Program will run by event when the communication comes back online. I'll check.
Regards,
Michael
Posted : 02/02/2016 11:35 am
Hi Michael,
We are working on the implementation in PcVue concerning historical data with its own time stamp. This will affect many protocols (eg. 61850,IEC104 and DNP3). At this time (and with any 11.0/11.1 version after September 2015) you can manage 'binary variables' with Timestamp very straight forward, getting values and timestamp from the device and they are stored in the historical data for only LOGLISTS with the timestamp from the device. Trend chart is with PC Time unfortunately.
(we are dealing with the implementation of this because if the connection is lost and comes back later...how do you represent it on the trend chart? your last point is earlier than the NS status, so your chart will always show NS until you get a value with a NEW Time stamp after the NS.... one option is remove completely the NS, but you will never know about the comm lost, and there are many other questions... no perfect solution found for the team until now).
Buffered data in devices which are sent once the Scada is reconnected is no managed at the time unfortunately, only the latest value is updated in PcVue.
Kind regards
César Bastidas
Posted : 02/02/2016 8:31 pm
Hi Cesar,
Thanks, ill just wait then. for the meantime, ill try some workaround..
Thank you and Best Regards,
Michael
Posted : 10/11/2016 12:34 pm
Hi Cesar
With PCVUE 12 is it still the same ? We can only log binary variables when they are sent by the RTU after the re-connection ?
Do we need to configure something special ?
Posted : 19/11/2019 9:52 pm
Hi
Did you find a workaround...and if yes could you tell us please ?
Posted : 19/11/2019 9:53 pm