search

ngocthanhit / xig

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

XIG stops responding after invalid URL entered #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install XIG on X2 ConnectPort, add to startup. Reboot.
2. Add XBee to ConnectPort and check it is associated.
3. Use X-CTU to enter valid URL - works OK - Source received. 
4. Enter invalid URL - no response. Nothing is returned not even a error.
5. XIG is now unresponsive and anything entered is ignored.
6. Reboot Connect port to bring XIG back to life.   

What is the expected output? What do you see instead?

See above

What version of the product are you using? On what operating system?

Latest XIG version
ConnectPort: 
  Model:   ConnectPort X2 
  Ethernet MAC Address:    00:40:9D:xx:xx:xx 
  Firmware Version:   2.9.0.11   (Version 82001596_F3 02/12/2010)  
  Boot Version:   1.1.2   (release_82001228_A)  
  POST Version:   1.1.3   (release_82002307_C)  
  Product VPD Version:   release_82002209_C 
  Product ID:   0x00A1 
  Hardware Strapping:   0x07BF 

XBEE:
  Physical Address:   00:13:a2:00:xx:xx:xx:xx!   
  Node Identifier (NI):      
  Parent Address (MP):   0xfffe   
  Type:   router   
  Profile Id:   0xc105   
  Manufacturer's Id:   0x101e   

  RF Module 
  PAN identifier (OI):   0x3333   
  Extended PAN identifier (OP):   0x96fdb5c6f7da3dfb   
  Operating channel (CH):   0x0015   
  Network address (MY):   0x38bd   
  Parent address (MP):   0xfffe   
  Association indication (AI):   0x0000   
  Firmware version (VR):   0x2270   
  Hardware version (HV):   0x1944   
  Device type identifier (DD):   0x30000   
  Number of remaining children (NC):   12   
  Maximum RF payload (NP):   84   
  Supply voltage (%V):   3263   
  Received signal strength (DB):   44   
  ACK failures (EA):   1

Original issue reported on code.google.com by gra...@pinnock.com on 29 Jan 2011 at 4:06

GoogleCodeExporter commented 9 years ago 
I changed the Extended PAN ID to 0xaaaa (as per examples) but the results are 
the same. I've narrowed the issue down a bit. The problem does not occur for 
all invalid URLs (in fact most are handled OK), but the following breaks it 
every time:

http://duff:duff/

The only way I have found to get it working again is to reboot the ConnectPort 
(A bit drastic).

Hope this helps.

Original comment by gra...@pinnock.com on 1 Feb 2011 at 10:08

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r36.

Original comment by Jordan.H...@gmail.com on 8 Feb 2011 at 11:26

GoogleCodeExporter commented 9 years ago 
Fix released in v1.1.1 of XIG.

Original comment by Jordan.H...@gmail.com on 8 Feb 2011 at 11:41

GoogleCodeExporter commented 9 years ago

Original comment by Jordan.H...@gmail.com on 6 Mar 2012 at 2:43

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision 5ed1814cce62.

Original comment by Jordan.H...@gmail.com on 29 Mar 2012 at 12:53

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision 7c92d7686dee.

Original comment by Jordan.H...@gmail.com on 29 Mar 2012 at 12:54