Help, hosed up SN170

[wjmmidstar]

I am a newbie and I have hosed up my SN170. In trying to upload a Snappy image over the air, a USB error occurred and the SN170 node went dead.

In trying to reset it to out of the box condition, I connected to the serial port and have manged to communicate to the board to erase the image, reload the firmware and reset the NV prams. Not necessarily in that order. I did finally figure out the sequence to set the Network address via the SaveNVparam function to that address on the label. I have managed to get it back on the air, but it doesn't respond to the scripts so something is still not set properly.

What should I do now as the out of the box configuration seems to elude me?

[kbanks]

Do one more "Factory Default" and then load example script MulticastCounter.py into it.

This should make it identical to a "fresh out of the box" unit.

Then make sure your channel and Network ID settings are what you want them to be.

[wjmmidstar]

Worked! Thanks!

Bill

[wjmmidstar]

I have the SN171 node now functional, but the link quality of this node is very weak. It drops out at about 10 feet away. Previous to my reflashing the node, strength was much higher. A quick sanity check - SN111 has much improved link quality.

Perhaps the LNA is turned off? I have tried to do a writePin to GPIO3 to set the LNA power on, but that has no effect. I have also tried setting the pin direction first, but again no change. Perhaps I am barking up the wrong tree with the LNA.

Any suggestions?

Thanks,

[wjmmidstar]

Ok, I am looking at the latest snap reference manual 2.2 and found the section specific to the PAN4561 and enabling the LNA via the feature bits.

The SN171 node is a x001F which seems to need set to x003F to enable the LNA. My efforts to set the feature bits to x003F using saveNvParam id11 don't seem to affect it.

Thanks,

[kbanks]

1) Does the GUI confirm you changed the ID #11 parameter correctly?

2) Did you reboot the node afterwards, so that the NV change would take effect?

3) Do you have an older (Rev B) module? If so, see page 134 of the 2.2 SNAP Reference Manual. You may need to set NV #64 to 1.

[wjmmidstar]

1) Does the GUI confirm you changed the ID #11 parameter correctly?
Yes, Returned value = 0
2) Did you reboot the node afterwards, so that the NV change would take effect?
Yes

3) Do you have an older (Rev B) module? If so, see page 134 of the 2.2 SNAP Reference Manual. You may need to set NV #64 to 1.
Yes, I changed to a 1 prior to trying #1 and #2 above. Still no effect.

configuration parameters/device still show feature bits = 0x001F

[wjmmidstar]

Fixed the issue. LNA was not enabled on SN4561. Problem for those others who are newbies like me, running the GUI statement SaveNvParam(id, obj) the "obj" does not like the hex format. I was trying to put in "x3F" or "x00\x3F" and the GUI said it changed it, but a check of LoadNvParam(11) showed the value of x001F.

Just changed the x003F to regular old decimal 63 did the trick. The GUI likes decimal numbers.

Thanks for the support.

[kbanks]

Just changed the x003F to regular old decimal 63 did the trick. The GUI likes decimal numbers.


The GUI is also fine with hex, but the correct prefix is '0x', not just 'x'.

(This is a standard Python thing, not anything unique to SNAP, SNAPpy, or the GUI).