Hi. I’m following the iDigi x4 starter kit directions in the getting started guide, and have everything compiled and uploaded but cannot get the live web page to show. The images below show the mac addresses, and configuration files. I’m not using the board right now, only the router, the repeater and the temperature sensor.
telnet 4146
also fails.
Hello Christina!
A couple of points:
First, the screen shot you attached to your post of starting the Dia indicates you are starting the Dia running on your PC: in order to acquire data from the router and the temperature sensor you will have to run the make.py script on the configuration file you attached to this forum posting and upload the dia.py and bin/dia.zip files to your ConnectPort X4 gateway.
After you have uploaded the files you will need to telnet to the gateway:
C:> telnet 192.168.1.10
and start the script on the ConnectPort X4:
#> python dia.py
You will receive some debug output. If you have any trouble make sure to cut and paste (or take a screen grab) of this output so we may help you further.
Secondly, I noticed a typo in the URL used to access the Web presentation of your sensor data. You specified:
…when it should be:
http:://192.168.1.10/idigi_dia
…according to your configuration file.
Please do not hesistate to write further if you continue to experience trouble!
Jordan
Hi jordanh,
thankyou for your reply… i dont know i found telnet in vista and now its working properly while using CLI but while running a demo when i give a command
python dia.py
or
python dia.py dia.yml
it gives me an error as show in attachment.
can u please help me out with that.
regards,
GV
New technologies and updated versions at your finger tips .Visit - Internet Download Manager
Thanks Jordan!
I got it working , was just missing this step:
Thanks!
================
After you have uploaded the files you will need to telnet to the gateway:
C:> telnet 192.168.1.10
and start the script on the ConnectPort X4:
#> python dia.py
No problem!
After you have run and verified that you have everything setup correctly, you can enable the dia.py script to autostart underneath the Python section of the Web User Interface.
Please let us know if you have any trouble finding it!
Best regards,
Jordan
oddly, it worked but now i have error messages after restarting… . I switched to a fixed IP for the X4, but that was it. Also get a channel_dump ok but the web page is blank?
Wow. Interesting!
Does the ConnectPort X4 have access to the Internet? In the network settings did you give it a valid gateway address?
If that’s not it, could you please attach your configuration file?
Jordan
see attached…
#> python dia.py
Determining platform type…Digi Python environment found.
iDigi Device Integration Application Version 1.1.11
Using settings file: dia.yml
Core: initial garbage collection of 0 objects.
Attempting to read “dia.yml” in “WEB/python/dia.zip”…
Core: post-settings garbage collection of 25 objects.
Starting Channel Manager…
Starting Device Driver Manager…
XBeeDeviceManager(xbee_device_manager): node ‘00:13:a2:00:40:31:7f:89!’ moved to
CONFIGURE state.
XBeeDeviceManager(xbee_device_manager): node ‘00:13:a2:00:40:30:9d:71!’ moved to
CONFIGURE state.
XBeeDeviceManagerConfigurator: busy, deferring ‘00:13:a2:00:40:30:9d:71!’
XBeeDeviceManager(xbee_device_manager): 00:13:a2:00:40:30:9d:71! next config att
empt deferred 30 seconds.
Starting Presentation Manager…
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘DL’ to ‘\x
40\x31\xd2\xa0’
XBeeDeviceManagerConfigurator: busy, deferring ‘00:13:a2:00:40:30:9d:71!’
XBeeDeviceManager(xbee_device_manager): 00:13:a2:00:40:30:9d:71! next config att
empt deferred 30 seconds.
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘P1’ to ‘0x
3’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘DH’ to ‘\x
00\x13\xa2\x00’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘IR’ to ‘0x
1388’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘IC’ to ‘0x
800’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘D2’ to ‘0x
2’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘D3’ to ‘0x
2’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘D1’ to ‘0x
2’
Core services started.
GarbageCollector: collected 0 objects.
XBeeDeviceManagerConfigurator: busy, deferring ‘00:13:a2:00:40:30:9d:71!’
XBeeDeviceManager(xbee_device_manager): 00:13:a2:00:40:30:9d:71! next config att
empt deferred 30 seconds.
XBeeConfigBlockDDO.apply_config: applying changes (AC)
: broadcasting new SP = 0x1f4
XBeeConfigBlockSleep: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘SP’ to ‘0x1f4’
XBeeConfigBlockSleep: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘SO’ to ‘0x0’
XBeeConfigBlockSleep: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘SN’ to ‘0x1’
XBeeConfigBlockSleep: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘SM’ to ‘0x4’
XBeeConfigBlockSleep: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘ST’ to ‘0x3e8’
XBeeConfigBlockSleep: applying changes (final AC)
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:31:7f:89!’ = ‘WH’ to ‘0x
7d’
XBeeConfigBlockDDO.apply_config: applying changes (AC)
XBeeConfigBlockFinalWrite: trying ‘WR’ to ‘00:13:a2:00:40:31:7f:89!’
XBeeDeviceManager(xbee_device_manager): configuration done for node ‘00:13:a2:00
:40:31:7f:89!’ promoting to RUNNING state.
XBeeSensor(sensor0): running indication
XBeeSensor(sensor0): DD info (module_id, product_id) = (0x0003, 0x000e)
XBeeSensor(sensor0): sensor is a ‘Digi XBee Sensor /L/T’ no humidity capability.
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:30:9d:71!’ = ‘DL’ to ‘\x
40\x31\xd2\xa0’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:30:9d:71!’ = ‘IR’ to ‘0x
1388’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:30:9d:71!’ = ‘D2’ to ‘0x
2’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:30:9d:71!’ = ‘DH’ to ‘\x
00\x13\xa2\x00’
XBeeConfigBlockDDO.apply_config: trying ‘00:13:a2:00:40:30:9d:71!’ = ‘D1’ to ‘0x
2’
XBeeConfigBlockDDO.apply_config: applying changes (AC)
XBeeConfigBlockFinalWrite: trying ‘WR’ to ‘00:13:a2:00:40:30:9d:71!’
XBeeDeviceManager(xbee_device_manager): configuration done for node ‘00:13:a2:00
:40:30:9d:71!’ promoting to RUNNING state.
XBeeSensor(sensor0): raw sample L: 163, T: 736
XBeeSensor(sensor0): raw sample L: 137, T: 736
XBeeSensor(sensor0): raw sample L: 357, T: 736
XBeeSensor(sensor0): raw sample L: 388, T: 736
XBeeSensor(sensor0): raw sample L: 336, T: 739
XBeeSensor(sensor0): raw sample L: 212, T: 739
(-6, ‘The name does not resolve for the supplied parameters. Neither nodename n
or servname were supplied. At least one of these must be supplied.’)
XBeeSensor(sensor0): raw sample L: 371, T: 739
XBeeSensor(sensor0): raw sample L: 378, T: 739
XBeeSensor(sensor0): raw sample L: 334, T: 739
XBeeSensor(sensor0): raw sample L: 228, T: 739
XBeeSensor(sensor0): raw sample L: 275, T: 739
XBeeSensor(sensor0): raw sample L: 371, T: 741
(-6, ‘The name does not resolve for the supplied parameters. Neither nodename n
or servname were supplied. At least one of these must be supplied.’)
XBeeSensor(sensor0): raw sample L: 397, T: 741
XBeeSensor(sensor0): raw sample L: 381, T: 741
XBeeSensor(sensor0): raw sample L: 360, T: 741
XBeeSensor(sensor0): raw sample L: 306, T: 741
XBeeSensor(sensor0): raw sample L: 228, T: 741
(-6, ‘The name does not resolve for the supplied parameters. Neither nodename n
or servname were supplied. At least one of these must be supplied.’)
XBeeSensor(sensor0): raw sample L: 240, T: 741
XBeeSensor(sensor0): raw sample L: 374, T: 741
XBeeSensor(sensor0): raw sample L: 388, T: 741
… nevermind it was IP conflict… works now, hope it stays. fingers crossed
Hi friend,
I am also new with digi and getting problem to run demo… i have attached a snapshot which shows error in my comm promt and also in putty, i am using “vista”, does it make much difference .
looking for ur replies
cheerzs
GV