After switching the firmware to routers all modules are discovereed on ConnectPort Manager. But none of them are discovered with the PC sample program Digi Embedded Kit Gateway Viewer. What would you recommend to try?
The post above was moved from a thread regarding a different topic, and thus was used to create this new thread…
Make sure the python portion of the demo app has been started as that’s where the “discovery” portion of the app is done. You could either start this by auto-start in the Applications > Python area of the CP-X Web UI, or manually start it from the commandline by telnetting to the CP-X, then issuing command "python .
If doing this from the commandline, you’d then see some dialogue…
#> python EmbeddedKitService.py
Starting up…
Ready for incoming requests!
Discovering nodes…
7B30:[00:13:a2:00:40:0a:0a:d4]!- SensAdpt PAN888
33B7:[00:13:a2:00:40:0a:0f:c1]!- RS232 PAN888
Hi,
My problem is:
While uploading demo application demo to gateway (connectPort X2), the error says something like “No enough disk space-code5”. Please advice.
Thank you.
Hi,
Thanks for your help. I was able to upload files. But now, when opened demo application, I am getting error “List Index out of range”.
I have attached the telnet image. Please help.
Ummi
Hi,
I am rebooting the CP-X everytime I am runnig the application but still giving the same error.
How can I fix the bug in the application? Thanks
Ummi
Hello, I think I have the same problem as yesok: I’am working with my Starter Kit XK-B11-SK-W.
I correctly see gateway, sensor and rs232 units in my browser, but the “Companion Application” does not work:
It displays the main window “Digi Embedded Kit Gateway Viewer”, another window which says “Enter IP Address of Gateway” 192.168.5.6. I correct it in 192.168.1.1 that is what functions with my browser, but the app, after Discovery, complains with “No devices found”.
I tried to follow this reply but it seems I don’t have the EmbeddedKitService.py loaded in my hardware.
I only see: python.zip, xbee_sensor.py, zigbee.py, zb_tcp_serial.py (which is also in auto-start), zb_tcp_serial.zip.
Perhaps must I uplod EmbeddedKitService.py to the gateway and then start it ?
Please give me simple answers: I only have the kit since 2 days … thank you
I forgot to attach the log contents:
Exception in thread Discovery Thread:
Traceback (most recent call last):
File “threading.pyc”, line 460, in __bootstrap
File “threading.pyc”, line 440, in run
File “ZigBee\ZigbeeDiscover.pyc”, line 161, in discover_thread
File “xmlrpclib.pyc”, line 1147, in call
File “xmlrpclib.pyc”, line 1437, in __request
File “xmlrpclib.pyc”, line 1183, in request
File “xmlrpclib.pyc”, line 1297, in send_content
File “httplib.pyc”, line 856, in endheaders
File “httplib.pyc”, line 728, in _send_output
File “httplib.pyc”, line 695, in send
File “httplib.pyc”, line 679, in connect
error: (10061, ‘Connection refused’)
This article should help:
http://www.digi.com/support/kbase/kbaseresultdetl.jsp?id=3063
Hi, thanks for this link.
I followed the instructions and all looked fine (except for minor discrepancies) until I got to step 4f. :
I opened a DOS shell and
> telnet 192.168.1.1
#> python EmbeddedKitService.py
…
I got an Exception : see attached file.
What went wrong ? any help ? thanks
“Error 22” generally means the app is trying to bind to a radio that’s already been bound to.
The culprit is normally a script that’s set to auto-start in the Applications > Python > Auto-start Settings area. Please uncheck anything set to auto-start and reboot your CP-X, then try redoing the steps in that part of the article when the gateway comes back up.
A couple places you can verify whether or not a script is already running are from the Web UI: Management > Connections, or from the commandline doing the “who” command. A running python script and its threads will show up in both of these places.
The X2 has a limited amount of “code space” compared to the X4 or X8, so there is room for the demo app and that’s about it.
If you go into the Web UI, Applications > Python area and delete any files listed which aren’t actually part of the Embedded Kit Gateway Viewer app (such as python.zip for instance), there should be enough space.
One thing that “List Index out of Range” can mean is that the demo app was running then shutdown (using the “Shutdown Server” button in the app for instance), then an attempt was made to start it again without the CP-X being rebooted.
I believe this is a bug in the Demo app and should be fixed, but the bottom line is you must reboot the CP-X after shutting down the app, before it can be run again.
Any resolution on this? I have the same issue. When I run who, the only thing running is term and telnet. When I type pyhon EmbeddedKitService.py after resetting, I get this:
Starting up…
Ready for incoming requests!
Discovering nodes…
Exception in thread WPANSerialEndpoint:
Traceback (most recent call last):
File “WEB/python/embedded_kit_gateway.zip/threading.py”, line 442, in __bootst
rap
File “WEB/python/EmbeddedKitManager.py”, line 199, in run
nodes = self.get_bindings_hash_list()
File “WEB/python/EmbeddedKitManager.py”, line 496, in get_bindings_hash_list
hash_list = [self._bindings.bindings[k].to_hash()
File “WEB/python/EmbeddedKitManager.py”, line 38, in to_hash
return {
IndexError: list index out of range
Help!
Through further testing I believe this isn’t a bug at all, because another thing that can cause this error is a radio associated to the CP-X gateway which can’t be communicated with.
From the CP-X WebUI Configuration > XBee Network screen, first of all check the box “Clear list before performing refresh”, then hit the refresh button. For each of the radios listed, click on its extended address to make sure you don’t get an error. If you do get an error like “Can not display mesh settings for this node”, you’ve found your culprit. Turning off that adapter should allow the demo app to run without error.
I worked with this customer over the phone.
The culprit (for closure to this thread) turned out to be the RS232 adapter, which had an older (1220) version of firmware on it. Once we’d updated the RS232 adapter to the 1247 firmware, the Embedded Kit Gateway Viewer app was up and running.
I’m also having failures trying to run the EmbeddedKit.
Here’s the error msg:
#> py EmbeddedKitService.py
Starting up…
Ready for incoming requests!
Discovering nodes…
Exception in thread WPANSerialEndpoint:
Traceback (most recent call last):
File “WEB/python/embedded_kit_gateway.zip/threading.py”, line 442, in __bootstrap
File “WEB/python/EmbeddedKitManager.py”, line 199, in run
nodes = self.get_bindings_hash_list()
File “WEB/python/EmbeddedKitManager.py”, line 496, in get_bindings_hash_list
hash_list = [self._bindings.bindings[k].to_hash()
File “WEB/python/EmbeddedKitManager.py”, line 38, in to_hash
return {
IndexError: list index out of range
Exception in thread Serial Endpoint:
Traceback (most recent call last):
File “WEB/python/embedded_kit_gateway.zip/threading.py”, line 442, in __bootstrap
File “WEB/python/embedded_kit_gateway.zip/threading.py”, line 422, in run
File “WEB/python/EmbeddedKitManager.py”, line 248, in run_serial_endpoint
self.get_bindings_hash_list())
File “WEB/python/EmbeddedKitManager.py”, line 496, in get_bindings_hash_list
hash_list = [self._bindings.bindings[k].to_hash()
File “WEB/python/EmbeddedKitManager.py”, line 38, in to_hash
return {
IndexError: list index out of range
Been trying it several times and followed the steps according to: http://www.digi.com/support/kbase/kbaseresultdetl.jsp?id=3063, still no luck
Also, Admin, can you point out how can I update the RS232 adapter version on the CP-X4?
This may be a compatibility issue now…
The Embedded Kit Gateway Viewer was an app written two years ago, and was basically obolete when the iDigi Dia was released. As such, it hasn’t been updated with the changes that when into the NDS 2.8 –> 2.9 release (detail of the changes found here: http://www.digi.com/wiki/developer/index.php/Python_Migration_Guide_for_NDS_2.8_to_2.9)
I will update the kbase article to reflect this, but the bottom line is that app reached its life expectancy when the 2.9.x EOS firmware was released. My recommendation would be to use the demo apps contained in the iDigi Dia instead. You can download the app from here upon registration: http://www.idigi.com/resources.jsp