VVP stopped reading data after saying "Console did not understand command"

Hi,

I have a new Vantage Pro with USB connection. This night, at 5h22 it stopped receiving data from the console. At the bottom was a message displaying that the console did not understand a command. After restarting VVP, everything worked normal again.

Does someone know what this could cause? I use VWS (com 6), Weather Display (com 7), WsWin (com 8), WeatherLink (com 9) and Live VP (TCP/IP).

Which program gave the “console did not understand” message? If it was VirtualVP, could you look in the log.txt file and see what the exact text of the message was?

Steve

I’d like you to give you the log file, but it does not exist… How can I create one?

Regards,

What Version of VVP are you using ?

If it’s 1.2.3 then . . . . . from the web site…

“What’s new in version 1.2.3
VirtualVP now uses the user data folder (Users{username}\AppData\Local\SoftWx\VirtualVp) for all files to which data is written instead of the VirtualVP installation folder in order to function better on Vista and Windows 7 computers.”

Have you looked in there rather than the VVP install directory ?

regards
Dave

Ok, found it :slight_smile: I’m using version 1.2.3

Here the last part of the log file:

19/01/2010 18:18:15:957 Bug - TVpCom.BeatNotify: VpConsole: Wake Up Console pkt not enabled
19/01/2010 18:18:15:957 Warning - VpConsole: No response after several retries for Wake Up Console
19/01/2010 18:18:15:957 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:16:067 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:16:504 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:16:942 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:17:379 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:17:817 Warning - VpConsole: No response after several retries for Get Live Sensor Data
19/01/2010 18:18:17:864 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:17:926 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:18:145 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:18:364 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:18:582 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:18:911 Bug - TVpCom.BeatNotify: VpConsole: Wake Up Console pkt not enabled
19/01/2010 18:18:18:911 Warning - VpConsole: No response after several retries for Wake Up Console
19/01/2010 18:18:18:957 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:19:020 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:19:239 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:19:457 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:19:676 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:20:004 Bug - TVpCom.BeatNotify: VpConsole: Wake Up Console pkt not enabled
19/01/2010 18:18:20:004 Warning - VpConsole: No response after several retries for Wake Up Console
19/01/2010 18:18:20:004 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:20:114 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:20:551 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:20:989 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:21:426 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:21:864 Warning - VpConsole: No response after several retries for Get Live Sensor Data
19/01/2010 18:18:21:911 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:21:973 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:22:192 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:22:411 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:22:629 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:22:957 Bug - TVpCom.BeatNotify: VpConsole: Wake Up Console pkt not enabled
19/01/2010 18:18:22:957 Warning - VpConsole: No response after several retries for Wake Up Console
19/01/2010 18:18:23:004 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:23:067 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:23:286 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:23:504 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:23:723 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:24:051 Bug - TVpCom.BeatNotify: VpConsole: Wake Up Console pkt not enabled
19/01/2010 18:18:24:051 Warning - VpConsole: No response after several retries for Wake Up Console
19/01/2010 18:18:24:051 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:24:161 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:24:598 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:25:036 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:25:473 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:25:911 Warning - VpConsole: No response after several retries for Get Live Sensor Data
19/01/2010 18:18:25:957 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:26:020 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:26:239 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:26:457 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:26:676 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:27:004 Bug - TVpCom.BeatNotify: VpConsole: Wake Up Console pkt not enabled
19/01/2010 18:18:27:004 Warning - VpConsole: No response after several retries for Wake Up Console
19/01/2010 18:18:27:051 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:27:114 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:27:332 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:27:551 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:27:770 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:18:28:098 Bug - TVpCom.BeatNotify: VpConsole: Wake Up Console pkt not enabled
19/01/2010 18:18:28:098 Warning - VpConsole: No response after several retries for Wake Up Console
19/01/2010 18:18:28:098 Error - VpConsole: Too many consecutive failures of console to respond. Will continue trying periodically.
19/01/2010 18:18:28:317 Error - Het apparaat herkent de opdracht niet.
19/01/2010 18:46:13:212 Error - Het apparaat herkent de opdracht niet.

I’m using the USB version to connect to my console (not direct USB, but USB to a virtual COM-port) The console firmware is 1.82 (latest)

PS: “Het apparaat herkent de opdracht niet” means “The device doesn’t recognize the command” (Have Win XP Dutch installed)

Regards,

Koen

Hi Steve,

Did you had a chance to see what the problem is? I have this now a few times a day, sometimes there is only 30 minutes between the errors. If you need more info, let me know.

Regards,

Koen

For some reason I was thinking you had WL connected to VVP via TCP/IP, and that is the test I started yesterday (it’s been running without error). My normal configuration is WL connected to VVP via a virtual COM port, and that runs without error for me on my main weather station setup, and has been for quite a long time. Just on the off chance that I’m running a development build of VVP, I’ve installed the version that’s on my website, and I’ll keep running with that and see if anything changes.

The error you’re seeing in your native language is not generated by VVP. It is a Windows error that is occurring during one of calls VVP makes into the operating system. That’s one of the reasons I’d like to recreate it, so I can see the exact english text of that error and look up what generates it.

Steve
SoftWx

Hi Steve,

Thank you for testing. Most of the time it is possible to recreate the error. When I change the monthly and rainly rain total (I increased it because they where all set to 0 as I began measuring whith a new installation) the error was displayed a few minutes after it. Sometimes it wasn’t, but most of the time it was. I also checked “protect console” for WL and all the other porgrams, except for VPlive because I let it update the barometer readings every 5 minutes and synchronize the console time with my PC.

At the moment I stopped WL and unchecked the 5 min. barometer update and synchronize console time in VPlive. I hope to eliminate the problem this way. VVP ran now for 12 hours without complaining. Yesterday it ran 22 hours until the error appeared.

Before, on a previous installation, I had never this issue. I had a VP1, serial with the same programs running (only, the versions now are newer).

Concerning WL: I’m using version 5.9 and used the USB to serial driver which was provided on the CD-rom of WL. I assume it is the most recent one.

It is a Windows error that is occurring during one of calls VVP makes into the operating system. That's one of the reasons I'd like to recreate it, so I can see the exact english text of that error and look up what generates it.

It may be not the exact words for what you should get when the error appears, but the word in Dutch mean “The device doesn’t recognize the command”. I’m wondering what device XP is pointing to. The console? VVP? One of the weather programs?

Regards,

Koen

Ok, some more info. I had this error again this morning at 9:07. It’s not WL related because the program was not running. Maybe it’s VWS, I use version 14.01 I can try to install a previous version to see if that resolves the problem…

I installed a previous version of VWS (12.08). Everything ran fine for about 25 hours. Then, again… The same fault message. I gues it’s not related to one of the programs, but VVP itselves. Can you make the possibility to reset the com port, or let VVP restart when such a message arrives? Restarting resolves it, until the next error…

Koen, Steve,

Is there any progress in this matter because i have (i think) the same problem.
Another error i saw in the log VVP was: apro exception.

I have VVP 1.2.3 (and WL 5.8.2) installed on a windows 2003 Home Server system, don’t know if this has anything to do with my problem.
On another pc i have Cumulus running (but this was not running when the error occurred).

Whenever this problem occurs (every couple of days) i just have to restart VVP and everything works fine again.

Another thing i noticed was that when this problem arises i cannot reconnect after a disconnect (the menu item stays Disconnect), so i have to restart VVP

Maybe i should start another thread but i think this is the same problem.

Thanks lou

Hi lou,

Steve tried to generate the error, but until now I had no reaction from him, so I suppose he didn’t find a solution at this moment. I wrote an application which closes VVP when this happens and I let StartWatch monitor VVP which restarts it after it has closed. This works fine this way, but VVP has to be restarted every few days.

I hope Steve will find a solution for this.

Regards,

Koen

Thank you Koen for your reply.

This morning i have replaced N8VBvCOM with com0com, maybe that this will solve it.

If not than i will use windows scheduled task to restart VVP once every day

Lou.

Hi Lou,

I did the same, without any luck… I hope it works for you but I doubt to it. Which message appears in VVP with you? Is this in English? Steve wanted to know the exact message in English, but mine gave it in Duch because my OS is Duch.

Regards,

Koen

These types of problems can be hard to solve when I’m not able to duplicate them. However, I’m hoping that the more robust communications code of the new version of VVP I’m working on, rewritten in C#.NET will alleviate these sorts of communications problems.

I will need to make one more version of the current VVP though, to add support for the new LOOP command present in the latest console firmware.

Steve