Today I got the basic ethernet interface working on the Uprising Controller and got the web server to work. We currently have 11 pages of configuration data available to the user.
Included in those 11 pages are three that reflect the names and values of the variables known to most through RTD. So if you are familiar with the intricacies of the Revolt product, you will be able to configure most of this controller very easily.
Of course, the other 8 pages are user friendly, so you don't need to know what motor-os-dt means.
A second method of RTDing to the Uprising Controller is in the works. Today, you have the ability to connect a serial line to the Revolt product and monitor the activity for later analysis, that remains true with Uprising. We are making available for the Uprising product, a TCP port to connect with to process RTD commands. Thus substituting the ethernet for the serial connection. What this means is that you will be able to monitor and capture data remotely......from across the world. An enhanced RTD will be necessary to take advantage of this....or write your own socket program. Then when you get stuck, you just have Adam connect to your Uprising controller from his home, in the middle of the night, in his pajamas to diagnose your problem......is that OK that I said that Adam?
And, Adam, we still have 40% of the processor's data space free and 70% of program space free. We can grow a bit.
Ok, I'm back to the bug fixing.
Eric