Archived Forum

Sounds ok from the receiving end, as long as you have the frequency and group set correctly you should start to receive messages in the minicom window.

It sounds like your sensors not transmitting. Make sure it's on the same frequency and network group as the rfm12pi. The led on the rfm12pi should flash when it receives data 

Hello everybody!

I am experiencing the same exact problem...

I've tried to perfectly match the Arduino file from Chris and Minicom config without success (nothing happens in the minicom window and I see an "offline" in the bottom right - probably referred to its dialup part)

How did you (hopefully) solve it, chris? :)

If anybody else has hints I'd love it.

I've fought harder today (with no luck).

Deciding I've done something wrong with the programmer I've tried (being a total noob) to debug what's wrong using the only thing I can make: blink a led.

From minicom if I use "1l" or "0l" command the little RFM12Pi turns the led on and off so I *think* it's alive and kicking.

Ive configured it this way:

80 i16* g210 @ 433 MHz  Lock: 1

On the TinyTX side I've tweaked a very little bit Nathan's code to see if everything was working and if the code was running.
The code I've added is between // led debug comments.
I've used led 0 because (strange) it corresponds to attiny pin 2, not used by nathan:

//----------------------------------------------------------------------------------------------------------------------
// TinyTX - An ATtiny84 and RFM12B Wireless Temperature & Humidity Sensor Node
// By Nathan Chantrell. For hardware design see http://nathan.chantrell.net/tinytx
//
// Using the DHT22 temperature and humidity sensor
//
// Licenced under the Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) licence:
// http://creativecommons.org/licenses/by-sa/3.0/
//
// Requires Arduino IDE with arduino-tiny core: http://code.google.com/p/arduino-tiny/
//----------------------------------------------------------------------------------------------------------------------

#include <DHT22.h> // https://github.com/nathanchantrell/Arduino-DHT22
#include <JeeLib.h> // https://github.com/jcw/jeelib

ISR(WDT_vect) { Sleepy::watchdogEvent(); } // interrupt handler for JeeLabs Sleepy power saving

#define myNodeID 16      // RF12 node ID in the range 1-30
#define network 210      // RF12 Network group
#define freq RF12_433MHZ // Frequency of RFM12B module

#define USE_ACK           // Enable ACKs, comment out to disable
#define RETRY_PERIOD 5    // How soon to retry (in seconds) if ACK didn't come in
#define RETRY_LIMIT 5     // Maximum number of times to retry
#define ACK_TIME 10       // Number of milliseconds to wait for an ack

#define DHT22_PIN 10     // DHT sensor is connected on D10/ATtiny pin 13
#define DHT22_POWER 9 // DHT Power pin is connected on D9/ATtiny pin 12

DHT22 myDHT22(DHT22_PIN); // Setup the DHT

// led per il debug
int led = 0;
// led per il debug

//########################################################################################################################
//Data Structure to be sent
//########################################################################################################################

typedef struct {
        int humidity; // Humidity reading
     int supplyV; // Supply voltage
      int temp; // Temperature reading
} Payload;

Payload tinytx;

// Wait a few milliseconds for proper ACK
#ifdef USE_ACK
  static byte waitForAck() {
   MilliTimer ackTimer;
   while (!ackTimer.poll(ACK_TIME)) {
     if (rf12_recvDone() && rf12_crc == 0 &&
        rf12_hdr == (RF12_HDR_DST | RF12_HDR_CTL | myNodeID))
        return 1;
     }
   return 0;
  }
#endif

//--------------------------------------------------------------------------------------------------
// Send payload data via RF
//-------------------------------------------------------------------------------------------------
static void rfwrite(){
  #ifdef USE_ACK
   for (byte i = 0; i <= RETRY_LIMIT; ++i) {  // tx and wait for ack up to RETRY_LIMIT times
     rf12_sleep(-1);              // Wake up RF module
      while (!rf12_canSend())
      rf12_recvDone();
      rf12_sendStart(RF12_HDR_ACK, &tinytx, sizeof tinytx);
      rf12_sendWait(2);           // Wait for RF to finish sending while in standby mode
      byte acked = waitForAck();  // Wait for ACK
      rf12_sleep(0);              // Put RF module to sleep
      if (acked) { return; }      // Return if ACK received
 
   Sleepy::loseSomeTime(RETRY_PERIOD * 1000);     // If no ack received wait and try again
   }
  #else
     rf12_sleep(-1);              // Wake up RF module
     while (!rf12_canSend())
     rf12_recvDone();
     rf12_sendStart(0, &tinytx, sizeof tinytx);
     rf12_sendWait(2);           // Wait for RF to finish sending while in standby mode
     rf12_sleep(0);              // Put RF module to sleep
     return;
  #endif
}

//--------------------------------------------------------------------------------------------------
// Read current supply voltage
//--------------------------------------------------------------------------------------------------
long readVcc() {
   bitClear(PRR, PRADC); ADCSRA |= bit(ADEN); // Enable the ADC
   long result;
   // Read 1.1V reference against Vcc
   #if defined(__AVR_ATtiny84__)
    ADMUX = _BV(MUX5) | _BV(MUX0); // For ATtiny84
   #else
    ADMUX = _BV(REFS0) | _BV(MUX3) | _BV(MUX2) | _BV(MUX1);  // For ATmega328
   #endif
   delay(2); // Wait for Vref to settle
   ADCSRA |= _BV(ADSC); // Convert
   while (bit_is_set(ADCSRA,ADSC));
   result = ADCL;
   result |= ADCH<<8;
   result = 1126400L / result; // Back-calculate Vcc in mV
   ADCSRA &= ~ bit(ADEN); bitSet(PRR, PRADC); // Disable the ADC to save power
   return result;
}

//########################################################################################################################

void setup() {
  // Led per il debug
  pinMode(led, OUTPUT);    
  // Led per il debug

  rf12_initialize(myNodeID,freq,network); // Initialize RFM12 with settings defined above
  rf12_sleep(0);                          // Put the RFM12 to sleep

  pinMode(DHT22_POWER, OUTPUT); // set power pin for DHT to output
 
  PRR = bit(PRTIM1); // only keep timer 0 going
 
  ADCSRA &= ~ bit(ADEN); bitSet(PRR, PRADC); // Disable the ADC to save power
 
}

void loop() {
 
  // Led per il debug
  digitalWrite(led, HIGH);   // turn the LED on (HIGH is the voltage level)
  delay(1000);               // wait for a second
  digitalWrite(led, LOW);    // turn the LED off by making the voltage LOW
  delay(1000);   
  // Led per il debug
 
  digitalWrite(DHT22_POWER, HIGH); // turn DHT sensor on

  DHT22_ERROR_t errorCode;
 
  Sleepy::loseSomeTime(2000); // Sensor requires minimum 2s warm-up after power-on.
 
  errorCode = myDHT22.readData(); // read data from sensor

  if (errorCode == DHT_ERROR_NONE) { // data is good

    tinytx.temp = (myDHT22.getTemperatureC()*100); // Get temperature reading and convert to integer, reversed at receiving end
   
    tinytx.humidity = (myDHT22.getHumidity()*100); // Get humidity reading and convert to integer, reversed at receiving end

    tinytx.supplyV = readVcc(); // Get supply voltage

    rfwrite(); // Send data via RF

  }

  digitalWrite(DHT22_POWER, LOW); // turn DS18B20 off
 
  Sleepy::loseSomeTime(1000); //JeeLabs power save function: enter low power mode for 60 seconds (valid range 16-65000 ms)
   
}

This
This way I see that the led works so the code gets executed.Nothing appears on the minicom anyway...What is wrong?

Hi guys,

i'm trying to do exactly the same thing (other sensors, and with a beaglebone black).

when I began, i encounter the same problem : nothing appears with "minicom -b9600 -D/dev/ttyO1"

Then i decide to flash the RFM12Pi's firmware.with one that is a bit different : https://github.com/mharizanov/RFM2Pi/blob/master/firmware/Full_RF12demo_...

see informations on my blog (in French) : http://mymiscellaneoustricks.wordpress.com/

So now i can see packet into minicom...in fact lot and lot of noise.

The next step is to "isolate" datas that concern my sensors. For that i had supposed that i can filter my view by select specific Network Group, but I have no idea of the one used by my sensors.

Help  would be appreciated.

Hi, Docin!

I'd be glad to share energies but I'm still stuck.

I've downloaded the firmware you suggest on the RFM12Pi and tried to see if in minicom I get data...

Nothing happens there.

What should I do?

I've prepared my TinyTX uploading the dht22 code on the attiny and followed your suggestion about RFM12Pi: what is next?

Thanks,
D.

hi ltpitt,

• what is your serial port?
• have you successfuly upgraded the rfm12pi firmware?(use avrdude) If yes, the led should be now lighted
• what are the minicom parameters you are using ?

When and where did you download your jeelib library from?

For the past 12 days there's been an urgent "feature" being developed in the Jeelib site called,

"Reducing RAM usage for the ATTiny84"  http://jeelabs.net/issues/436

@Docin

I *think* it is ttyAMA0 (to use minicom I digit: minicom -b 9600 -o -D /dev/ttyAMA0)

Yessir! I've used the firmware in your link and updated it with avrdude using my usbtinyisp.

In minicom I see:

80 i16* g210 @ 433 MHz  Lock: 1

Should I digit something in minicom to activate retrieval or data should simply appear in it?

@ukmoose
I got jeelib from sourceforge 15 days ago (more or less)...
If you know of a good link to download a working copy of it I'd be really happy :)

@ltpitt

okay dokey! Your RFM12Pi module in listen for data only into the Network Group #210.

Simply type "0g"  (zero) and it will listen for all Network groups.

@docin

Sadly no good news :(

The group specified in Nathan's code for dht22 (https://github.com/nathanchantrell/TinyTX/blob/master/TinyTX_DHT22/TinyT...) specifies group 210.

I've tried to select all groups like suggested but I get nothing...

Just the normal "help" minicom screen.

How can I track down the problem?

Put some print statements in the code, look at the serial port on your arduino.  

If there's nothing being transmitted there's nothing for the RFM12Pi to recieve.

This is really interesting.

I use an attiny84 and I have to check for its serial output...

Being totally new to the subject the only way I knew to check for information was to change the code like I did a few replies before.

I'll investigate more about the print statements in arduino and check better for what nathan's script sends to the RFM12Pi.

Thanks for the tip: I'll let you guys know :)

I am trying to learn more about the subject and I've read something that I didn't love:

http://harizanov.com/2012/08/setting-up-arduino-ide-for-working-with-att...

"I program the little guys with an USBTiny ISP programmer, just be careful when you program them and have 3.3V components on the board as well, such as the RFM12B module. Most ISP programmers (like the USBTiny ) do have a jumper that when removed does not power the board with 5V, thus you can use a battery or other 3.3V power source and not fry the other components."

This means that if I've used the usbtinyISP (with the jumper connected) to change firmware on my RFM12Pi I've fried it? :(

How can I check if I've killed it?

Hi everyone...

Can someone please be so kind to write me how to configure the RFM12pi to receive all signals on the 433 and show what's received on the screen?

I tried:

minicom -b 9600 -o -D /dev/ttyAMA0

Then I see minicom and I configure it pressing:

4b and 0g

I should now receive from all devices sending data on 433 mhz, right?

Why nothing happens?

Should I press something?

Yes your minicom setup appears to be correct but without seeing what you can see it's difficult to tell if it is correct.

In general if you are not receiving data on minicom

Have you made sure that no other process is using the serial port? Follow the instructions on this page: http://www.hobbytronics.co.uk/raspberry-pi-serial-port

Rather than opening up the RFM12Pi to receive everything why not configure it to receive data if it is being broadcast from the TinyTX?  Use the same network group but a DIFFERENT node ID as explained here  http://openenergymonitor.org/emon/buildingblocks/rfm12b2

Why are you so confident that the problem lies with the rfm12Pi?  Rather than your TinyTx? 

Have you double checked that the frequency of your RFM12B hardware is 433MHz?

Have you double checked that the aerial is the right length? 

Have you double checked the solder joints are all good on the RFM12B?

Hi there and thanks for your time, again :)

I've been trying to follow your suggestions:

Have you made sure that no other process is using the serial port? Follow the instructions on this page: http://www.hobbytronics.co.uk/raspberry-pi-serial-port

Done as instructed (was already set this way)

Rather than opening up the RFM12Pi to receive everything why not configure it to receive data if it is being broadcast from the TinyTX?  Use the same network group but a DIFFERENT node ID as explained here  http://openenergymonitor.org/emon/buildingblocks/rfm12b2

I have tried g0, g210 and several groups with lucky guesses

Aerial should be the right lenght (433mhz): 165mm

I will post screenshots so maybe it's easier to understand what am I doing wrong...

I've asked Nathan how to debug TinyTX and he suggested me to use a specific test script.

I downloaded it and compiled it in arduino:

https://dl.dropboxusercontent.com/u/3900156/arduino.png

Then I flashed it on the attiny with avrdude (notice warnings: are those problems?):

https://dl.dropboxusercontent.com/u/3900156/avrdude.png

Then I assembled my little tinytx, feed it with 3.5 volts (I have nothing to feed it 3.3 as suggested) and opened minicom with this setup:

https://dl.dropboxusercontent.com/u/3900156/minicom.png

Have you double checked the solder joints are all good on the RFM12B?

How can I check that? Forgive my inexperience... I can use a tester but... What should I check?

I am sorry I feel very stupid for wasting your time but I have no clue being a total noob in the area :)

Please do not give up

It works.

I ran on the top of the hill to yell and cry until I passed out.

God bless everyone.

Hi ltpitt,

I have a problem similar to your's and am curious as to how you got it working!

Can you please share your solution?

Edit:
I have tried all of the above suggestions, but with no success.

The activity LED on the RFM12PI lights up on boot, as I have read elsewhere it should, so I suppose that the board is in functional condition.

Further, I have a wireless cooking thermometer that runs on the same frequency (4: 433MHz). I assume that I should be able to intercept its packages using group 0, but I receive nothing still.

When I try to transmit to the RFM12PI using either a TinyTX3 or the sensor part of the cooker thermometer the status LED on the RFM12PI does not light up at all.

I have not even once seen minicom report being online, it is always offline.

-----

Best regards!

In my case very serious attention had to be spent on the TinyTX side.

I had to get a 3.3v converter (https://www.sparkfun.com/products/10967) to be sure that the little guy was fed with the right amount of energy and I had to check that it was working using the test code included in TinyTX github (here: https://github.com/nathanchantrell/TinyTX/blob/master/TinyTX_SendTest/TinyTX_SendTest.ino)

Once done all of this (including a few lolvely problems with placing upside down the attiny on the TinyTX) the two little beasts finally decided to talk to each other.
This happened ONLY in the same room because I built a terrible antenna for TinyTX (now I'm buying a rubber duck or similar) so be sure that you are VERY close to the pi when doing your tests.
In my experience the RFM12Pi listens ONLY to TinyTX and not to any 433mhz device in my house.
Probably poor configuration on my side but that's what I experienced.
So I could put the dht22 into the game, flash back the right code for dht22 and write a silly python script to decode its signal (Nathan was of great help and on his site you find marvellous information: http://nathan.chantrell.net/tinytx-wireless-sensor/).

If you need the code to read dht22 without emoncms I put my horrible (but working) script on github so you can use it as start :)

https://github.com/ltpitt/tinytx-dht22-raspberrypi/blob/master/dht22.py

If I can be of help I'm here.

Hi ltpitt,

Thank you very much for your reply!

I do not have a voltage divider, but am using the 3.3v output of an Arduino Uno, although I see on the Arduino forum that a voltage divider might be required anyway.

I have tried with the RPI and TinyTX3 right next to each other using the TinyTX SendTest program from Nathan, but with no luck.

I have started a separate thread for my problems: http://openenergymonitor.org/emon/node/5094, so we can continue our discussions there.

Best regards

- Anders

hello,

I'm still in stuck with my RFM12Pi

For a reason I ignore, I receive too many paccket (i'm flooded)

Connecting with minicom is okay

The help banner gave me the following output:

Available commands:
  <nn> i     - set node ID (standard node ids are 1..30)
  <n> b      - set MHz band (4 = 433, 8 = 868, 9 = 915)
  <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> l      - turn activity LED on PB1 on or off
  <n> q      - set quiet mode (1 = don't report bad packets)
  <n> x      - set reporting format (0 = decimal, 1 = hex)
  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)

If I select the zero group, i'm flooded by lines of this type( around 5 lines per second)

ÿX G12 3DD00C0340FD1055A1D3F82385E72CFD79949F8EEB6653D59278D566C0E12FB8F4751F5FDE1A847103B990F8E02213FD1BA266108A085B31032F9F2B1376CB3F022AA5C791010004477E007E0C0000E534E400D86D6F005FB4010000E8030000000000003904F503C500C400C000C100C200C6000403070501013030300
X GE1 005276CD805F002542C54AE0BA057CD782A68CC3031C244F0042134D6910A2881B1048810782118AB820D257D15D799C1D57438B3E58C0B246F26ABECF961AB61BB6E277E5010004477E007E0C00000237E400E06E6F0036B4010000E8030000000000003904F503C500C400C000C100C200C60004030705010130304338
X G47 BD0E27FDF4432E1522B09131033BC0DF15C0E087FCFB2AF301C4E7983FA547C0EDE6587BB2CE06E1B4FF7F821DEACA890514EFDDB0C67C0E38968619FB70A53F54045B4FB4010004477E007E0C00000839E400DD6F6F0048B4010000E8030000000000003904F503C500C400C000C100C200C6000403070501013037303D
X GCA 2FCF97AEB30417C58F7897FED8646C00E0A78BA4EFC96C36A55A00D7C5002CFB49588420843CCFCEE65794BB35017E9825AC66FB8D4B4FF1CBCF508F8207337A40B91AF2A8010004477E007E0C0000C43AE400B6706F0005B4010000E8030000000000003904F503
X GD0 2A9EFD6C34FAA4247688A2AB77610004F1137EE35D6CD700DFE1E81E93EF7B05F690E623D635CF004436431DD0099C306160742AEFD65A63E05CF3C0E647BD924038158BBB010004477E007E0C0000A53BE40024716F0022B4010000E8030000000000003904F503C500C400C000C100C200C60004030705010130343032
X GB8 079F6E1D0908EA7EF2DC3D41572D3FF6E809C0B10DAC8B7555E0003B79E64F08D9B10324B15CEDD3C16648E3AFB7F8032D5967043B5B6ED37F385D7AE3CEB82BDCA5D9C8E3010004477E007E0C00007A3DE40009726F0021B4010000E8030000000000003904F503C500C400C000C100C200C600
X G12 081F106130CAA6368DBBCA49C00B42462AC397883CDCF1546F1FD843C4C3427D283DBC81EE30C7036F967A8454BB21ACA5DE2D1D98F70807BFAD08DC580E13FBB9B9A70332010004477E007E0C0000723EE40083726F000FB4010000E8030000
X G80 303661CCB29486C1EC91001F10641205830EE7D067985AC18EE7030039D1B0A6010600601C8ED6D5EFD44958FE4560258EA3A8285B1188302107A93FE933CF1F4708400E81010004477E007E0C0000433FE400E8726F0079B4010000E8030000000000003904F503C500C400C000C100C200C60004030705010130353030
X G88 871233EC26A0A249014DA0A17129842C2041A64E313CD40A0224A0C6151A4A070E12902EA42088AE46628FC98819C77D00501131EACBE14CC1AC24289074232991441E0203010004477E007E0C00009140E4008B736F0063B4010000E8030000000000003904F503C500
X G1B 0980975216E58E08C7071822962F6E69865679C9C6940C6A04AC709900368608BAF3
X G22 39200044F411378CA4A6E4B620
X G2A 26A33A4EEB8A6AF3C56108ABDF9B8ED614BA2D8AFF824D8EE7860264BB0F8418CD78A4FA829610A43DC4BE14223E78604F258E18CFAF9C680314511514
X GA1 2CA7F2F41840E43D000222633A8AC1D5256640CEE8F6A028C6646B809FA8C1F90318FB60423E5DF0DD7451D728321C5C40D9B097C3B797614120CC03
X G30 5EB521C877B22E94C070830714EC1ED80619FD47581F200A177E8E1A5B885C1CFFEAE59092E9CA392C80BB83FA2638D85F2F0AD7506D370324A8D9D2F36104D448915384F1010004477E007E0C0000AE43E40010756F003AB4010000E8030000000000003904F503C500C400C000C100C200C60004030705010130303333
X GDA 98CC23341867A2324FB13A1DA23CD47939C17624AD9C2307D2C1C94576017C38307305863CD15DA69269E1DBE571187705F950934CCFDBE13181E333BAD8EF8002409243DA010004477E007E0C00002245E400C6756F0019B4010000E8030000000000003904F503C500C400C000C100C200C60004030705010143323033
X G7E 1A4DDEED84F04D840B99E7C96CBF2EFC77C93C40B251E0805471D0342EA533D3EB4486485C42A5B0F0364ABDE2C0067363E05589F49CF296FBD8079D95C4C225B48D566F1E010004477E007E0C00008946E40075766F004BB4010000E8030000000000003904F503C500C400C000C100C200C60004030705010133393038
X G89 304201BF47ADA44AC435920D88B88890E4E4FF4100740B4B91F8B0C23EB2BC3BDE10881C8640823D68733FBE0209C2631026829583610C30E82393D224502A900942768820010004477E007E0C00004D48E40052776F0020B4010000E8030000000000003904F503C500C400C000C100C200C6000403070501014334303B
X GA8 1DE453C6870227FA3681839EEC68BCBE0E33271364184E9410EEFDD3F31951215019603729009C2D1B701B862F46
X G12 126B920EE0C18B19AF98B38E5C645CADCFB571F2C0CEB90ABCC86AD41808395E8F1A4C349CA6F9B8BA46CA5B37CF76E705E885B1C569455E034F5C7956BB46221D3C81D187010004477E007E0C0000604AE40055786F0056B4010000E8030000000000003904F503C500C400C000C100C200C60004030705010130304332
X GF8 37E2AA517C023905B897610DB2F8F07866C326F80A6ACA42A1AE4E1013093112D4A5B09CC3110F298F0594833AA399FA04A13C6503F0485230D819400AE05140E000AE4A92010004477E007E0C0000894BE400E6786F004BB4010000E8030000000000003904
X GF0 BA57849ED0806008CEED8CF22C9FAE186E1A9471D6C190ECE31C4AA4782788DDB0A192586B5220A1BE1862BC40036015FB18120F6A777403FA44B2B4A096CE9A069E4318FE010004477E007E0C0000EB4CE40093796F0071B4010000E8030000000000
X G73 0502B0AF69D5AED76C026FCF0FD98CDE5D621CF6A62811EFE3F8F744DD0A8BB68CB69D1EEFF144D5F5DDEFBBB2F17A1CDE31124B39AAD9675F6F6F204F2C2FFF4F7843E8DE010004477E007E0C0000954EE400637A6F006FB4010000E8030000000000003904F503C500C400C000C100C200C60004030705010143323033
X G38 28
X G00 3F604DD3806C42A020898C00975E450829CB94A3944C389B40900A2036638C8977A10410E250EE000D6100C8883000118B099DF810548E6001EC2DE04E74412FC4A1891486010004477E007E0C00
X G98 30D0480A689619BE90082819A60C886808E16108A10403900DC0
X G0B 3023
X G91 82FA901088905404263A47CE01706F510040A88A4299200D4C
X GF7 2CB102027C802E88BA13B804803B914100C704AE50307FC2698086FE9C00005F2F286A440257600210B9E04055803197414ECF41A016614145E76A027C0C0BC21091901069010004477E007E0C00005C51E400BE7B6F0044B4010000E8030000000000003904F503C500C400C000C100C200C60004030705010130303030
X G8A 167A1B0FC2D6B9943A5C747FA39EBF16C3D26FE90E3EEDF71C3CACCFA87B47E90A834992AFF4B7C5FF1D178F736E7596E502D0D1A1A8B3F645AEF5
X GE4 B0964294CC06A77D124C62A22299361ADE42151EC12795DB25000F51D8FFACE2569894604460875159922E29007CEB8FC6E58EBCFFECEA4DA5A2AC2A7F0D5903230F4A8406010004477E007E0C00002253E4009C7C6F0019B4010000E8030000000000003904F503C500C400C000C100C200C60004030705010130313337
X G6F 82E3C15D3EC480BFC988112E8879021971111F34703AF332E2740A8087DC960BEC56FF3161DFF353961F121296C689A6311E7C0A36175DB6B901ACE580243E5DBC28A906DB010004477E007E0C00
X G97 1726383DF75B90B936F5C8D7A6DB46A86E037BDDB3CADA79FC3EF467980384B04005A38C06A57FA7234321081264FCFFA0A4E4
X G79 942277E997A15ADDE2AEBFBF75BB5E5020910EFD94A6A5CC523D165EE03EB19336E26217B9035E26E6FFE7A86A0AAF525B55D63E308DAA2EEA487084FB6ADF6EE0151D263D010004477E007E0C00002B56E400177E6F00
X G8F 18FC7F3855EEF277F925529CA5F4F7CF78FFB7CC73B47CD747FFA78E7EE15EC74ABF1E74E6F908DDE0284B132867963571ED2044508BF5873C36B734405EFD7513CCF7C068010004477E007E0C00001857E4008B7E6F0078B4010000E8030000000000003904F503C500C400C000C100C200C600040307050101303

Same result if I test it with my laptop at the top of a mountain  :-(

I had the same Problem. RFM2Pi LED always on, nothing to see in minicom.

One week of flashing. trying, flashing, trying...... nothing Displayed in minicom.

Then I used an older Version of JeeLib in Arduino ..... works !!

Lets give it a try...

I'm in the oposed situation :mine is too verbose

hi,

I'm back.

Can you, please tell me which version of JeeLib you used for ?

How to check the version? I'm currently using the last one from their git