I still have a number of questions about this new product. I think it's a good idea, because many people have asked for the ability to connect the console via ethernet because they don't have or don't want a computer where their console is. For people that have or will have their computer near the console, I'm not sure how many will want to spend the $130 extra for that.
One of the things I'm curious about is the part about downloading data to multiple computers. This sounds like they're putting in functionality like what VirtualVP provides.
Other questions have to do with their direct CWOP submission. I'm hoping they will also improve the data that gets submitted vs. the current state of WeatherLink (only sending the rain since midnight and not the more important 24 hr rain for example).
Some more good news in this (unless you are an author that has to do the work) is that weather programs will likely now have to support direct TCP/IP connection to the console to support this new data logger. This would be great. VirtualVP supports it going out already, and VPLive supports it as an input. It's just so much cleaner than serial, and would eliminate the need for the virtual COM port driver. I just hope they don't invent a new protocol at the same time. It would be nice if it was a straight conversion from serial to TCP/IP like what I did for VirtualVP and VPLive.
Bottom line for me is that it will probably take away some potential VirtualVP sales, but for people that will be connecting to a computer anyway, and will be running non-WeatherLink software, $30 for VirtualVP is a lot cheaper than the extra $130 that this new data logger costs vs. the serial version.