View Full Version : setChannel function
korda
11-28-2008, 08:21 PM
I have been trying setting several networks by using setChannel(n) function and lost few remote nodes completely.
Changing Bridge channel from 0 to 10 die not help in finding these lost units.
I decided to check setChannel out of range protection. It worked only when I tried setting channel =-1. My bridge went to channel 4 (default).
Then I tried to set channel =16 and my bridge was lost completely, even USB link was lost. Even power cycle did not help!
In this case to recover I would have to have factory board and connect serially to reset everything to default.
So, do you have any idea what happened?
msellers
11-29-2008, 02:45 PM
The setChannel() function takes a channel parameter 0-15 representing which SNAP channel the node should switch to. Using numbers outside this range is not supported.
Note that this function changes the “live” channel setting, and the effect only lasts until the next reboot or power cycle. You can also use saveNvParam() to save the “persisted” channel setting, if you want the node to stay on that channel.
Applications wanting to change the channel now plus going forward should probably use both functions.
wbschindler
04-28-2009, 12:15 AM
Added to a script the ability to store the channel in NV then use it for subsequent restart.
Appears that the channel, if fetched from NV ram, before it is set results in the module becoming unusable. Ouch! #!@**x :mad:
There must be a way to reset the module to factory, but I confess that I did read this somewhere. :confused:
I will call in the AM to get some help. Frankly, while I do believe that these modules will perform, I am having a really difficult time finding documentation to solve what should be "easy" problems.
W Schindler
Chief Network Products Designer,
Secom International
kbanks
04-28-2009, 08:58 AM
If you configured your unit such that you cannot talk to it, you can use the "Factory Default NV Params" function (look under the "Options" menu in Portal) to revert the unit to it's original factory settings.
1) Connect a RS-232 cable from your PC to the second serial port on the node that you want to "reset to defaults".
On our various demo boards, the correct serial port is the only one that HAS a DB-9 connector, there is no way to connect to the wrong port.
I mention the "second UART" requirement in case you are ever running the RF Engine on some other board.
2) In Portal, go to "Options", and choose "Factory Default NV Params".
3) You will get a pop-up dialog box. You need to select the correct COM port (using the drop-down) and then press the "Default" button (just like the on-screen prompt says).
4) You then reset (or power-up) the module.
5) The Boot Loader on the node sends out a "hi I'm here" message (byte) when it starts up. Portal will hear this, and send out the "revert to your original factory settings" message.
6) Reboot (or power-cycle) your node, and it should be just like it came from Synapse (Channel 4, Network ID = 0x1C2C, etc.)
We will make this procedure more prominent in the next release of our documentation. I thought it was covered in the SNAP Reference Manual, but I did not find it in a "quick look" this morning.
vijayaraj
06-04-2009, 08:10 AM
Hi,
I have been trying setting network by using saveNvParam function and lost few remote nodes completely. When i passed the value to it,my bridge was lost completely, even USB link was lost. Even power cycle did not help!
In this case to recover I would have to have factory board and connect serially to reset everything to default.
I proceeded:
-used the option of Factory Default NvParam option in Portal software
for Bridge and Enddevice
-when i did that to the Bridge,only RS232 port is detected as bridge
port for communication.COULD NOT establish communication with
USB.
- End nodes are NOT GETTING DETECTED in the portal software.
Query
1) Can you suggest me how to get back to normal condition like condition when first operated kit with both USB and RS232 enabled and End nodes getting detected in Portal Software?
Thanks,
kbanks
06-04-2009, 09:10 AM
1) Can you suggest me how to get back to normal condition like condition when first operated kit with both USB and RS232 enabled...
I assume you mean USB enabled on the bridge device, and RS-232 enabled on the others.
A single node cannot talk to Portal on both the USB and RS-232 interfaces at the same time (you can use both interfaces, they just both can't be talking to Portal.)
Using the RS-232 interface, go into the Node Info pane and hit the "big gear" button. When the config dialog comes up, hit the "Device" tab and change the Default Uart setting from 1 to 0. This will move Packet Serial (the protocol that Portal and the node use to converse) from the second UART to the first one. Hit the OK button, and then reboot the node.
You now will be able to connect to the bridge using the USB interface instead.
...and End nodes getting detected in Portal Software?
If you have Factory Defaulted the remaining nodes, then they should be back on the default settings of Channel 4, Network ID 0x1C2C.
If after getting your bridge running like you want, you still do not see the rest of your nodes, try using Portal's built-in Find Nodes function (look this up in the SNAP Reference Manual).
vijayaraj
06-04-2009, 09:20 AM
Hi,
I tried using Find nodes function of function by scanning all the channel,i could not find any end node other than the master node which is connected to the PC.
Any more suggestion please,any parameters i need to change in the portal?
Thanks,
kbanks
06-04-2009, 05:01 PM
At this point I would try Factory Defaulting the end devices again.
You should then be able to find those nodes on channel 4, network ID 0x1c2c.
vijayaraj
06-05-2009, 04:51 AM
Hi,
I tried the following in both the Bridge and End node.
- setting Factory Default NV Param
- Reload the Firmware once again
- Setting once again the Factory Default NV Param.
- Erase the Image
- Reload the script written.
I tried above steps more than twice.
- Even tried uninstalling Portal and reinstalled to make sure no problem with
portal
Some Facts Found out:
- Bridge Responds to the commands which i programmed in the script
like read channel,read address,read registers etc to the PC Hyper terminal via COM port
- But the LED Blinking which i enabled in my script for every 1 second is not
blinking.
Next Step:
- I reloaded with the bridge with the mCastCounter.py,I COULD NOT see
any blinking of LED or Seven Segment Display.
Now i am confused,i could not say RF engine is not working since it is responding to the commands in my script at the same time i could not say it is working since it is not making LED blinking.
Can you suggest what could be the solution to solve this problem,AS it is highly urgent to make these things working as Soon as possible...
Thanks,
kbanks
06-05-2009, 10:29 AM
I tried the following in both the Bridge and End node.
- setting Factory Default NV Param
- Reload the Firmware once again
- Setting once again the Factory Default NV Param.
- Erase the Image
Try doing just the Factory Default step, for all of your units.
Do not load a script into any of them (your script may be the problem).
Now try to establish communications to your bridge, using the RS-232 port.
Optional: Once this is working, switch the bridge over to the USB port, if that is the interface you need to use. (Change the Bridge's Default UART as previously explained).
Once you are communicating with your bridge, try to communicate with the other nodes (still without using any scripts).
Since you have Factory Defaulted all the nodes, they all will be on channel 4, Network ID 0x1C2C.
Only start using scripts again after you have re-established basic communications. Then, if loading a script makes the unit stop responding, then the problem is in that script.
vijayaraj
06-05-2009, 11:08 AM
Try doing just the Factory Default step, for all of your units.
Do not load a script into any of them (your script may be the problem).
Now try to establish communications to your bridge, using the RS-232 port.
Optional: Once this is working, switch the bridge over to the USB port, if that is the interface you need to use. (Change the Bridge's Default UART as previously explained).
I have Done this and i could establish connection between Bridge and the Portal. :)
After this when i scan the nodes,which every other node has factory default values,it is not getting detected in the portal. :(
But When i read the node by node parameters using RS232 ,It has channel 4 and same network address.
Can you give me some suggestion what to do for this?
mgenti
06-05-2009, 11:14 AM
But When i read the node by node parameters using RS232 ,It has channel 4 and same network address.
I'm not sure what you are describing here. Do you mean if you connect to one of the other nodes via rs-232 it shows channel 4 network 1c2c?
vijayaraj
06-05-2009, 11:42 AM
-I programmed each and every node to factory default parameters.
-Then I tried establish communication between Bridge and Portal.It is success.Portal shows the bridge in it.
-Then i tried to find the nodes present in the network using Find nodes.But :(
no nodes got detected.
So i just checked the configuration of each node using DB connector given in the each of the board (EK2500 kit with PAN4555 in it).When i read the configuration it shows channel as 4 and network ID as 1c2c.
My problem is ,why end nodes are not getting detected other than bridge node and Not establishing connection with portal.
Can any one suggest some solution for this.It is really really very urgent.
Thanks,
kbanks
06-05-2009, 01:02 PM
With the Portal/bridge connection working, what happens when you click the Broadcast PING button?
Or try this - under Network choose New Configuration...
Are you seeing any of the other nodes?
The only way I know to NOT be able to talk to nodes when the NV settings are correct is to have changed the NV settings, but NOT rebooted (the NV settings are only read and used at startup). Give all the nodes an reboot to make sure this is not the problem.
vijayaraj
06-05-2009, 01:12 PM
Hi,
When i press the broadcast pin button,it could hear only the Bridge node and not from any other end node.
Tried Network,New configuration could only see the bridge node
I have tried the Rebooting of the device.But :( problem persist.
Will it be the problem of any software file getting crashed which is loaded in to PAN4555 module other than SNAP firmware.?
kbanks
06-05-2009, 01:32 PM
In an earlier post you said:
I tried the following in both the Bridge and End node.
- setting Factory Default NV Param
- Reload the Firmware once again
- Setting once again the Factory Default NV Param.
- Erase the Image
- Reload the script written.
When you reloaded the firmware, exactly what firmware did you load?
If what you uploaded did not have "PAN4555" in the filename, then putting it into a PAN4555 module was a mistake.
Synapse RFE code will not work in a PAN4555 module (and vice versa).
In particular, the radios are different between the modules, and loading the wrong code will make over-the-air communications impossible.
If the .sfi file you loaded had PAN4555 in the filename, then you can ignore this post.
vijayaraj
06-05-2009, 01:42 PM
Hi,
I just went into the following option in the portal.
Option -> Firmware Upgrade
The name of the firmware upgrade is SnapV2.1.8.sfi
So,from the above post,is that the file is not suited for PAN4555 module?
If so can you please suggest how to get specific firmware upgrade?
kbanks
06-05-2009, 04:41 PM
No, that is the firmware for the Synapse RF Engine. The PAN4555 hardware is similar enough to the original RFE that it is not an obvious failure when you load it.
Check the same directory (where the original SNAP sfi file is) for a file with "PAN" in the name. Also check the Portal CD that should have come with the kit.
Finally, please post an email address so that we can email you the necessary file in case you cannot locate it.
We are sorry for the inconvenience.
vijayaraj
06-06-2009, 12:08 AM
Hi,
My email IDs is vijayaraj@degreec.com
My alternate email id is rajvijayaraj@yahoo.co.in
kbanks
06-06-2009, 10:54 AM
I have attempted to send you a file, but the email server is acting up.
I will try again later.
vBulletin® v3.8.0, Copyright ©2000-2012, Jelsoft Enterprises Ltd.