New MX setup

[92merc]

That number somehow flipped back to 3. I have the Log Interval just below the COM port setting, set to 15 minutes.

Here is the most recent log. Just shows FTP errors. Which I don't have anything configured in FTP yet since I still have Version1 up and running.

[steve]

The value 3 for that setting is equivalent to 15 minutes.

To get rid of those ftp errors, turn off all of the realtime ftp settings.

Then turn on debug logging and data logging by editing Cumulus.ini - see the instructions - and start Cumulus. It looks like VVP just isn't responding at all.

[92merc]

Well, now I'm totally confused. I added the Logging=1 to the bottom of the [Station] section. Didn't add the data logging option. Restarted MX and got this error. Tried adding in both logging options. Still got the error. Took both of them out. STILL getting the error. So now MX won't run at all.

[steve]

The connection to VVP isn't working.

[92merc]

I'm beginning to think there is something wrong with VVP. After restarting VVP, I got MX up and working back to Normal Running again. I let it run for awhile. See a lot of LOOP 50 attempts in the log file. So I am attaching it.

If it isn't something obvious to you, I'm thinking it'll be easier for me to get my last few bugs worked out in my Saratoga templates. Then shut down all of my old stuff and let Cumulus1 talk directly to COM1. Then just migrate over to MX.

From what I've read, I can transfer the data I've received from C1 over to MX. Then setup MX with basically the same configs as C1.

[steve]

While VVP is a very good, and unique product, it is out of date, and no longer supported, and there are a number of known issues wth it, all of which go to explain why it is now free. That's not to say that there may not be issues with MX, but MX does seem to work fine when talking directly to a console. I haven't tried MX with VVP, nor am I able to, so can't offer much help with any issues while using it.

[92merc]

And there really isn't much to configure in VVP. Basically you chose the input port. Then there are four IP Consoles. You choose whether you want it restricted to 127.0.0.1 IP or allow other PC's in the subnet to access it. Port number itself. And "protect console" checkbox if you want to allow programs such as Weatherlink to change settings on the console.

It's usually just worked for me. Oh well. MX will happen. Just a matter of timing. VWS is pretty much dead in the water. Cumulus has the features I need and nothing more. I like KISS where possible. Thanks for the help.