WS5100 GW is not working after 2.0.1b update [SOLVED]



  • Hi,

    I updated my GW (Mega + shield 5100) with 2.0.1b and have now the following in the log:

    1	18/10/2016 17:34:35	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_HEARTBEAT_RESPONSE	399502
    2	18/10/2016 17:34:45	RX	0 - Gateway	INTERNAL	C_INTERNAL	NO	I_HEARTBEAT_RESPONSE	409499
    

    It does not accept any connections. The heartbeat goes on and it does not start. Never had a problem with 2.0b or before...

    Any idea what may have caused it please?


  • Admin

    This doesn't look like a log from the gateway.



  • @hek this is a log from MYSController



  • @hek

    GW log:

    0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGAS-,VER=2.0.1-beta
    0;255;3;0;9;TSM:INIT
    0;255;3;0;9;TSM:INIT:TSP OK
    0;255;3;0;9;TSM:INIT:GW MODE
    0;255;3;0;9;TSM:READY
    IP: 10.1.1.120
    0;255;3;0;9;MCO:REG:NOT NEEDED
    0;255;3;0;9;MCO:BGN:STP
    0;255;3;0;9;MCO:BGN:INIT OK,ID=0,PAR=0,DIS=0,REG=1
    0;255;3;0;9;TSF:MSG:READ,10-10-0,s=1,c=1,t=17,pt=5,l=4,sg=0:220
    0;255;3;0;9;TSF:MSG:READ,10-10-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
    0;255;3;0;9;TSF:MSG:BC
    0;255;3;0;9;TSF:MSG:FPAR REQ,ID=10
    0;255;3;0;9;TSF:PNG:SEND,TO=0
    0;255;3;0;9;TSF:CKU:OK
    0;255;3;0;9;TSF:MSG:GWL OK
    0;255;3;0;9;!TSF:MSG:SEND,0-0-10-10,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
    0;255;3;0;9;Eth: connect
    0;255;3;0;9;Eth: 0;0;3;0;2;
    0;255;3;0;9;Eth: 0;0;3;0;2;Get Version
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    0;255;3;0;9;Eth: 0;0;3;0;18;PING
    

    node log:

    0 MCO:BGN:INIT NODE,CP=RNONA--,VER=2.0.1-beta
    4 TSM:INIT
    10 TSM:INIT:TSP OK
    12 TSM:INIT:STATID=13
    14 TSF:SID:OK,ID=13
    16 TSM:FPAR
    53 TSF:MSG:SEND,13-13-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    2062 !TSM:FPAR:NO REPLY
    2064 TSM:FPAR
    2101 TSF:MSG:SEND,13-13-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    4110 !TSM:FPAR:NO REPLY
    4112 TSM:FPAR
    4149 TSF:MSG:SEND,13-13-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    6158 !TSM:FPAR:NO REPLY
    6160 TSM:FPAR
    6197 TSF:MSG:SEND,13-13-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    8206 !TSM:FPAR:FAIL
    8208 TSM:FAIL:CNT=1
    8210 TSM:FAIL:PDT
    

    From what I understand there is a problem with GW.
    Will probably have to change radio. It is PA version fed from AMS117 from 5V Mega 2560 pin - should be enough juice.
    Tried to change the power source without any luck.



  • Changing nrf24l01+ PA for another one resolved the issue. I hate this Chinese transceiver - so much time is waited to troubleshoot hardware issues.


  • Admin

    Sorry to hear that you got a crappy radio @alexsh1, and good that you found the issue.



  • @hek The issue is that nrf24l01+ was (and still is) working fine with pre 2.0 version. In fact it was one of the best transceivers I have in terms of range.
    For whatever reason it does not work with 2.0


  • Mod

    @alexsh1 You could consider donating this radio to the project, so we can run some tests on it.
    If an incompatibility snook in with 2.0.0. we might be able to fix it, so we can all benefit from it.



  • @Yveaux @hek More than happy to donate. However, as I discovered today the issue was not the transceiver. The issue was this little board (AMS1117 3.3). The problem is that it has been working intermittently. 0_1477332967655_image.jpeg

    My multimeter was showing a stable 3.4V, but under load it was behaving strangely. A normal nrf24l01+ (non PA) was performing much better for a while and then after a while it would start playing again.

    I have spent a few months trying to troubleshoot the problem not spending too much time, but today I decided to nail it down finally.
    😡 😡 😡 😡 😡 😡 😡


  • Mod

    @alexsh1 Any idea what is wrong with it? The AMS1117 is a rather common chip and not much else is on it, so I wonder what caused the issue...



  • @Yveaux No idea - I just replaced it for a similar board. I am going to change AMS1117 or can donate it if you can to get down to the bottom of it



  • All I can see is that after changing the AMS1117 the GW works like a charm. Surely, I need to do more testing to make sure it is rock solid.


  • Mod

    @alexsh1 Well, I suspect the AMS is of bad quality, hardly able to supply 100mA.
    Another thing is that when they fail for some reason, they tend to short-circuit internally and pass on their input voltage to their outputs directly, frying the circuit you're trying to power :rage4:
    At least, that's what I found out about them so far...



  • @Yveaux said:

    they tend to short-circuit internally and pass on their input voltage to their outputs directly, frying the circuit you're trying to power :rage4:

    Luckily, this is not what happened to me.
    AMS1117 has not failed completely. Only with PA version (higher current) I experienced issues.


Log in to reply
 

345
Online

6.7k
Users

7.6k
Topics

80.4k
Posts

Looks like your connection to MySensors Forum was lost, please wait while we try to reconnect.