I see that the Master.cs input switch has a case time sync, but that results in a [NO_FUNC_CODE_SUPPORT] from the outstation. #344
-
I'm not new to DNP3, just to your library. I will say that my last deep dive into the protocol was many years ago, so the various group numbers and specific byte patterns are out of my head at the moment. Apologies ahead of time for stupid or nonsensical questions. I'm currently prototyping an outstation that will essentially maintain a database table for outside access of the binary value collection's states. I see that the "lts" input to the master CLI causes a RecordCurrentTime, Write, and then g50v3 in the outstation but then I see the [NO_FUNC_CODE_SUPPORT] response and an error in the master CLI. Is this a bug in the example or is there code that I need to implement to complete the exchange successfully? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Hi @mattheweby. Which example (language) are you using? I can then point you in the write direction. I believe that, by default, the outstation examples all reject time write requests. |
Beta Was this translation helpful? Give feedback.
-
Change this method to return There's a section in the docs here that discusses what is happening: https://docs.stepfunc.io/dnp3/1.5.2/guide/docs/api/outstation/application#time-synchronization Our library will NOT change the system clock. It's up to you to do so or reconcile a clock with the time received via DNP3 and then apply a calculated time when updating the database. |
Beta Was this translation helpful? Give feedback.
-
No problem at all. Reach out as you have questions. |
Beta Was this translation helpful? Give feedback.
Change this method to return
WriteTimeResult.Ok
:dnp3/ffi/bindings/dotnet/examples/outstation/Program.cs
Line 23 in 7f8bcf1
There's a section in the docs here that discusses what is happening:
https://docs.stepfunc.io/dnp3/1.5.2/guide/docs/api/outstation/application#time-synchronization
Our library will NOT change the system clock. It's up to you to do so or reconcile a clock with the time received via DNP3 and then apply a calculated time when updating the database.