Well…after a year of ‘delays’ (I got me one of them ‘little human beings’ running around the house now!), false starts, ‘feature creep’, etc., I got back on the project a few weeks ago and I’m practically stumped…
To recap, here’s the system as it stands right now -
System 1 - Mobile device, vehicle mounted…tilt angles, GPS lat/long/speed, time, and others, being sampled and sent via a ConnectOne Nano WiReach module via a Mifi2200 over the 'net about once a minute. Doing this using a simple file FTP back to the main server here in my basement. Small file, about 1K total per minute.
System 2 - The server. Simple laptop running Ubuntu 8.04, ProFTP, etc. Serves up a simple page using iFrames (I know, don’t groan so loud) with basically the .txt which was sent from System #1 displayed in the middle of it, and using the Refresh metatag to update the page.
System 3 - The browser PC, wherever I am, I can pull up the page, and have a look-see at what System 1 is doing at the moment.
Problems -
-While uploading a fresh dataset file via FTP from #1 to #2, AND #3 does a Refresh, obviously #3 comes up with a dead file because the file doesn’t really exist at that particular moment on #2 since it’s being re-written. The next time the page refreshes (or I ‘F5’), it’ll likely load just fine, obviously because the file is small and it updates pretty quick.
-Once per minutes sucks…'nuff said.
-The option suggested above in which the server (#2) sends out requests to the datalogger (#1) likely won’t work since the IP address will change fairly often (Mifi2200 internet access), likely every time the system is powered up. Also, if my datasheet reading is correct, the ConnectOne Nano WiReach doesn’t support these methods of accessing files or datasets which aren’t internal to the chip itself.
I read up on AJAX as noted above and it seems to me, unless I’m wrong which is quite possible, that AJAX would work just fine for the browser (#3) and server (#2), but not between the mobile device (#1) and the server (#2). And besides, I don’t get it…which I guess is the big thing. Looks like one helluva steep learning curve there.
So, I guess I need a quick & dirty-er method to “push” data from the mobile server #1 to the server #2, which, when updated would push that data out to a browser #3, which it looks like AJAX will handle if I can ever figure it out. I know the methods are out there. Just gotta get a handle on exactly what they are called/named/whatever.