Discussion for the Tau Labs android application

xbee usb hardware info

no avatar
User

pug398

Posts

700

Joined

Fri Mar 07, 2014 2:26 am

xbee usb hardware info

by pug398 » Sat May 03, 2014 6:12 pm

Just so I do not hijack other thread. Peabody perhaps you can find out if Parallax xbee adapter having different vid:pid cause my problem with xbee radios not working directly with android app. The vid:pid is 0403:6001 and bus device name is FT232R USB UART

They work indirectly by using BT bridge but trying to resolve other issue.
User avatar
User

peabody124

Posts

1339

Joined

Tue Feb 18, 2014 12:33 pm

Re: xbee usb hardware info

by peabody124 » Sun May 04, 2014 3:19 pm

Ok I'll give it a look. I created a bug issue here: https://github.com/TauLabs/TauLabs/issues/1184 to track it. Can you post there whether it pops up a connect dialog even?
no avatar
User

pug398

Posts

700

Joined

Fri Mar 07, 2014 2:26 am

Re: xbee usb hardware info

by pug398 » Sun May 04, 2014 11:06 pm

Posted what I know there. Last thing it says is opening serial device but FirmwareIAPObject has all zeros. Never gets to loading UAVO set.
User avatar
User

peabody124

Posts

1339

Joined

Tue Feb 18, 2014 12:33 pm

Re: xbee usb hardware info

by peabody124 » Mon May 05, 2014 12:07 am

Ok interesting. Then it's something about the serial communications itself failing. Maybe a problem in the FTDI driver then. I'll have to see if I can get mine paired etc. I remember that always sucked. Any good how to links?
no avatar
User

pug398

Posts

700

Joined

Fri Mar 07, 2014 2:26 am

Re: xbee usb hardware info

by pug398 » Mon May 05, 2014 2:32 am

I found the new XCTU Next Gen utility to be relatively easy. Plug xbee into usb adapter and then plug both into computer. Use the auto discover in left pane to find it first then you can set settings in right pane after you select the radio on left. Set each xbee destination address to the other xbee device address (serial #) and make one the coordinatortor (gcs) and the other the end node. It will auto discover the device as long as you check the boxes for possible comport and baud. In the pic below I set everything in blue bars and further down the baud is set to 57k. I also updated the firmware. I have not yet changed the pan id on both of them but it would be good to set it to something unique if in populated area. I do not have that problem :)

http://www.digi.com/support/productdeta ... =utilities
Attachments
XCTU_xbee.png
XCTU_xbee.png (205.33 KiB) Viewed 2885 times
no avatar
User

pug398

Posts

700

Joined

Fri Mar 07, 2014 2:26 am

Re: xbee usb hardware info

by pug398 » Tue May 06, 2014 2:14 pm

After tracking down both sets of schematics it looks like manufacturers use the same FT232R series chip in same configuration. I will do away with parallax usb adapter and use xbee Din/Dout lines only and see what happens. The xbee radio may handle CTS, RTS signals differently than the 3DR radio.

update: Disabling all flow control pins made no difference with android gcs. Still hangs after opening port. Still works fine with computer gcs.
Last edited by pug398 on Wed May 07, 2014 12:19 am, edited 1 time in total.
User avatar
User

peabody124

Posts

1339

Joined

Tue Feb 18, 2014 12:33 pm

Re: xbee usb hardware info

by peabody124 » Tue May 06, 2014 4:21 pm

Yeah that is what I'm suspecting makes the difference. I need to look at what the android ftdi driver does.

Sent from my Nexus 5 using Tapatalk
no avatar
User

pug398

Posts

700

Joined

Fri Mar 07, 2014 2:26 am

Re: xbee usb hardware info

by pug398 » Tue Oct 28, 2014 6:16 pm

Peabody this is your reminder message :D

If you look at redoing the android communication side could you see if standard CDC usb serial device support can be included in addition to FTDI.

Who is online

Users browsing this forum: No registered users and 1 guest

Powered by phpBB ® | phpBB3 Style by KomiDesign