martinnossel
11-30-2008, 10:04 PM
I have now had the current file I am working on disappear twice and I mean the file is cleared on the hard drive. The is the xxx.py in the directory and the size is 0.
One was on my machine. And once on the test site machine while connected via gotomypc.
Both times I did not have a backup as I am trying to debug the programs and its work in progress, and is more than infuriating. It happens as you click the tab to bring up the code.
Also the rename function does not work in updating the nodeX name in portal, its cleared after a node reboot or “network..new “configuration. I have had to use the node.name = “loadNvParam(8)”_sent_by_node (every time there is communication from a node to portal)
I have a test system set up that been running for about 10 days. In the test there are 9 nodes. At the moment the system has been running 10 days each node sending data ever 5 seconds. No sleep.
I want them to sleep for varying times from 5sec to 15min depending on whatever.
The set up is star. (I think, as all nodes are in range of the bridge (not sure how to confirm this but would like to be able to.))
I wrote and tested software with only one node that allows the node to wake up, send data and check if it can go back to sleep. The bridge is always awake. It looked very nice with the ammeter pulsing for less than a second and the data appearing in the portal chart.
I just loaded one of the test nodes and the ‘portal_node’ with above software. One node sleeping and waking up for a instant to transmit every 5sec, the other 8 transmitting every 5 seconds but not sleeping.(the awake nodes send 4 short strings 2 to the chart, and 2 to the log). The sleeping node send 10 variables (displayed in portal), the above 4 strings and requests a ‘can I sleep’ variable. The system immediately bogged down completely some data was received from 2 nodes.
I am about to change the NV parameters to ‘listen out’ and reduce the ‘discovering calls’.
Please can I get some details on what portal is doing in the background so I to optimize this system.
Even with just a one node system waking up and sleeping, if I press the “watch nodes button” the poor event log goes berserk, with 3sec discovery calls etc.
I see in the new sleepy mesh examples, (thanks, they were informative, we need more of the same) that in one you poll the sleepy mesh (for the above reason?). If this is the case I am going to get more speed out of a bunch of couriers with ‘post its’ than a mesh with 600 or more nodes and will need car batteries to power the nodes as they stay awake waiting there chance to transmit. How I am supposed to divide up the network and debug such a system after what I am struggling with now, makes me want to get a job as a street sweeper. (which I will soon probably end up having to do)
Martin
One was on my machine. And once on the test site machine while connected via gotomypc.
Both times I did not have a backup as I am trying to debug the programs and its work in progress, and is more than infuriating. It happens as you click the tab to bring up the code.
Also the rename function does not work in updating the nodeX name in portal, its cleared after a node reboot or “network..new “configuration. I have had to use the node.name = “loadNvParam(8)”_sent_by_node (every time there is communication from a node to portal)
I have a test system set up that been running for about 10 days. In the test there are 9 nodes. At the moment the system has been running 10 days each node sending data ever 5 seconds. No sleep.
I want them to sleep for varying times from 5sec to 15min depending on whatever.
The set up is star. (I think, as all nodes are in range of the bridge (not sure how to confirm this but would like to be able to.))
I wrote and tested software with only one node that allows the node to wake up, send data and check if it can go back to sleep. The bridge is always awake. It looked very nice with the ammeter pulsing for less than a second and the data appearing in the portal chart.
I just loaded one of the test nodes and the ‘portal_node’ with above software. One node sleeping and waking up for a instant to transmit every 5sec, the other 8 transmitting every 5 seconds but not sleeping.(the awake nodes send 4 short strings 2 to the chart, and 2 to the log). The sleeping node send 10 variables (displayed in portal), the above 4 strings and requests a ‘can I sleep’ variable. The system immediately bogged down completely some data was received from 2 nodes.
I am about to change the NV parameters to ‘listen out’ and reduce the ‘discovering calls’.
Please can I get some details on what portal is doing in the background so I to optimize this system.
Even with just a one node system waking up and sleeping, if I press the “watch nodes button” the poor event log goes berserk, with 3sec discovery calls etc.
I see in the new sleepy mesh examples, (thanks, they were informative, we need more of the same) that in one you poll the sleepy mesh (for the above reason?). If this is the case I am going to get more speed out of a bunch of couriers with ‘post its’ than a mesh with 600 or more nodes and will need car batteries to power the nodes as they stay awake waiting there chance to transmit. How I am supposed to divide up the network and debug such a system after what I am struggling with now, makes me want to get a job as a street sweeper. (which I will soon probably end up having to do)
Martin