Problems with first sensors

[tekka]

@blebbens Your logs look ok, but your radios don't seem to talk to each other - this could possibly hint to radio interference or HW issues. Try:
(1) reduce PA power by setting:

#define MY_RF24_PA_LEVEL RF24_PA_LOW

and recompile and reflash GW and node sketch.

(2) move node and GW further away from each other
(3) Switch off WiFi AP

Please report back on any of these solutions with log from GW and node.

Thanks.

[blebbens]

Now I defined MY_RF24_PA_LEVEL RF24_PA_LOW in both, gateway and sensor.
Before I have done this, I compiled and uploaded the ClearEpromConfig.

The logs... gateway:

17.07.2016 15:52:22	STARTUP	Initialize message logging
17.07.2016 15:52:22	STARTUP	1.0.0 (build 3314)
17.07.2016 15:52:22	STARTUP	FPC 3.0.0 / Lazarus 1.6
17.07.2016 15:52:22	STARTUP	still under development :) tekka 2016
17.07.2016 15:52:22	STARTUP	Load INI file...
17.07.2016 15:52:22	STARTUP	INI version 1.0.0 (build 3314)
17.07.2016 15:52:23	INFO	*** Logging START ***
17.07.2016 15:52:23	VERSION	1.0.0 (build 3314)
17.07.2016 15:52:23	INFO	Logging=TRUE
17.07.2016 15:52:23	INFO	AutoID=TRUE
17.07.2016 15:52:23	INFO	AutoFW=TRUE
17.07.2016 15:52:23	STARTUP	INI file loaded
17.07.2016 15:52:23	STARTUP	Loading FW repository...
17.07.2016 15:52:23	REPO	FW "Blink" loaded. t=10, v=1, blocks=80, crc=0x46D4
17.07.2016 15:52:23	REPO	FW "TimeReporter" loaded. t=20, v=1, blocks=736, crc=0xE923
17.07.2016 15:52:23	REPO	FW repository loaded. Items=2
17.07.2016 15:52:23	STARTUP	Initialize message types
17.07.2016 15:52:23	NODE	New node discovered, node id=0
17.07.2016 15:52:23	NODE	New node discovered, node id=255
17.07.2016 15:52:23	INFO	read MySensors.xml
17.07.2016 15:52:23	INFO	Application: MYSController
17.07.2016 15:52:23	INFO	Node id=0 skipped
17.07.2016 15:52:23	INFO	Node id=255 skipped
17.07.2016 15:52:30	UPDATE	current=1.0.0.3314 remote=1.0.0.3314
17.07.2016 15:52:32	INFO	Flushing FIFO
17.07.2016 15:52:32	INFO	Connected to COM9
17.07.2016 15:52:34	RX	0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0)
17.07.2016 15:52:34	CHILD	New child discovered, node id=0, child id=internal
17.07.2016 15:52:34	RX	0;255;3;0;9;TSM:INIT
17.07.2016 15:52:34	RX	0;255;3;0;9;TSM:RADIO:OK
17.07.2016 15:52:34	RX	0;255;3;0;9;TSM:GW MODE
17.07.2016 15:52:34	RX	0;255;3;0;9;TSM:READY
17.07.2016 15:52:34	RX	0;255;3;0;14;Gateway startup complete.
17.07.2016 15:52:34	RX	0;255;0;0;18;2.0.0
17.07.2016 15:52:34	DEBUG	Update child id=255, type=S_ARDUINO_REPEATER_NODE
17.07.2016 15:52:34	RX	0;255;3;0;9;No registration required
17.07.2016 15:52:34	RX	0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1

6	17.07.2016 15:52:34	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_GATEWAY_READY	Gateway startup complete.
7	17.07.2016 15:52:34	RX	0 - Gateway	INTERNAL	C_PRESENTATION	NO	S_ARDUINO_REPEATER_NODE	2.0.0

And, the sensor...

TSM:INIT
TSM:RADIO:OK
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT

They now are far away from each other...

I think, all cables are connected to the right position.

EDIT:
Found a MQ-135 air quality sensor. Uploaded the mysensor example sketch. But, the same error output in serial monitor.

Please take a look at this picture of my NRF24L01 amplified. Perhaps, it is wrong wired ? On my NRF24 there is no mark for GND, so I took this picture.

But, isn´t my gateway (wired the same) working very well ? Is there a way to find out, if the wiring is wrong ? Would the gateway work like you can see in the log ?

Or another idea: I changed the gateway´s sketch to a baud rate of 115200. The sensor´s sketches don´t contain this information. Do I need to set their baud rate to 115200, too ?

[tekka]

@blebbens Looks like you have nRF24L01, not nRF24L01+. The nRF24L01 does not support 250Kbps (see here, page 8 ). MySensors is set (by default) to 250Kbps datarate. In your case, try this:

#define MY_RF24_DATARATE RF24_1MBPS

and recompile and reflash GW and node.

[scalz]

@blebbens
could you show a link where you bought radio modules you're using please. I think @tekka may have found the problem :)

For people who are getting same messages "FPAR FAIL", I think you may fall into the old case "st:fail", hardware related like using capa for radio, tekka advices above etc... where radio does not work properly and there is no ACK back so the comm is not validated. Then, after multiple retries, it fails.

I can confirm this at least for static nodes. On my side, the latest v2.0 from dev branch works ok for me. as expected ;) Config tested for the moment is serial gw with exotic mcu atsam (I mean compared to classic gw). And the node is a multisensors. Radio is RFM69.

[blebbens]

Flashed ClearEpromConfig...

Added to the sketches...
#define MY_RF24_PA_LEVEL RF24_PA_LOW
#define MY_RF24_DATARATE RF24_1MBPS

Think, this overrides MyConfig.h ?

What a pity... just the same output... recognized as "unknown" S_ARDUINO_REPEATER_NODE.

I bought this NRF:
http://www.aliexpress.com/item/1sets-Special-promotions-1100-meter-long-distance-NRF24L01-PA-LNA-wireless-modules-with-antenna/32341792715.html?spm=2114.13010608.0.161.TbEXts

But, the delivered NRFs have no marked GND.

Oh, any ideas left ? Delivery of standard NRFs take 30-40 days.

Extract of MyConfig.h:

/**
 * @def MY_RF24_SPI_MAX_SPEED
 * @brief MY_RF24_SPI_MAX_SPEED to overrule default nRF24L01+ SPI speed.
 */
//#define MY_RF24_SPI_MAX_SPEED 4000000

/**
 * @def MY_RF24_CE_PIN
 * @brief Default RF24 chip enable pin setting. Override in sketch if needed.
 */
#ifndef MY_RF24_CE_PIN
	#if defined(ARDUINO_ARCH_ESP8266)
		#define MY_RF24_CE_PIN 4
	#elif defined(ARDUINO_ARCH_SAMD)
		#define MY_RF24_CE_PIN 27
	#else
		#define MY_RF24_CE_PIN 9
	#endif
#endif

/**
 * @def MY_RF24_CS_PIN
 * @brief Default RF24 chip select pin setting. Override in sketch if needed.
 */
#ifndef MY_RF24_CS_PIN
	#if defined(ARDUINO_ARCH_ESP8266)
		#define MY_RF24_CS_PIN 15
	#elif defined(ARDUINO_ARCH_SAMD)
		#define MY_RF24_CS_PIN 3
	#else
		#define MY_RF24_CS_PIN 10
	#endif
#endif

/**
 * @def MY_RF24_PA_LEVEL
 * @brief Default RF24 PA level. Override in sketch if needed.
 */
#ifndef MY_RF24_PA_LEVEL
#define MY_RF24_PA_LEVEL RF24_PA_LOW
#endif

/**
 * @def MY_RF24_CHANNEL
 * @brief RF channel for the sensor net, 0-125.
 * Frequence: 2400 Mhz - 2525 Mhz Channels: 126
 * http://www.mysensors.org/radio/nRF24L01Plus.pdf
 * 0 => 2400 Mhz (RF24 channel 1)
 * 1 => 2401 Mhz (RF24 channel 2)
 * 76 => 2476 Mhz (RF24 channel 77)
 * 83 => 2483 Mhz (RF24 channel 84)
 * 124 => 2524 Mhz (RF24 channel 125)
 * 125 => 2525 Mhz (RF24 channel 126)
 * In some countries there might be limitations, in Germany for example only the range 2400,0 - 2483,5 Mhz is allowed
 * http://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2013_10_WLAN_2,4GHz_pdf.pdf
 */
#ifndef MY_RF24_CHANNEL
#define MY_RF24_CHANNEL	76
#endif

/**
 * @def MY_RF24_DATARATE
 * @brief RF24 datarate (RF24_250KBPS for 250kbs, RF24_1MBPS for 1Mbps or RF24_2MBPS for 2Mbps).
 */
#ifndef MY_RF24_DATARATE
#define MY_RF24_DATARATE RF24_250KBPS
#endif

[Tore André Rosander]

Have you tried to use another sketch?
Just a random mysensors sketch to see if it that one also get presented as repeater node.
Maybe just take one with a button and make your own (if you dont have any) and see if the buttonpress gets transmitted.

[blebbens]

@Tore-André-Rosander
Have tried out different sample-sketches from library, e.g. motion and air quality.

It is... so... frustrating. There has to be a stupid mistake causing the sensors to report their availability as repeater node.

[tekka]

@blebbens I totally understand your frustration but I'm afraid, your issue seems HW/radio-related. The logs look normal, also the repeater node message (which is actually emitted from the GW, see your domoticz screenshot and GW log). If you can get a different pair of nRF24L01+ (the P-version), I'd retry with those.

[Tore André Rosander]

Is it just me or does it look like the repeater node is not the actual sensor node?

If you look at the logs " Gateway INTERNAL C_PRESENTATION NO S_ARDUINO_REPEATER_NODE 2.0.0" "New child discovered, node id=0, child id=internal" and "Update child id=255, type=S_ARDUINO_REPEATER_NODE"

How about try to define the node id manually?
And just to be sure the clear eeprom config sketch in the mySensors examples.
You can also try the RF24 library ping-pong examples to test your radios.

[SGi]

Ok so connections appear to be my major problem.... my dupont cables seem to be a bit dodgy... now wired with solid jumpers i can get the 'gettingstarted' sketch of the RF24 library working.

Now i have the following log from the sensor which is encouraging but still weird:

Anything obvious now? The sketch on the sensor is the basic motionsensor one from the examples of 2.0.0 and the gateway is the serialgateway sketch... both no changes

[nielsokker]

@SGi

I am not an expert but i had the same problem. I think a controller determines the id. But since you have none, it can't be done this way. Set a static ID with

#define MY_NODE_ID 11 

or something

[SGi]

@nielsokker Yea you are probably right, no problem now though since as soon as i hooked it up to my controller everything works fine :) dodgy wires on the gateway was the issue all along.... using the very basic node sketch i can now see it in Domoticz and watch it turn on/off every 10 secs :)

[tekka]

@SGi Excellent, have fun 👍

[blebbens]

Think, I do not understand yet.
The motion sketch uses #define CHILD_ID 1.
Where do I have to insert #define MY_NODE_ID 1 ? Just into the skecht of the motion sensor ?

[Tore André Rosander]

@blebbens i think you can just put it over "define child id"

[nielsokker]

@Tore-André-Rosander said:

define child id"

I think so too.

These are probably just minor mistakes, changing from MySensors versions.

[blebbens]

So, I have to delete CHILD_ID und change it to MY_NODE_ID?

Okay, reaching home today, perhaps. Hope, this works.

[Tore André Rosander]

No, just add the define node id.

[nielsokker]

@blebbens

The old define, might become useless, but it wont be in the way either. It is your choice.

[scalz]

@blebbens use MY_NODE_ID to define the id of your node. the child id is for your sensors id, not the node id.