On May 28, 2010, at 9:53 PM, PicO Aquariums wrote:
> Very nice.
Basically the controller can return any data you like to receive. It's just a matter of coding it to return that specific data, but with just this tiny piece of XML, you can basically write any mobile app to interpret that.
XML is the way to go.
For this particular code I'm using it, I coded it to do this:
http://betatest.reefangel.com:2000/ = default page
http://betatest.reefangel.com:2000/wifi = main screen
http://betatest.reefangel.com:2000/rxx = override relays, where the first x indicates the relay you want to override and the second x indicates which mode you want to override.
There are 3 values that can be used on the second x:
0 = override relay off
1 = override relay on
2 = disable override and return to auto
The return page for this is command is the XML data.
For example, if you browse to http://betatest.reefangel.com:2000/r51 you will be instructing the controller to override the relay 5 to on position.
If you just feel like peeking at the XML data, you can call an inexistent relay. I usually browse to http://betatest.reefangel.com:2000/r99
The main screen is basically an AJAX powered webpage that keeps calling r99 to gather the XML data.
I felt that a refresh every 5s was sufficient.
But, since this will be an open source code, everything is free to modify anything and everything to accommodate their needs/requirements. :)
I'm leaning towards a Roving Networks module, because it is very simple to use and comes with pretty much everything built-in. The other modules I have tried are either too expensive, or do not offer stuff I'd like to have in the attachment.
I hope this info has given you some understanding of how the controller is interacting with the wifi attachment and the possibilities that can come out of it!!! :)
Sincerely,
Roberto Imai
I got some work done this past weeks.
Here is the result:
http://i730.photobucket.com/albums/ww302/newhobby_photo/P1040887.jpg
http://i730.photobucket.com/albums/ww302/newhobby_photo/P1040888.jpg
http://i730.photobucket.com/albums/ww302/newhobby_photo/P1040890.jpg
http://i730.photobucket.com/albums/ww302/newhobby_photo/P1040893.jpg
My board is working fine and initial tests were very good.
All I have to do now is fully test it and find a supplier of the cable used.
If you could connect and let me know if you encounter any problems, I would appreciate.
http://betatest.reefangel.com:2000/wifi
Unless there is a major problem that I'd have to work on this, it's going to be attached to my Reef Angel test unit until Tuesday 06/29/10 and then I'll put back the original ugly prototype.
I don't know who it was, but someone was monitoring my unit 24/7 for about 3 weeks. If you read this, would you send me an email letting me know if you encounter any problems?
The supplier of this little cable is the hold back now. I wish I spoke Chinese :(
Roberto.
Roberto.
I wanted to inform that the wifi attachment is being manufactured and the enclosures are in the production line.
I'm expecting to have them ready to be shipped between 2 to 4 weeks.
I'll have 50 pieces available.
Please visit http://reefangel.com/order.html to place your pre-order and reserve yours.
Thank you,
Roberto.
I had a minor set back on the enclosures.
They had to be sent back to be modified.
I should have them back next week.
Roberto.
Roberto
The manual is up and when I was creating it, I realized the setting up part is a bit long and can be confusing.
Does anyone have any recommendation of a terminal emulator type of software that I could write a script to send text via COM port to the device and create a somewhat automated setup process?
Or maybe use .NET to create a GUI setup application?
Roberto.
________________________________________
From: reef...@googlegroups.com [reef...@googlegroups.com] On Behalf Of Roberto Imai [rob...@imlogo.com]
Sent: Thursday, July 29, 2010 9:08 PM
To: reef...@googlegroups.com
Subject: RE: Wifi attachment prototype
I can comment on this because I've encountered something like this at
a previous job. We had to configure some devices via serial cables
using a terminal emulator. No matter how straight-forward things
were, somebody always screwed it up and was unhappy. Once we created
a GUI and started having our program(s) do the configuration, the
happier the users were and the less troubleshooting we had to do.
So, I vote for a GUI application written in whatever you like. I'm
partial to C++ and MFC applications because that's what I wrote for
many years. Others may prefer .NET apps or other languages.
Regardless of what is chosen, something simple and straight-forward is
ideal.
This is just my 2 cents.
Curt
--
/*
* Curt Binder
*/