Emonhub not receiving a certain node

I'm trying to switch from using a NanodeRF to an EmonHub. I am doing this since I have a custom node that sends a few items of data using unsigned ints which fail using the NanodeRF. 

The problem is that for some reason my Emonhub isn't recieving that Node. When I use the minicom I can see all the other nodes transmitting, but I can't see my none 21. My NanodeRF receives it just fine, but it messes up the data a bit for the unsigned ints. 

Is there a max size for the packet that for some reason the emonhub wont' receive but that the NanodeRF can? Any other suggestions?

 

 

pb66's picture

Re: Emonhub not receiving a certain node

The only size restriction is 66byte packet size set within JeeLib, emonhub and emoncms are not so fussy. 

Just for clarity, emonHub is just a software running on the Pi, the receiver hardware attached to the Pi's GPIO is usually a RFM2Pi and combined these are one form of emonBase, the emonPi and NanodeRF are also emonBases.

emonHub can only process the data it receives' and if you are not seeing the data in minicom then the data is not arriving at the serial port of the Pi so this excludes the Pi and emonhub, leaving only the "Custom Node", the RF route or the RFM2Pi to debug.

Some RFM2Pi firmwares did have a ~20byte packet size cap for a while, how big is your packet? 

Is the emonBase located where the NanodeRF was located? Is the "Custom Node" within range ? have you tried moving it closer just to test?

If it is not range/interferance and the packet size is ok then since the other nodes are seen it would suggest something in the "Custom Node" is causing an issue. Can you tell us more about it?

Paul

Marquis27's picture

Re: Emonhub not receiving a certain node

Thanks for the assistance. I don't think I'm hitting any limits. 

This is my data structure. I think this is 9 x 2 = 18 bytes.  That should be within the size limits. Perhaps I have an old version of the RFM2Pi firmware.. Maybe that is a place to start? If I'm using a v1 can it take an updated firmware? 

typedef struct {
  int systemVolts; // Processor Voltage
  int battery;   // Battery Volts
  int volts; // Volts to the Charger (From Panel)
  int current; // mA x 10 (Panel Current)
  unsigned int lux;
  unsigned int ir;
  unsigned int full;
  int state;
  int temp;
} Payload;

 

I'm sure it's not a range issue. They are sitting about 1 foot apart. 

 

pb66's picture

Re: Emonhub not receiving a certain node

I'm afraid I'm not that clued up with the v1 emonPi, but I would not expect there to be any problem with 18bytes of data. 

Although the typedef struct looks fine, I don't think that would pprobally stop the packet being received by the  rfm2pi. what hardware is it?, what sketch are you running?

Are you sure the group and frequency are set up correctly on node 21? Do you have another test sketch you can try?

Paul 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.