This is a question for programmers that have written their own code to interface with the VP2.
For no other reason than that I can, I wrote my own software to interface to my VP2 data logger. It's worked fine for many years but recently I decided to implement the SETTIME function and have run into a strange problem!
Normally I have the application running in the LOOP sequence, restarting each time it terminates. If I want to update the time, I wait until the current LOOP is completed. At this point there is no data being moved between the VP2 and my application. I now issue the SETTIME command, I get the ACK and then send the date/time + CRC. I get an ACK back from the VP2 and by observation on the VP2 display, I can see that the time has been set OK. So far so good.
What happens next is curious.
I send a new LOOP command but I do not get loop data back. Most times I get nothing but occasionally I get what appears to be a truncated loop response. The display on the VP2 freezes. This carries on for a while, maybe a couple of minutes, during which time I send wake-up messages and LOOP requests every 10 seconds or so. Eventually, the VP2 seems to work out what's going on and starts sending LOOP data normally again.
I have both a VP2 and an Envoy; both exhibit this weird behaviour. Have any other programmers come across this?
Many thank in advance,
John