search

ngocthanhit / xig

Automatically exported from code.google.com/p/xig
0 stars 0 forks source link

XIG for Windows (7) not finding XBEE ZIGBEE/Hanging at "my IP is: ..." #41

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Plugging in Xbee (xb24 - zb Coordinator API) via xbee explorer
2. Starting XIG
3. Browser opens but page fails to load.

What is the expected output? What do you see instead?
I expect to see the XIG output a few more lines and finishing with "ready" or 
equivalent. I expect the browser to correctly load the page and allow me to 
select my Xbee device. 
Instead, the XIG hangs at "My IP is: ..." and the browser does not load 
"http://localhost:8000".

What version of the product are you using?
I have tried running the latest (beta) XIG and also tried the previous (stable) 
XIG, neither of which work. Both of which produce above result.

Please provide any additional information below.
If I quickly close the XIG cmd prompt while the page is trying to load in the 
browser, it will start to load. Re-opening the XIG app quickly will then cause 
a new tab to open that fails, but the initial tab completes loading the page, 
however it still does not detect the Xbee.

I'm using (I belive) XBee ZB, which are series 2? In xctu it says XB24-ZB.
I followed the official set up instructions for windows.

Thanks.

Original issue reported on code.google.com by jonisyke...@googlemail.com on 25 Oct 2013 at 10:11

GoogleCodeExporter commented 9 years ago 
Hi I am having the same problem.

Regards

Original comment by pentacom...@gmail.com on 3 Jan 2014 at 7:56

GoogleCodeExporter commented 9 years ago 
Hi there also experiencing the same problem with my Connectport X2 and Series 2 
XBEE's in API Coordinator as well as AT Router.

Original comment by nick.sul...@gmail.com on 3 Mar 2014 at 4:32

Attachments:

GoogleCodeExporter commented 9 years ago 
Looks like you are running at 115,200 baud. The highest supported baud rate is 
57,600.

There might be other issues, but let's check that baud rate first, and make 
sure you've read the instructions carefully. Can you post any more information 
about the ConnectPort X2 problem you mention? Log file or screenshot when 
launching the xig.py from the ConnectPort's command line interface?

Original comment by robfal...@gmail.com on 4 Mar 2014 at 4:10

GoogleCodeExporter commented 9 years ago 
Hi Rob,

Thanks for your response.
I've had sort of a bit of progress you might say. Reading your help on the XIG 
webpage, I've set the XBEE S2 to API Coordinator mode. Doing this seems to have 
enabled some progress, unfortunately to no avail. Screengrab shows XBEE Status 
: "Joined or Formed Network". Also the Logs show some further progress but as 
mentioned the steps aren't successful. Also changing the Baud Rate hasn't had 
any impact

cheers
Nick

Original comment by nick.sul...@gmail.com on 5 Mar 2014 at 12:37

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hi again,

Digi's Device Discovery tool now also finds "XIG PC Gateway". Status : "Not 
Properly Configured".

Original comment by nick.sul...@gmail.com on 5 Mar 2014 at 12:43

Attachments:

GoogleCodeExporter commented 9 years ago 
Device Discovery will not be relevant in this case so that can be ignored.

Have you followed the setup steps for Series 2 radios listed here? 
https://code.google.com/p/xig/wiki/Windows_Installation

Especially have you configured ATD6 1 (turns on monitoring for RTS)?

Original comment by robfal...@gmail.com on 10 Mar 2014 at 5:18

GoogleCodeExporter commented 9 years ago 
tried series 1 and wi-fi radios, all with the same results posted here...

Original comment by ransomh...@gmail.com on 28 May 2014 at 12:19