I bought a RFM69Pi V3 module (868mhz) to be able to receive data from my nodes (also sending on 868mhz).
I disabled the serial console. Then I connected the module to my Raspberry Pi (running raspbian jessy) like so: http://puu.sh/phLxR/7b16354b0b.jpg When I power on the raspberry the red LED of the RFM69Pi is on for a few seconds, then never again.
minicom -b 38400 -o -D /dev/ttyAMA0 is giving me a very strange output: (one line adding approx. per second even if my sender is not sending at all)
On this page: https://wiki.openenergymonitor.org/index.php/RFM69Pi_V3#Debugging at the very bottom they say it should look different. In another post I could read that G0 may stand for group 0 which should be 210. They say it is possible to change it in minicom but I don’t get it. If I type s.th. like “210g” I don’t get any response from minicom and the above lines keep adding. How can I setup the RFM69Pi V3 to receive 868Mhz data with group 210 ?
In minicom do you get a response to typing a v and entering? or a ? and entering?
It would be good to establish if all commands are ignored or if the settings are locked, the current configuration output from either v or ? should confirm if locked and the? should give you the help text to see the fll list of options including how to unlock the settings if locked.
As you’ve discovered, whilst in minicom typing command string 210g and enter. should switch it out of “all groups” mode (which is set by using 0g).
Once out of all groups mode you should see your nodes, there is a wrinkle in the way the all groups function works and it actually gives you all groups except the configured group so the absence of your expected nodes isn’t significant until you exit all groups mode. If anything it may confirm you device was set to group 210 prior to being set to 0g
Do you have a transimitting node nearby and turned on?
The serial output you are seeing with ‘?’ is discarded packets that are being ignored. You can turn off display of discarded packets by turning on quiet mode by sending serial command 1q via minicom.
In emonHub.conf you will need to set the frequency to 868mhz. emonHub config can be edited in the Setup > EmonHub tab of local Emoncms
Thank you for your answers.
When I type “v” or “?” in minicom nothing happens (same when pressing enter afterwards). I’ve just reinstalled raspbian jessy and it didn’t change anything. https://community.openenergymonitor.org/t/rfm69pi-getting-started-basic-question/260 There I could read that sending a ? will list all available commands… it won’t work for me. It doesn’t even seem like I can type anything at all, minicom is just listing the lines mentioned above. Only thing that works is strg+a + z. I can then use all options listed in the help screen, but I do not see a single way there to configure the RFM69Pi.
I can not find any descriptions on the internet about a “?” command like: http://manpages.ubuntu.com/manpages/xenial/man1/minicom.1.html
When you see the list of commands can you see the current settings listed at the bottom e.g.
Available commands
<nn> i - set node ID (standard node ids are 1..30)
<n> b - set MHz band (4 = 433, 8 = 868, 9 = 915)
<nnnn> o - change frequency offset within the band (default 1600)
96..3903 is the range supported by the RFM12B
<nnn> g - set network group (RFM12 only allows 212, 0 = any)
<n> c - set collect mode (advanced, normally 0)
t - broadcast max-size test packet, request ack
...,<nn> a - send data packet to node <nn>, request ack
...,<nn> s - send data packet to node <nn>, no ack
<n> q - set quiet mode (1 = don't report bad packets)
<n> x - set reporting format (0: decimal, 1: hex, 2: hex+ascii)
123 z - total power down, needs a reset to start up again
Remote control commands:
<hchi>,<hclo>,<addr>,<cmd> f - FS20 command (868 MHz)
<addr>,<dev>,<on> k - KAKU command (433 MHz)
Current configuration:
E i5 g210 @ 433 MHz
The config of this module is 433Mhz 210 network group
‘v’ should work for you since you have the latest module.
Example commands:
8b - set frequency to 868 (default 433)
210g - set group to 210 (default)
1q - turn off quite mode (don’t return bad packets ‘?’)
p - list avialble commands
v - return version (only supported on newere RFM69Pi)
``
There should be no need to use minicom. Do you intend to use the RFM69Pi to post to Emoncms? If so, I would recommend using latest pre-built SD card image and configuring the module via emonHub . You should set 868mhz in emonhub.conf
I don’t get it. You all say “press v or press ? or press p”. I’ve now read every single thread on the internet about minicom and rfm69pi. I’ve installed jessy like 3 times, even tried the openenergymonitor image. I’ve used raspberry pi model 1 and 2 and I pressed every single key like 500 times when minicom is open and there is no way that I can send a command (like set frequency / network id) to the rfm69pi.
Very sorry for this hassle. It sounds like you may have a hardware issue although it’ very strange that you can receive data from the RFM69Pi but not send data.
See screencast demonstrating sending serial using minicom:
Could there be something else interfering with the serial transmission e.g. Linux terminal? Before RMA Could you try with our pre built SD card image to make double sure there is nothing interfering with the serial link:
Thank you for your help.
What I’ve done for testing:
I’ve connected pin 8 and 10 of the raspberry using a jumper wire. When I open minicom now and type s.th. I can just read what I typed. As far as my knowledge can tell me, minicom is sending everything I type to the serial port and displaying everything which is received from the serial port in the console (correct me if I am wrong).
Which means, that the RFM69Pi should respond via the serial port when I send the letter “v” or “?” to the serial port by typing it in minicom? If this is the case, my RFM69Pi should behave differently. In order to check if the RFM69Pi is not working correctly I just orderd a new one . I have used the pre-build image, raspbian wheezy and a newly installed raspbian jessy so far, all behaving the same way (as described above)
It sounds like maybe you have a hardware issue with the RFM69Pi. Thanks for ordering another, however I was about to send you one anyway! I have refunded the cost of your new order. We will ship the new module today
. I have used the pre-build image, raspbian wheezy and a newly installed raspbian jessy so far, all behaving the same way (as described above)
