"Config save failed" on JeeNode after giving simple command

(5 posts) (2 voices)

Tags:

No tags yet.

mars

I configured the JeeNode, but run into troubles upto the point that I have to upload the RF12demo again to get the JeeNode back to life...

- it started with the problem assigning #10 to the node --> was set to node 0 - then after upload, I was able to communicate with the JeeLink upto the point that I tried to send a packet to a nonexisting node, but with an Ack. --> node set to 0 ??

See below for the output:

    Available commands:
       i     - set node ID (standard node ids are 1..26)
                   (or enter an uppercase 'A'..'Z' to set id)
       b      - set MHz band (4 = 433, 8 = 868, 9 = 915)
       g    - set network group (RFM12 only allows 212)
       c      - set collect mode (advanced, normally 0)
      t          - broadcast max-size test packet, with ack
      ..., a - send data packet to node , with ack
      ..., s - send data packet to node , no ack
       l      - turn activity LED on PB1 on or off
    Remote control commands:
      ,,, f     - FS20 command (868 MHz)
      ,, k              - KAKU command (433 MHz)
    Current configuration:
     B i2 g212 @ 915 MHz 
    > 1a
     -> 1 b
     ? 32 45 212 242 126 144 48 102 106 11 28 59 144 88 139 149 192 245 219 65 108
    > 0t
     -> 66 b
    > 0e
    > 0s
    > 0t
    > 0i
     @ i0 g212 @ 915 MHz 
    config save failed
     -> 66 b
    > 0n

    Available commands:
       i     - set node ID (standard node ids are 1..26)
                   (or enter an uppercase 'A'..'Z' to set id)
       b      - set MHz band (4 = 433, 8 = 868, 9 = 915)
       g    - set network group (RFM12 only allows 212)
       c      - set collect mode (advanced, normally 0)
      t          - broadcast max-size test packet, with ack
      ..., a - send data packet to node , with ack
      ..., s - send data packet to node , no ack
       l      - turn activity LED on PB1 on or off
    Remote control commands:
      ,,, f     - FS20 command (868 MHz)
      ,, k              - KAKU command (433 MHz)
    Current configuration:
     @ i0 g212 @ 915 MHz 
    > 0g
     @ i0 g0 @ 915 MHz 
    config save failed
    > 0i
     @ i0 g0 @ 915 MHz 
    config save failed
    > 0t
     -> 66 b
    > 0a
    > 0l
    > 8a

And once more, after upload issuing the command "N i" (ie set to node N):

    Current configuration:
     A i1 g212 @ 433 MHz 
     N i14 g212 @ 433 MHz 
    > 0i
     @ i0 g212 @ 433 MHz 
    config save failed

And dead again! Do I do something wrong?

Posted 13/05/2010 20:53:04

jcw

Get the very latest version of RF12 - see - that should fix the hang.
Node numbers have to be 1..31 - from what I can tell, you entered "0i" (or perhaps just "i", same thing) - that's a special node ID used for OOK transmissions. Same for groups, use 1..250 (0 is not yet a problem, but it is reserved).
Oh, wait. I think I see what's going on... something is sending the text "testing" to the JeeNode. That gets interpreted as lots of different commands, some invalid. Don't send arbitrary text to a JeeNode while it's running the RF12demo sketch.

Posted 13/05/2010 21:57:11
mars
I did get the latest RF12demo sketch, but that didn't help.
When I did enter 10 i, I got 0i as the response... As you can see, sending "N i" (should be allowed according to the help, ie 'A' to 'Z' is translated to a number: N = 14), which seems to work, as I get the response N i14.
Furthermore, I'm sending (from the keyboard) "Hello" messages as in "Hello,1 a", and afaik I'm the only one in this neighbourhood with a JeeLink/JeeNode.
Hmmmmm, weird: from the JeeNode to the JeeLink: "Hello everybody,1 a" results in a change in band from 915Mhz to 433Mhz for the JeeNode ?!?!?!?
Sending "Hello,1 a" sometimes results in (at the JeeLink):
```
    OK 97 0
```
But in some cases:
```
    OK 97 0
    DF S 34 2 679
```
Setting the JeeLink to collectmode (1c), results in a change of nodeid (from 1 to 9). If I set collectmode to 0 again (0c), the nodenumber remains 9 (instead of 1).
Something weird is going on with the commandline interface & interpretation of commands. Might be some overflow orso that triggers this very strange behaviour??
Posted 14/05/2010 09:34:28
jcw

> Something weird is going on with the commandline interface & interpretation of commands.
Aha, I get it. It's a mismatch between your expectations and the code...
You can't send strings that way. To send "hello", you would have to enter: 104,101,108,108,111,1 a
You can send strings, and you could extend RF12demo to do it, but as it is, it's byte-oriented.

Posted 14/05/2010 10:42:32
mars

Ok!

Posted 14/05/2010 12:18:31