We do have some error codes, but it would just need to be extended a bit. I don't think we have one for BAD (we still receive data but the source has marked it bad).
Timestamps I think are definitely a good idea, especially if we eventually DNP3. On Fri, Mar 5, 2021 at 5:39 PM Łukasz Dywicki <[email protected]> wrote: > You have response code for each individual field which allows you to > determine state (OK, REMOTE_ERROR etc.). Same information should be > available also for subscriptions. > > Best, > Łukasz > > On 05.03.2021 21:04, Andreas Vogler wrote: > > Ah, forgot: and is there a status available? Valid/invalid/good/bad > indicator of a plc value? > > > >> On 05.03.2021, at 21:02, Andreas Vogler <[email protected]> > wrote: > >> > >> Hi, > >> > >> How can I get the source time of a PlcValue? > >> > >> a) from a subscription PlcSubscriptionEvent > >> b) from a read request PlcReadResponse > >> > >> Best regards, > >> Andreas > > >
