The most of you are collecting data with a jeelink on a PC but I have an etherNode running on my LAN reporting data from a jeeNode with roomboard. Now I like to display the data in JeeMon as mentioned in this artikel http://news.jeelabs.org/2010/03/02/jeemon-as-web-server/ . I was looking around in many topics but I can’t find out how it works. Is there anybody to help me out finding a beginning.
Ethernode data in JeeMon as web server
(35 posts) (3 voices)-
Posted 12/08/2010 10:00:03
-
Hi JoopH,
JeeMon contains the wibble package for www and server side scripting. Put this in your application.tcl and you have a www server:
package require wibble proc start {} { set root [pwd] puts $root set virtroot "" # Define zone handlers. wibble::handle /$virtroot dirslash root $root wibble::handle /$virtroot indexfile root $root indexfile index.html wibble::handle /$virtroot static root $root wibble::handle /$virtroot template root $root wibble::handle /$virtroot dirlist root $root wibble::handle / notfound puts "Starting web server at http://:8080/ ..." wibble::listen 8080 }
Put an example html file in the root dir that is printed and try to fetch it with your browser. Now you have two main things to choose from:
either you're going to use wibble templates to serve your sensory data (like described in the posting you referred to)
or your application.tcl generates a data file like a json file which is fetched in the background by your HTML pages running javascript in your browser. I personally like this approach the most.
Let me know which one you like and I'll try to post an example.
Posted 12/08/2010 12:07:55 -
To access an etherNode, you can let JeeMon act as web client - there's a "readHttp" proc in JeeMon (lib/helpers.tcl) which lets you fetch a page from a webserver, e.g. (substitute your etherNode's IP address)
puts [readHttp http://192.168.1.123/]
Internally, this uses the http Tcl command.
You'll need to re-fetch periodically (see after), and you'll need to compare the texts to extract the differences, i.e. the new entries. All of this will be simplified and included in JeeMon in due time.
I'll try to create a small demo in the coming days.
FWIW, I'm currently designing the core message bus architecture for JeeMon, on top of which things like these can be added. Getting data in or out of JeeMon is the easy part, dealing with the dynamics of it all for real-time use requires more work...
Posted 12/08/2010 13:29:09 -
Thanks for your reactions.
This is in my application file:
package require helpers
puts [readHttp http://192.168.0.249/]
Teh console is reporting this.
RF12 etherNode - 868 MHz, group 212 RF12 etherNode - 868 MHz, group 212 - configure - send packetLast 10 messages:
3123: OK 33 162 114 233 0 3124: OK 33 162 114 233 0 3125: OK 33 163 114 233 0 3126: OK 33 163 114 233 0 3127: OK 33 163 114 233 0 3128: OK 33 163 114 233 0 3129: OK 34 250 0 0 0 3130: OK 34 250 0 0 0 3131: OK 33 164 114 233 0 3132: OK 33 164 114 233 0
Uptime is 147:50:43 (StatusWindow) 1 %After this there is a fatal error
unknown subcommand "start": namespace::application does not export any commands while executing "application start"
Posted 12/08/2010 18:54:34 -
That's because you did not define a start routine which is called by JeeMon. Try putting your puts call inside a start routine like this:
proc start {} { puts [readHttp http://192.168.0.249/] }Or just define an empty start routine
Posted 12/08/2010 19:19:25 -
Hi Stef007
D:/Users/Joop/Arduino/JeeMon/JeeMon-win64/StatusWindow Starting web server at http://:8080/ ... (StatusWindow) 1 %
After this there is a fatal error couldn't open socket: address already in use while executing
Posted 12/08/2010 19:55:07 -
Thanks
Posted 12/08/2010 20:07:22 -
JoopH,
the error about the socket: you have another process running that is listening on port 8080. Another web server or another instance of JeeMon?
Posted 12/08/2010 20:33:15 -
Hi stef007,
This is my console now:
D:/Users/Joop/Arduino/JeeMon/JeeMon-win64/StatusWindow Starting web server at http://:8010/ ... (StatusWindow) 1 %
I dont now where to find the root for this html file.
Posted 14/08/2010 07:01:52 -
First of all I like to start with this but I don’t understand how to put an application.tcl together to start this. http://news.jeelabs.org/2010/02/28/a-real-time-status-gui/ When I do have a start then I can raffle it out but for now it is to overwhelming.
Posted 14/08/2010 07:11:24 -
Weblog post about this has been scheduled for next Tuesday.
The way JeeMon uses application.tcl, is that it loads the script, and then calls a "start" proc, which must have been defined inside it. Files such as application.tcl are treated as "rigs", i.e. they are auto-loaded on demand, into their own namespace, and as "ensembles". Lots of things to explain, but it comes down to loading a file "foo.tcl" in such a way that any proc called "bar" in it can be called using "foo bar ?args...?".
In short: the last thing JeeMon does after its initial setup, is call "application start". Which is why you need the file "application.tcl" with a "start" proc defined inside.
The confusion probably comes from the fact that the "application.tcl" script has to be loaded before it can be used. So any code outside of the start port will be executed during loading. But you still need the start proc to avoid an error.
Posted 14/08/2010 08:34:04 -
Tanks, I wait until Tuesday.
Posted 14/08/2010 11:02:24 -
Running the code "EtherNodePull" results in: "error in startup script"
invalid command name "log" while executing.
What do I wrong??
Posted 20/08/2010 13:29:33 -
Hm, I can't reproduce this here. Are you running "JeeMon" and "application.tcl" next to each other in an empty directory? Are you using Windows? Mac? Linux? Any more messages?
Just to be sure, I've uploaded the code I'm using to here - rename it to "application.tcl" before use.
Posted 20/08/2010 15:04:39 -
Your's is working.
1e empty dir. Yes. 2e Windows 7 Your code is working. I can send you my code but I do not see a comma deferens.
Tanks for your help.
Posted 21/08/2010 06:43:54 -
O... I found it "Log" "L" reading in capital.
Posted 21/08/2010 08:21:02 -
I'm sorry you had to type it in, I've added a link to the weblog post.
(FWIW, I'm working on some site changes which will make it much easier to share code and files - no ETA yet)
Posted 21/08/2010 09:14:19 -
That's OK. Still learning.
Now I like to find out how the wibble server works on my LAN. I do not understand where to find/locate the root. Also I like to know if this http://news.jeelabs.org/2010/03/02/jeemon-as-web-server/ works i.c.w. "EtherNodePull"
Posted 21/08/2010 13:14:01 -
The root is the argument given to "Web server", i.e. with "Web server 8080 C:/mySite", it'll be listening on http://127.0.0.1:8080/ and serving files placed in C:\mySite\
No, this code isn't ready yet to work with that web page you mention. I'm workin' on it...
Posted 21/08/2010 13:55:50 -
Ok. on my local machine.
Posted 21/08/2010 14:25:34 -
After connecting a JeeNode with room board there is this warning. I don’t know why.
13:05:07.773 event add COM3 13:05:10.129 ignored setup A i1 g212 @ 868 MHz 13:05:10.129 > rooms JeeSketch on usb-A600dW9oA 13:05:11.642 warn usb-A600dW9oA: wrong # args: should be "my ROOM id light move humi temp lobat" 13:05:11.643 einfo wrong # args: should be "my ROOM id light move humi temp lobat" while executing "my $id {}$info" (class "::JeeSketch::ListenerBase" method "onMessage" line 18) invoked from within "my onMessage id $id info $info" (class "::JeeSketch::ListenerBase" method "onReceive" line 4) invoked from within "my onReceive $text" ("try" body line 10)Posted 26/08/2010 11:34:11 -
(indenting code and output with 4 spaces is easier to read - I took the liberty of editing your post)
I suspect that you've connected the JN directly over USB with with your machine running JeeMon. I don't think that scenario has been tested yet - the way I use room nodes is remotely, over wireless. There's a JeeLink (or JN) connected to the machine running JeeMon, and it's running RF12demo.
Arghh... so much still needs to be done before this stuff works in all the (obvious, sensible) ways people want to try it out!
Then again, this should be easy to fix. Can you show what your node is sending out to USB? I.e. while connected to a serial console / terminal i.s.o. JeeMon? Looks like there's some formatting or version difference.
Posted 26/08/2010 14:11:14 -
Let me explain. The point is I do know anything about this stuff and I try to find out how it works. My machine W7 is running JeeMon. There is an etherNode connected to my LAN. Now I try to find out if it is correct what I see in JM. Therefore I connected a JN with RF12demo over USB. Now I try to connect wireless a room nood but there is only rubbish over USB. After that I connected indeed the RN over USB. And there was again rubbish.
Posted 26/08/2010 15:01:56 -
Rubbish - hm, could that be a baudrate mismatch?
Posted 26/08/2010 16:39:35 -
This is what it have to do, I think.
20:21:03.394 got OK 33 208 124 251 0
20:21:05.420 .(W9oA)OK 33 208 124 251 0
20:21:05.421 .(W9oA)->ack
But this game out for the last 20 minites.
20:22:42.170 .(W9oA) ? 141 136 240 80 51 163 159 23 182 204 118 158 48 31 247 214 50 36 211
Posted 26/08/2010 18:49:38 -
I'm sorry but in the editor the text is OK. But when I post it al the spaces are Disrepairs.
Posted 26/08/2010 19:13:48 -
put your output between empty lines, and insert at least 4 spaces in front of each - it's Markdown formatting
The "?" packets usually indicate random noise. If the receiver doesn't receive a packet for some time, it increases its sensitivity (I think - it's called AGC). So when you don't get data, you'll sometimes see such junk packets. Just ignore them.
Posted 26/08/2010 19:58:56 -
I'm still trying to make this http://news.jeelabs.org/2010/02/28/a-real-time-status-gui/ working. There’s one problem: when I connect a RN direct over USB it works. A record in the window “Readings status” is filled with data. When the same reporting is coming in wireless over JL/JN there is no reporting in “Readings status”. I can’t find why this isn't working.
Posted 31/08/2010 11:10:28 -
There is still lots of magic / undocumented stuff involved, unfortunately.
You need to use the "central" sketch instead of RF12demo on your central node. It behaves the same, but it announces itself differently to JeeMon (as "[central]" i.s.o. "[RF12demo]"). And you need to set up a "config .txt" file - there are some posts about it at
If it doesn't work, please post or email what you see in the log output.
Posted 01/09/2010 15:20:15 -
Yep. That's the trick. You do not use the "title" in the config file??
Posted 02/09/2010 18:49:35 -
Ah - no, not yet. It's basically a comment for now, to keep track which node id is which in the config file.
Posted 02/09/2010 21:41:35 -
Now I try to connect my gas meter. A node With meter.pde is there. The sensor is connected with port 1. There is no report in Readings status. Wat do I have to config in config.txt.
Posted 03/09/2010 09:17:09 -
I'm still using the 2009 version of JeeMon for collecting my own meter data, so can't help you with this right now.
Am in the process of completely redoing the way messages get collected and routed. The puzzle I'm trying to solve alongside that, is how to auto-detect new devices and make it possible to add / replace drivers for different devices without restarting the system. It's most of all a modeling/design task, i.e. handling direct connections, devices that collect packets from other devices, as well as devices which consists of a group of separate sensors and data sources (e.g. ookRelay). Once the basic mechanism works, I'll start bringing over all the currently working bits & pieces.
It's all taking longer than planned, and blocking much more other work than I had anticipated. The sort-of-good news is that I've been making some substantial progress these last weeks.
Posted 05/09/2010 20:18:15 -
"Redoing the way messages get collected and routed" inclusive collecting over ethernet??
Posted 07/09/2010 09:18:59 -
No - the EtherNodePull code in demo-ethernodepull.tcl will remain the same.
But there will be a chain of filters / transformers, to process an obscure "OK 56 243 0 200 0" packet of bytes and turn it into a set of meaningful readings, regardless whether they came via an EtherNode or via a directly connected JeeNode/JeeLink. Transport independence - this isn't doable with the current logic in JeeMon.
Basic idea:
"OK 56 ..." - oh, that's on 868 MHz net group 5 ... let's look it up: aha, a room node in the kitchen "ROOM-RF12 56 ..." - ah, we need to run the "ROOM-RF12" packet decoder and generate a "ROOM" message "ROOM ..." - now run the "ROOM" handler, and interpret those 4 values as kitchen light/motion/temp/humid
Incoming packets generate events, which get tagged with info about the device that picked them up (ethernode ip address, JeeLink band/group, etc). The "OK" event then triggers an "OK" handler, which generates another event (or more than one, or none). These events in turn trigger new handlers, etc - until the process stops, producing a set of "readings".
This isn't JeeNode-specific, I'm just using that as example. Anything that can be connected and has a little driver for it to turn incoming data into events will be able to use the same mechanism. There's a lot more going on behind the scenes, email me if you'd like to look at some early docs and code.
Posted 07/09/2010 12:05:11