Any RFM95 user reports?
-
@mfalkvidd Thank you, looks like that will help me as well.
Have had a bit of a tinker and still not getting the transport to initialise.
#define MY_DEBUG #define MY_DEBUG_VERBOSE_RFM95 #define MY_RADIO_RFM95 #define RFM95_434MHZ #define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR48SF4096 #define MY_GATEWAY_SERIAL // Enable inclusion mode #define MY_INCLUSION_MODE_FEATURE #define MY_INCLUSION_MODE_DURATION 60 #define MY_DEFAULT_LED_BLINK_PERIOD 300 #include <MySensors.h> void setup() { } void presentation() { } void loop() { }``` Thats what i have for the gateway and this is the response0;255;3;0;9;MCO:BGN:INIT GW,CP=RLNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;RFM95:INIT
0;255;3;0;9;!TSM:INIT:TSP FAIL
0;255;3;0;9;TSM:FAIL:CNT=1
0;255;3;0;9;TSM:FAIL:PDT```Anyone able to assist? is the code right and its a hardware issue or is there more that needs to be in the code?
-
This is what I used for a RFM69 gateway on an esp8266. Something similar should work for RFM95:
#define MY_RFM69_FREQUENCY RF69_433MHZ #define MY_RF69_IRQ_PIN D1 #define MY_RF69_IRQ_NUM MY_RF69_IRQ_PIN #define MY_RF69_SPI_CS D2 // NSSMaybe MY_RF69_IRQ_NUM should be defined as digitalPinToInterrupt(MY_RF69_IRQ_PIN).
-
Hi,
I'm very interested in the LoRa thing : it' probably the only way to connect a node to a gateway through several floors of concrete in building.. (or do you think the NRF24 could do it ?)
Could you share your experience on how you wired your hardware ? (including how you power the RFM95 if the arduino pins can not supply enough power -I read somewhere that Lora require up to 200mA, more than the 20-40mA available on Arduino Pro Mini for instance).
br,
-
I'm also having trouble with RFM95's. I'm confused about MY_RFM95_IRQ_PIN and MY_RFM95_IRQ_NUM. Does PIN mean the GPIO pin number or the interrupt pin number? I've noticed that the same physical pin has different numbers depending on their use.
Also, what is the distinction between MY_RFM95_IRQ_PIN andMY_RFM95_IRQ_NUM?
-
Hi,
I don't know whether this helps, but I am also experiencing some trouble testing an RFM95 module.
I am using the Moteino with FTDI adapter.
I found that the connection is really instable (I should use some capacitors for a more stable connection I guess, even though there's no problem with the RFM69 433mHz version).
My configuration is the default one. Don't know if I even have to define it that way, just did it because I had to with the last ones:#define MY_DEBUG // used by MySensor (Print debug messages via serial) #define MY_RADIO_RFM95 // Select Radio-Module RFM95 #define MY_RFM95_FREQUENCY 868 // Define our Frequency of 868 MHz #define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR45SF128 //Default for medium Range and medium speed: RFM95_BW125CR45SF128 ; For long range and slow speed: RFM95_BW125CR48SF4096 #define MY_RFM95_NETWORKID 100 // leave out for gateway selection #define MY_RFM95_IRQ_PIN DEFAULT_RFM95_IRQ_PIN #define MY_RFM95_IRQ_NUM DEFAULT_RFM95_IRQ_NUM #define MY_RFM95_CS_PIN DEFAULT_RFM95_CS_PIN #define MY_NODE_ID 224 // Node ID #define MY_BAUD_RATE 38400Also I am trying to use it with an RPi and FHEM. But this didn't work so far.
But I do get it to work over the PC-USB using the Arduino Serial-Monitor... Strange. -
@gohan
Ah sorry, I misunderstood.
The RFM95s VCC is factory-wired to a regulator on the moteino. It is an out of the box MCU+Radio-Unit.
See this link for clarification:
Moteino with RFM95Sorry for the confusion.
EDIT: I just tried changing my normal 433MHz Gateway with Arduino Nano + RFM69HCW on the RPi for a Moteino-integrated-RFM69HCW one.
I have the same problem with that as with the LoRa Moteino GW... It works fine with the PC and even gets readings far away, I normally do not get.
Hooking it up to the RPi with FHEM it stops working...
I can't really explain that? :confused:EDIT 2: I checked the debug of the sensor-sided unit. It says st=OK...
So I guess I'll have to check my hardware (FTDI etc.) -
Ok, the on board regulator should able to provide 250mA while the Rfm95 uses 120mA max, so that should be OK.
@gohan
Your point made me look something up. Even though I do use the 2.5 amps powersupply for the RPi3 Model B I did find, that the RPi can only take up to 1Amp max. and depending on what's it doing, it can consume between 700-1000 mA.
So hooking up the Moteino + FTDI may max that out even though the USB-Port should supply up to 500mA.
raspberrypi.orgTypically, the model B uses between 700-1000mA depending on what peripherals are connected; the model A can use as little as 500mA with no peripherals attached. The maximum power the Raspberry Pi can use is 1 Amp. If you need to connect a USB device that will take the power requirements above 1 Amp, then you must connect it to an externally-powered USB hub.
So I'll try an active HUB next. And if that works I might give this a try:
Boost USB-Power
This site claims that a change in the RPi's config file should boost the max output current to 1.2 A... Sounds a little wild and unhealthy but I'll give it a shot.Also FTDIchip.com claims that you should use an external USB-power-supply when powering devices with more than 100mA. Everything points into one direction :scream:
-
Hey guys, a little later but still I've got "kind of" news.
Everything I tried to get the Moteino as GW to work consistently failed.
It seems the problem either lay with the FTDI or the Moteino as GW. Since I am using a Nano with an Adafruit Breakout RFM95W everything just works fine. It is a little unsatisfying but as I only need Moteinos for Nodes (low battery drain) I will go with this (cheaper) GW.
