is max URL length (72 char) ?

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Send URL with length > 73 characteres
Is there URL size limitation ?

From what I've seen 72 bytes seems the max.
I send URL via X-CTU Send Pack windows. This works fine if URL lenght <= 73 
characteres length.
More than 73, log is saying RECV: 72 bytes, and stuck (e.g no XMIT SEND).

What is the expected output? What do you see instead?
No reply fro URL. Log show XIG stuck, with RECV always at 72.

What version of the product are you using?
1.2.1

Please provide any additional information below.

Original issue reported on code.google.com by mersingt...@gmail.com on 2 Sep 2011 at 9:38

[GoogleCodeExporter]

I am not able to reproduce this bug on the current SVN trunk.  My guess is it 
is one of the following:

1) Something I've inadvertantly fixed with a new command parser in the upcoming 
XIG v1.3.0

2) X-CTU is not allowing you to send strings longer than 72 characters.

For starters I'd recommend you retest with another terminal program (e.g. 
putty) and then try the new XIG version when we're ready to release it!

Let us know how it goes...

Original comment by Jordan.H...@gmail.com on 5 Sep 2011 at 2:05

• Changed state: Invalid

[GoogleCodeExporter]

Hello,

I did test with putty, copying a 82 char URL lenght from the clipboard. Same 
issue. See attached some details.

I'll retest with 1.3.1

Original comment by mersingt...@gmail.com on 6 Sep 2011 at 8:28

Attachments:

• 3.JPG

[GoogleCodeExporter]

What baud rate is your XBee running at?  Are you using serial flow control?  
What could be happening here is that your pasted/line buffered URL may be 
overrunning the XBee's pitiful little serial input buffer and the extraneous 
data may be getting thrown away.

What you can also try is:

1) Enable CTS/RTS flow control by using X-CTU to set D6=1 and D7=1
2) Write the parameters to the XBee
3) Ensure that putty or X-CTU has CTS/RTS flow control enabled in the serial 
setup

And then retest!

You will see the RECV: messages from the remote XBee come across in 72 byte 
blocks but you should see multiple blocks (e.g. for a URL of 82 chars you'll 
see one of 72 bytes then one of 10 (or 11 with the newline)).

Best of luck and let us know what you find.

Jordan

Original comment by Jordan.H...@gmail.com on 6 Sep 2011 at 10:50

[GoogleCodeExporter]

Baud rate is 115200.
I did enable CTS/RTS (on the Xbee and  putty/X-CTU).
I did test again : same result.

(FYI, I initially sent this URL from an Arduino, println ( strURL ). As this 
was not working, I did start 'debugging', then sending via X-CTU.)

I'll wait for 1.3.1 release then.

Original comment by mersingt...@gmail.com on 7 Sep 2011 at 7:54

[GoogleCodeExporter]

I want to tell you that I just retest this with v1.3.0b1 and URLs of greater 
than 72 characters seem to work fine.  Please let me know if you can confirm 
this!

Original comment by Jordan.H...@gmail.com on 12 Sep 2011 at 5:16

[GoogleCodeExporter]

I have the same problem with version 1.3.0b2, no more than 72 character in the 
URL, 

Original comment by Celine.h...@gmail.com on 29 Nov 2011 at 6:25