Hi,
Given that I have not a moteino, I installed the Gateway on Rpi using the steps described in your great tutorial.
Terminated installation I log in to the site using username and pw defined in the tutorial.
Just after login I get a mask that says 'Waiting for socket connection ..'.
My question is:
It remains pending because there is not moteino connected to rpi or there is something else to launch ?
What is the program to launch after installation and/or a Rpi reboot ?
Thanx
Mauro
@andromeda - No, something is wrong with the socket.io setup. My setup loads up after that "waiting for socket connection"...now at least. I had the same issue, where I had a Nimbits server running on 8080 so I changed the socket.io configuration, but I missed the reference in the gateway.js script. Once I fixed that one it fully loaded.
I believe there are two references to the socket.io port. One in the "gateway.js" (as I mentioned) as well as the "/etc/nginx/sites-available/default". Check those...
Did the chat application that Felix used to test the configuration work for you?
--Jim
Did you start the gateway.js with: node gateway.js & ???
Quote from: fpaliuc on May 10, 2015, 04:38:12 AM
Did you start the gateway.js with: node gateway.js & ???
That's the point.
Following installation here http://lowpowerlab.com/gateway/#pisetup (http://lowpowerlab.com/gateway/#pisetup) and here http://lowpowerlab.com/gateway/#sourcecode (http://lowpowerlab.com/gateway/#sourcecode) I haven't seen anything regarding how to launch or use gateway.js.
I have only seen it here http://lowpowerlab.com/blog/2013/10/11/raspberrypi-home-automation-gateway-hardware-and-demo/ (http://lowpowerlab.com/blog/2013/10/11/raspberrypi-home-automation-gateway-hardware-and-demo/) :
chmod 755 nodejs-moteino.sh
sudo update-rc.d nodejs-moteino.sh defaults
That launch gateway.js at startup.
So, did the gateway.js have to be launched at startup and I have to use the
nodejs-moteino.sh shell script to do it or the gateway.js is launched by something else ?
Thanks
Yes you need to run the command node gateway.js & from the directory where gateway.js is located, then try connecting to the site via your browser.
The ampersand at the end makes the process run in the background until you logout.
P.
Good news: gateway guide was updated (http://lowpowerlab.com/gateway) and a link to a completely setup and ready to go Pi image was posted here (https://lowpowerlab.com/gateway/#sourcecode). It includes the web stack install and also all the files with some sample node data so it should run out of the box and you should not have much else to do except perhaps change passwords for the Pi and for the web auth (which you should actually do to make it secure). If you want to send email/SMS you need to put your email and mobile settings in gateway.js.
Let me know if there is any issue with it.
Enjoy!
Hi,
The link to it image seems broken ?
Can you check it please?
Thanks
Sorry please try again now!
Tomorrow I'll receive WeatherShield and some moteino.
I have downloaded rpi image and installed succesfully.
I think that to build the gateway infrastucture I need to start with a moteino (usb version) conneted to rpi and another moteino Connected to the WeatherShield.
But what I have to load to the usb(gateway) moteino connected to the rpi and what I have to load to the moteino with WeatherShield to communicate with the rpi gateway ?
Thanks a lot
Andromeda
Hmm, I just realize I didn't publish any example that is exclusively using WeatherShield.
I published others that combine their code with WeatherShield readings, for instance the GarageMote (https://github.com/LowPowerLab/RFM69/blob/master/Examples/GarageMote/GarageMote.ino). You can look at how that code is reading the data from the WShield. I may publish a sketch for WS only sometime.
Also notice the graphHelper.js is missing in the /var/www/default and I will re-publish an image that has that fixed, in the meantime you can copy it manually from the Github repo.
Quote from: Felix on May 17, 2015, 10:51:48 PM
Hmm, I just realize I didn't publish any example that is exclusively using WeatherShield.
I published others that combine their code with WeatherShield readings, for instance the GarageMote (https://github.com/LowPowerLab/RFM69/blob/master/Examples/GarageMote/GarageMote.ino). You can look at how that code is reading the data from the WShield. I may publish a sketch for WS only sometime.
Also notice the graphHelper.js is missing in the /var/www/default and I will re-publish an image that has that fixed, in the meantime you can copy it manually from the Github repo.
That's not a problem.
I have seen that inside GarageMote and MailboxNotifier there are weatherShield parts that can be extracted.
What I mean is what I have to load (which .ino ?) in gateway moteino and in the remote moteino nodes to communicate to the rpi gateway.
Or what is the protocol lto use to communicate with gateway.
Thanks
Sorry for the confusion, here's what you should load on your Gateway Moteino: https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway
That sketch passes data from your network to your Pi via the serial port, and passes data from your Pi to your remote nodes also (ie open garage or turn ON a light etc).
There are 2 sketches there, the second uses a newhaven i2C LCD to display the incoming messages right at the Pi, which is something I've always prefered to have. If you don't have that just load the first sketch.
No problem.
Now I know what to load to gateway moteino, but on the weathershied moteino I have to load something else that I can create myself, but what the gateway expect to receive ? which string/protocol etc...
Have I to see how you implement other nodes inside metrics.js and gateway.js files to define something else ?
There is some documentation on gateway string expectation ?
Thanks a lot
Andromeda
For now since there is no dedicated sketch for WeatherShield you can add the code from GarageMote to the Node sketch and just send the weather data to the gateway.
The tokens for the weather shield are defined in metrics.js (https://github.com/LowPowerLab/RaspberryPi-Gateway/blob/master/metrics.js) so if you don't change how that data looks like the data will automatically appear for your node when the data is received, then it gets updated and logged.
For testing purposes you could even just use the Node sketch or any other, and change the message to send something like F:67.89 or H:35 or P:123, or all those in 1 message separated by spaces.
Felix,
By chance is the Newhaven 20X2 LCD display sold by Jameco (see below) with a ST7036 controller appear to be the same as the LCD you referred to? The two links to driver sources commented in the includes section of the Sketch (ST7036.h and LCD_C022OBIZ.h gave me 404 errors when i went to check them out. I too want to be able to view the sensor data as it arrives at the Pi serial input.
http://www.jameco.com/webapp/wcs/stores/servlet/Product_10001_10001_2118539_-1
Quote from: Felix on May 18, 2015, 10:27:08 AM
Sorry for the confusion, here's what you should load on your Gateway Moteino: https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway
That sketch passes data from your network to your Pi via the serial port, and passes data from your Pi to your remote nodes also (ie open garage or turn ON a light etc).
There are 2 sketches there, the second uses a newhaven i2C LCD to display the incoming messages right at the Pi, which is something I've always prefered to have. If you don't have that just load the first sketch.
Yes they appear to be the same.
I completed the Rpi as designed with no significant errors. The only exception that the chat session worked but the console output in the ssh terminal did not show the debug messages, only the authentication messages. I completed the Pi Setup Guide with no apparent errors.
I completed the Source Code Setup page with no errors, but I got the same blank gateway home page as the original poster, "Waiting for socket connection".
I tried running gateway.js again and got the following errors:
pi@raspberrypi ~/moteino $
module.js:340
throw err;
^
Error: Cannot find module 'nedb'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/home/pi/moteino/gateway.js:64:17)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
<CR>
[1]+ Exit 8 node gateway.js
Perhaps gateway.js has not completed?
Another question, what html is being referred to on the Gateway Source Code page http://lowpowerlab.com/gateway/#sourcecode (http://lowpowerlab.com/gateway/#sourcecode)
QuoteOnce that is done, you can get the HTML interface to the garage door, and copy it to your /var/www/default directory you created in the last post (copy these files: index.php, icon.ico).
The referenced link takes me to the Github Pi-Gateway files where I cannot find anything related to garage door.
Rick
Looks like you're missing the nedb install?
cd ~/moteino
sudo npm install nedb --save
The paragraph you mentioned was copied in error from a previous guide, please ignore it. The link to the files is here (https://github.com/LowPowerLab/RaspberryPi-Gateway/blob/master/index.php).
You nailed it, Felix. Thanks!
As I recall, there was an error with the nedb install when I installed socket.io and I fixed it with this from an earlier post in this forum. After getting through that, I must have skipped nedb and nodemailer.
pi@raspberrypi ~/moteino $ sudo npm install nedb --save
sudo: npm: command not found
Quote from: ssmall on May 05, 2015, 01:51:59 PM
I have same issue. npm is not set up in my PATH correctly.
Try this:
cd ~/moteino
which npm // This should give you the path to npm. In my case it's: /opt/node/bin/npm
sudo /opt/node/bin/npm install nedb --save // instead of just npm use the path that came back from which: /opt/node/bin/npm
Great, so is it all working now?
QuoteGreat, so is it all working now?
Not yet, letting the brain cool down for a few minutes, though.
I thought it started working, at least the home page showed connected, but I don't have any nodes running so the page was empty.
Gatewaylog.db shows
{"$$indexCreated":{"fieldName":"n","unique":false,"sparse":false}}
{"$$indexCreated":{"fieldName":"m","unique":false,"sparse":false}}
I did not make any changes and it later quit working. I am now back to
https://192.168.1.12/ showing waiting for a socket connection.
I am learning a lot here and feel I am real close to having this setup working. Could someone provide a quick checklist of services and dependencies to check and the method of testing?
Also, I have a GarageMote that communicates with the Gateway moteino when connected by serial and Arduino serial monitor.
When connected to the Pi gateway, The GarageMote flashes like it should, but there is no led activity on the gateway moteino whatsoever. From the Pi terminal, minicom displays "promiscuous mode", sketch set to false. Seems at one point I sent a "r" relay check from minicom and got a flash memory dump. Shouldn't I have seen the same communication I did from Arduino?
Rick
There are so many moving parts in this setup that it's hard to type a list on every post where something isn't working. The gateway stack setup guide I wrote has all the steps along with explanations of everything and everyone who wants to really understand the hows and whys of all this should go through it at least once.
"Waiting for socket connection.." means your page is loading but your socket is not. It means the gateway.js script might not be running (or something is blocking it which is less likely). The guide has the details of to run that and how to make it run at boot and also how to run it manually and have it not die on you when you logout of SSH. Looking on the page for any js errors might also help explain things (F12 in chrome/firefox etc).
Manually run the script like this and it will persist after logoff:
nohup node gateway.js &
The code for the gateway moteino should be this: https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway
That will forward the packets from the wireless network to your Pi's serial port, and also back to your listening nodes from the gateway UI.
I guess walking away from it for a while is what I needed!
When I started it up and logged in, I was able to start node with gateway and it worked again. I will swear I had tried it many times before, but we won't argue with success.
I tried to build my GarageMote and gateway about two years ago and put it away when I could not get it to work. I have built the Pi from the ground up at least six times now and I have most of the pages almost memorized now. I am getting closer to the big picture, bus as you say, there is a lot going on here. Thanks for your comments on gateway.js, it probably was not running.
I now have the two GarageMote moteinos talking to the serial ports but not through the radios. The gateway side just shows
"Listening at 433 Mhz...
SPI Flash Init OK. Unique MAC = [D7:63:3C:48:4F:30:8D:2D:]" and does a hex dump when I input a "r" for relay test.
Since I have the problem solved related to this thread, I will start a new one if I don't make progress soon.
Thanks for the help!
Ok great. Regarding the gateway moteino again...
The code for the gateway moteino should be this (be sure to adjust the settings in the sketch to match the radio hardware): https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway
That will forward the packets from the wireless network to your Pi's serial port, and also back to your listening nodes from the gateway UI.
I assume you know that the radios should all have the same frequency, same network ID, unique node IDs, the gateway should be ID=1. Then you can expect the nodes to talk to your gateway and listen for commands from it. A simple node activity like garage open/close should pop that node in the UI of your gateway. Then you can select the node type (garage Mote) and you should see the OPEN/CLOSE button.
Quote from: Felix on June 22, 2015, 12:50:47 PM
A simple node activity like garage open/close should pop that node in the UI of your gateway.
Where should I look if this doesn't happen? I do see some entries in gateway_nonmatches.db
Rick
If you start gateway.js manually (node gateway.js) it will show any serial activity on the SSH console in that same session, so you can see any serial messages.
Otherwise use minicom or any other serial console to talk directly to your gateway moteino the same way you would do on your PC's arduino serial monitor.
I'm stuck at the same place as Rick. Let me list a few things on where I stand.
Gateway fires up everytime. Works great.
I've loaded the PiGateway from Github (commented in the sketch as garagemote)
Listening at 433 Mhz... SPI Flash Init OK. Unique MAC =
I'm trying the simplest of connections with a Weathershield.
When I use the monitor from within IDE I can see the 29 character output from the shield
BAT:4.86v F:7577 H:49 P:25.53 (packet length:29)
I've confirmed the Gatewayid is 1, Networkid is 100 on both, Baudrate is 115200 on both, the Moteino for the Pi is Node 1, the Weathershield is node 2, and the encryption is the same 16 Char for both sketches, the Frequencies are both set to 433 and I removed the // on the #define IS_RFM69HW //uncomment only for RFM69HW! Leave out if you have RFM69W!. line of both sketches (both nodes are HW's).
I saw Felix's post about "baby steps". I've gone over everything on the list and topics I can find in the forum... the gateway works... the radios just won't talk on 433Mhz.
https://lowpowerlab.com/forum/index.php/topic,1112.msg7196.html#msg7196
Any test commands, comments, thoughts, ideas... anything, I'm willing to try.
Thanks -
Have a great night.
Lane,
It sounds like the 2 Moteinos can communicate, correct?
If so, then skip the next paragraph.
If not: let's take a few steps back. I know you said you walked the "baby steps" but I want to ensure your 2 Moteinos can talk to each other. First load them with the example Gateway (https://github.com/LowPowerLab/RFM69/tree/master/Examples/Gateway) and Node (https://github.com/LowPowerLab/RFM69/tree/master/Examples/Node) sketches (adjust settings as appropriate).
Your real gateway code for the PiGateway is this (https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway).
This should pass any received RF packets to the serial port of your Pi, which is then picked up by the gateway.js script that handles the whole interface. Please ensure the settings are adjusted in settings.js as well. You must be sure the serial port on your Pi is accessible by the script and is correctly set in settings.js
Could you open minicom to see if you get the same messages you see in the IDE serial monitor?
That would confirm the RF link and serial port are working, and there's something else going on, reading the data from the serial port. The messages should be newline terminated, that's something the PiGateway.ino sketch does.
Felix,
The nodes communicate through IDE if plugged in with a USB cable with the FTDI.
I reloaded the R4 w/flash intended as a Gateway with the Gateway sketch you linked to, and the other R4 intended for the Weathershield with the Node Sketch. The setups came in right with the Network 100, Nodes 1 & 2 respectfully, Baud 115200. One had a GatewayID 1, one of the sketches did not, is that an issue? Using IDE I used the Serial Monitor (pic's attached of both) to see the output of each.
You mentioned the serial port on my Pi. I used your Raspberry Pi image and haven't changed anything since that. I did a serial test (stty -F /dev/ttyAMA0) I stumbled across (pic attached), not sure if the results are germane to this issue.
I reviewed the Settings.js file from on the RasPi card, it all seems to be correct. Mostly email and cell phone settings. I didn't change the serial at all so it's at default. port : '/dev/ttyAMA0'...
baud : 115200,
I have Minicom installed on my RasPi (sudo apt-get install minicom) but I'm not sure what you'd like me to do with it, or how to use it. Using Terminal from Mac I remote into the PI. I just lack the knowledge with minicom from the command line.
Let me know your thoughts.
Thanks
Lane
Here's a close up of the jumpers from the Moteino Node to the RasPi Pins.
Maybe I've got something backwards. The power works (passed the Blinky test), I traced the Tx and Rx to Rx and Tx so I think those are right.
Regarding the RasPi serial port, I read this on a Pi site, is this applicable to Moteino's?
QuoteBy default, the serial port on the Raspberry Pi is configured as a console port for communicating with the Linux OS shell. If you want to use the serial port in a software program, you must disable the OS from using this port.
Let me know if you spot something.
Thanks
Lane
P.S. A couple of the pins on the Moteino look like they don't have solder but the solder sucked through to the backside copper. I check them for continuity to the header and they all had good tone.
Lots of NOTHINGs coupled with quite weak RSSI indicate that you have something wrong in your radio settings, so double check the hardware matches the settings in the sketches, especially the isHW setting and the frequency. Have you soldered 1/4 antennas?
Minicom is just a serial monitor program, just like the Arduino IDE serial monitor. You start it up from the command line on your pi, with flags indicating the port and baud rate etc. Type minicom -help for details.
PROGRESS --
As you advised a few post back, I loaded :
Quote
First load them with the example Gateway and Node sketches (adjust settings as appropriate).
I'm getting "Sending... ACK -27 " straight down the feed. The nodes speak to each other, the yellow LED blinks on each as they transmit and receive. I had not noticed the
"#define IS_RFM69HW" line in the sketch(s) to remove the //.
I left the gateway sketch as is, it's seems to be working great. I loaded the Weathersheild sketch from "RFM69/Examples/WeatherNode/" on Github.
I tested both, the gateway says it's got a MAC Address and is Transmitting on 433Mhz (worked great during the node test), the Weathersheild says it's loaded and ready to go ...
QuoteWAWeatherMote - transmitting at: 433 Mhz...BMP180 init success...BAT:4.86v F:7245 H:47 P:25.68 (packet length:29)
I went to my Secure Server - IP address for the Moteino Gateway, the gateway was there, but no nodes (see pic attached). I looked on the Monitor page on the Server Gateway and it says connected. I unplugged and plugged them back in, nothing, at most the "connected" time would change.
Why can't I see the Node's in the Secure Server?? It connects, I can see the monitor where it says "connected", it seems to be talking. We're soooo close....
Thanks
Lane
Lane,
Can you please open the serial monitor minicom like this:
minicom -b 115200 -D /dev/ttyAMA0
To quit it hit ENTER, CTRL-A + Q
You should see the packets dumped by the gateway Moteino, received from any remote nodes. Once that is confirmed we can continue.
Felix,
I'm attaching three images of the feedback I received from Minicom (it would all fit on one screen shot).
The results when I hit "Enter", then the bottom of Minicom with the connection info.
The other image is of the only bit of obscure info that came through Minicom.
I hope these snapshots of info help you .
Thanks Again
Lane
I see one garbled message, so it looks like the Pi serial receives the data from the gateway Moteino.
The garbled payload means either it's some noise that happened to pass the CRC check and got "decrypted" into decrypted noise, it gets ignored by the gateway. Or the encryption key doesn't match but I think you already verified this.
The next step is to get your remote node to send data that you can see in Minicom. Once that is verified we can move into the gateway.js script.
If Minicom doesn't show your remote packets, then it's a step back to figuring out why the remote Moteino can't talk to your gateway Moteino --- all settings again. If that works in the Arduino IDE it should definitely work in minicom.
Truly Baby Steps
Using the Gateway and Node exchange sketches proved that the Moteino's were talking. I went to your Github dir RFM69 and re-copied the Weather sketch. I modified it, uploaded it and it didn't work again. I finally copied the settings section from the Gateway sketch and pasted it into the Weather sketch, same info I hand entered, but this time it worked. I have data flowing on the Minicom Terminal screen using the command you gave me.
I'm not getting the data from the sensors that I see passing through my Pi serial port Mincom monitoring terminal, updating in the Web Gateway. I know the data is being transmitted, the Pi is "ACK Sent", but neither the data or the node are showing on the Gateway web page. The Gateway web page is there, I log in, the Low Power site comes up with no nodes. I remembered in one of your post (or videos) you said "...the server will update the node when the node transmits", so I waited, 10+ data packets sent, no nodes. I verified the ip address with $ hostname -I .
Almost there.
Thanks
Lane
Lane,
What is the exact sketch you are using on the Gateway Moteino connected to your Pi?
I have this sketch loaded: (leftover from testing the 433Mhz link)
https://github.com/LowPowerLab/RFM69/tree/master/Examples/Gateway (https://github.com/LowPowerLab/RFM69/tree/master/Examples/Gateway)
Should I be using this one?
https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway (https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway)
Also, can you drop me a link to which Weather Sketch I should be using? One has altitude adjustments, one makes //comments of the altitude, but no #define Altitude in the setup section.
Thanks
Lane
In the meantime...
I reloaded the PiGateway:
https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway (https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway)
I'm Tx/Rx data through the Pi's AMA0 port as witnessed by Minicom:
[2] START [RSSI:-34][ACK-sent]
[] BAT:4.86v F:7352 H43 P:25.80 [RSSI:-33][ACK-sent]
[2] BAT:4.86v F:7352 H:42 P:25.80 [RSSI:-35][ACK-sent]
[2] BAT:4.86v F:7374 H:41 P:25.80 [RSSI:-38][ACK-sent]
[2] BAT:4.86v F:7331 H:42 P:25.80 [RSSI:-39][ACK-sent]
I can still log into the Moteino Gateway but after more than eight data updates, no nodes are recognized by the Gateway.
Thanks
Lane
Quote from: Felix on September 18, 2015, 08:55:44 AM
Lane,
Can you please open the serial monitor minicom like this:
minicom -b 115200 -D /dev/ttyAMA0
Hi Felix,
I am learning to setup the Pi Gateway too. I too am not finding my node in the successfully connected web interface. I followed the steps above. Using the newest image. Gateway and Node sketch. The result of the above command is the attached screenshot. So it appears the pi is not receiving anything from the moteino? any idea on what to test next?
Dreehak, did you make sure to edit settings.js and set your serial port to whatever it's on? AMA0 is default. I had to change mine to USB0 and mine worked
yes, that worked! now I see output from
minicom -b 115200 -D /dev/ttyUSB0
like LaneF, progress!!! unfortunately, I still don't see the Node showing up in the web GUI.
when trying to start gateway.js manually
node gateway.js &
I get attached screenshot. Form my research online, this could mean port conflict?
Drrehak,
I learned the painful way when it comes to receiving data using Minicom across the AMA0 port, patience is the key. For the Weathershield it takes 15 "Wake Up" cycles or 2min for each batch of info to be sent. When I first hit the enter key on the Minicom command Felix gave us, I was expecting instant gratification and a flow of data equal to the NSA, nope, takes two mins for the first set 29 char of data to flow.
Now we just have to figure out why the Secure Gateway isn't see the nodes....
Good luck
LaneF
Strange Update:
I logged off and back on, I
restarted "node Gateway.js" in the ~moteino dir . I had my Terminal open (it's always logged on to Minicom watching the port) but
didn't log in or log onto the Gateway or Minicom. I got called away from my desk (Kids !!).
When I came back, I logged into the Gateway
first THE NODE WAS THERE ! I'm using power through my Mac's USB>FTDI>Weathershield. BAM, every two min (ish) the new data would roll in and the Gateway would update. Perfect
HERES THE CATCH !! When i logged into Minicom through the Mac's Terminal (ssh
[email protected]) watching the data roll across the Pi's AMA0 port the updates STOPPED in my Gateway !!! I watched the time since last update clock hit 2,4,6,10,15 mins before it hit me.... I Ctrl-A (Z>Q) out of Minicom and the data in the Gateway flowed again.
To sort of test this. I "Sudo halt" shutdown, rebooted, did not open Terminal or Minicom across AMA0, I went straight to "cd motieno" now in ~/moteino I entered "node gateway.js" ... as fast as I hit the enter key the Gateway sprang to life and the data flowed in.
I started Minicom to monitor the port... the data
stopped.
I'm so new, I'm not sure this is real, or makes sense to you "Hero Moto's" but given my frustrations with this ... I hope this tip can help someone else.
Have a great Sunday
LaneF
I'll try rebooting and then restarting gateway.js and see if the web gui comes up
Well it's nice when it works huh!
Here's what's happening .. You cannot open a serial terminal in 2 places. You can either look at it with minicom or have it open by the gateway.js nodeJS script. In windows it's actually locked by the first app that opens it, the other can't even open it. Im a bit surprised you can "steal" it temporarily in Linux, but maybe that has its advantages.
Anyway, I think you now got it to work :)
thanks Felix,
I am not using minisom when getting my error in the screenshot. I am trying to investigate why my node is not visible in gateway interface.
Have you followed the gateway install guide?
Is your serial port enabled?
I used the stack image. I think most of the install has proven successful, since I can:
1. open gateway from web browser
2. view communicating node at serial using minicom. (this proves that serial port is enabled)
I am getting an error message when manually starting node gateway.js
That's because it's already running :)
Use this to see what other node processes are active:
ps aux | grep node
Quote from: Felix on September 21, 2015, 11:17:42 PM
That's because it's already running :)
Use this to see what other node processes are active:
ps aux | grep node
hmm. not sure how to decipher output. pasted below. so do I have 2 running?
pi@raspberrypi ~ $ ps aux | grep node
root 1320 0.0 0.5 3608 2240 ? Ss Sep21 0:00 sudo -u pi /opt/node/bin/node /home/pi/moteino/gateway.js
pi 1326 3.7 15.0 108576 66972 ? Sl Sep21 1:52 /opt/node/bin/node /home/pi/moteino/gateway.js
pi 1387 0.0 0.4 3552 1800 pts/0 S+ 00:04 0:00 grep --color=auto node
No. Just one.
But I don't understand what is the real problem, if any?
The script is running, you can load it in the browser, everything seems to work as expected, why would you run it manually again?
i'm following the guide and other troubleshooting ideas in this thread. One of the steps was to make sure that gateway.js is running by manually starting. I was confused at the error output.
So, I am still troubleshooting the problem which is my node is not visible in the browser.
Is your serial connection confirmed to work?
What is the sketch you are running on the end node and on the gateway moteinos?
What is your packet message looking like?
What do you expect to show up?
QuoteIs your serial connection confirmed to work?
is using minicom adequate? if so, yes.
QuoteWhat is the sketch you are running on the end node and on the gateway moteinos?
I am running the sketches Node (https://codebender.cc/example/RFM69/Node)and Gateway (https://codebender.cc/example/RFM69/Gateway)(with freq changed to my freq, and commenting out for RF69HW)
QuoteWhat is your packet message looking like?
What do you expect to show up?
I was expecting to see a visible Node in the browser. and some variation of the increasing A, AB, ABC, ect.
Node and Gateway are not the proper sketched, they are purely only used for debugging and testing, not for the Moteino Gateway.
The metrics defined in metrics.js will not match anythink like "ABC..." which is meaningless.
The proper MoteinoGateway sketch is here (https://github.com/LowPowerLab/RFM69/tree/master/Examples/PiGateway).
You can try sending dummy data, from instance from this random number sender node sketch (https://github.com/LowPowerLab/RFM69/blob/master/Examples/RandomNumbers/RandomNumbers.ino) that sends random fahrenheit data.
thank you! it works! sorry, I was confused that Gateway and Node sketches would also work.