P
Hi,
I have my Serial Gateway on a RasPi with Pimatic operational for >2 years now.
Since a few days I notice all drie leds (rx, tx, error) are flashing simultaneously every second.
I can recall it didn't behave like that when I setup the system.
All is working correct, I see all sensors sending/receiving data in a correct way.
What can be wrong here?
I think it is logical to have sensors try indefinitely since this is the concept of sensors in a network.
Otherwise you would not know (when not debugging) all is ok in your network.
A network sensor not being one in an usual way, just for convenience (like my BBQ-temp sensor), has to be defined otherwise.
@GertSanders The define was sufficient in my case:
#define MY_TRANSPORT_WAIT_READY_MS 2000
The sketch continues on startup when not able to connect (my BBQ-temp node is working stand alone) but will keep on trying to connect. When the gateway is found it will connect and the data is available on iPhone.
Thanks!
@gertsanders Can you show your script on this with the define MY_TRANSPORT_WAIT_READY_MS to get a "timeout" and using the TransportReady() ?
I would like to do the same with my BBQ-temp node since it has it's own display (node is for convenience to check temps on iPhone but not always needed).
@gohan A capacitor is used in al my sensors, I did not shield it. Also my gateway has no shielding and is working fine.
Wat should ne shielded? All the electronics of the radio, so everything except the antenna?
@etxmsol I think you might be right about to strong signal.
I just tried changing the MY_RF24_PA_LEVEL from RF24_PA_MAX down to RF24_PA_LOW and RF24_PA_MIN. With RF24_PA_MIN it worked. :)
I will try again with increasing distance and increasing the level when needed for my purpose.
@gohan That's what I did as mentioned in my post (radio power module) using a separate 5V power supply as well.
@sundberg84 I powered it directly from the Arduino Nano, also tried with separate power supply. No change, same results.
My gateway works fine with the same type of radio directly from the Nano.
What else to consider.
Hi,
I'm trying to replace a NRF24L01+ radio with a NRF24L01 + PA + LNA radio (with the antenna) to achieve a better range.
The node is working with the NRF24L01+ without any problem.
I now have tried 3 different NRF24L01+ PA +LNA and still end up with the same issue:
0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSF:SID:OK,ID=10
14 TSM:FPAR
51 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2058 !TSM:FPAR:NO REPLY
2060 TSM:FPAR
2096 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4104 !TSM:FPAR:NO REPLY
4106 TSM:FPAR
4142 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6150 !TSM:FPAR:NO REPLY
6152 TSM:FPAR
6188 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8196 !TSM:FPAR:FAIL
8197 TSM:FAIL:CNT=1
8199 TSM:FAIL:PDT
18202 TSM:FAIL:RE-INIT
18204 TSM:INIT
18211 TSM:INIT:TSP OK
18213 TSF:SID:OK,ID=10
18215 TSM:FPAR
18252 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20259 !TSM:FPAR:NO REPLY
20261 TSM:FPAR
20298 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22305 !TSM:FPAR:NO REPLY
22307 TSM:FPAR
22344 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24351 !TSM:FPAR:NO REPLY
24353 TSM:FPAR
24390 TSF:MSG:SEND,10-10-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26397 !TSM:FPAR:FAIL
26398 TSM:FAIL:CNT=2
26400 TSM:FAIL:PDT
It doesn't want to connect.
I also tried to use the radio power module but with no luck.
My serial gateway is also using the same NRF24L01+ PA +LNA and works for over a year ok.
What can I do to get it working?
@gohan I know it is suggested only when experiencing bad reception issues:
Connecting a Decoupling-Capacitor
If you experience bad reception or if transmitted data never reaches destination, try adding a decoupling capacitor of 4.7µ - >47µF (the exact size usually doesn't matter) across the radio's 3.3V and GND.
But I didn't have issues, only when using the Arduino IDE Serial Monitor and only with this specific node.
Until now I only had one in the Gateway radio. All other nodes work without except for the Weather Station node because this is running on a solar cel with rechargeable battery on a larger distance. In this one I also extended the NRF24L01 radio antenna.
Problem seems solved. Thanks for helping out.
@gohan I understand. But when running ok it is also connected to the PC (using power of the same USB port but not running IDE Serial Monitor) so I guess the PC itself is not the issue.
Since it seems a communication issue I just added a decoupling capacitor of 4.7µF on the radio power supply.
Now the node connected after 5 attempts.
I guess using the serial monitor generates some noise on the USB influencing the 3.3V output of the Nano making the radio instable.
@gohan said in Node not connecting in IDE Serial Monitor but does stand alone:
ok, but don't you have another computer to try?
No.
What makes you think it is computer related?
@gohan No I didn't want to downgrade my EDI ending up in having library issues.
@FotoFieber I have the node attached via USB to my PC. All works fine.
I open the Arduino IDE having the sketch, as already running on the node, open to edit. All works fine.
I now start the Serial Monitor. The node restarts and I see this:
0 MCO:BGN:INIT REPEATER,CP=RNNRA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:INIT:STATID=100
15 TSF:SID:OK,ID=100
17 TSM:FPAR
53 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2061 !TSM:FPAR:NO REPLY
2063 TSM:FPAR
2099 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4107 !TSM:FPAR:NO REPLY
4109 TSM:FPAR
4145 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6153 !TSM:FPAR:NO REPLY
6155 TSM:FPAR
6191 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8199 !TSM:FPAR:FAIL
8200 TSM:FAIL:CNT=1
8202 TSM:FAIL:PDT
18205 TSM:FAIL:RE-INIT
18207 TSM:INIT
18214 TSM:INIT:TSP OK
18216 TSM:INIT:STATID=100
18219 TSF:SID:OK,ID=100
18221 TSM:FPAR
18257 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20267 !TSM:FPAR:NO REPLY
20269 TSM:FPAR
20305 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22313 !TSM:FPAR:NO REPLY
22316 TSM:FPAR
22352 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24360 !TSM:FPAR:NO REPLY
24363 TSM:FPAR
24399 TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26407 !TSM:FPAR:FAIL
26408 TSM:FAIL:CNT=2
26411 TSM:FAIL:PDT
Continuing to RE-INIT.
Closing the IDE does not solve anything. I first need to unplug the USB and plug it in again and the node is working again.
No suggestions?
In addition: in both situations the node (Nano) is powered by the PC (usb). The node is connecting to the gateway but as soon Arduino IDE Serial Monitor is started (node restarts) the node won't connect to the gateway anymore responding with FAIL (keeping trying).
Debugging is an issue now.
Since the latest Arduino IDE update I did last week I notice my Display Node project can't be monitored by the IDE Serial Monitor. The node fails to connect to the Gateway.
However when the node is powered without using the IDE Serial Monitor it is working properly.
What can be the reason for this?
@gohan Sorry I didn't answer that this weekend.
I tried many times before to build a ESP8266 Gateway and ended up in frustrating continuous reboot issues.
So I gave up on that.
I have now a Serial Gateway working fine.
How would a MQTT gateway benefit more in the issue I have not being able to directly retrieve data from the controller?
@Boots33 That's how I plan to do it now. But for every new sensor value to get to the Display node (or when building a new Display node) I also have to update someting in Pimatic. That's what I would like to get rid off.
@Boots33 Display nodes are convenient in monitoring status of other nodes. I would like to have a Display node in the lead for this (on request).
In this way new Display nodes can be set up more easily without having to update the controller for each change on Display nodes.
If Pimatic would be able to handle the 'request()' for the node doing the request it would be great I think (like your solution).