PropBOE USB Connection Not Working
John R.
Posts: 1,376
In my 4-H Robotics sessions, we are having problems with the recently released PropBOE boards and getting connected via the USB port. When the board is connected (regardless of power source or power switch setting), Windows (XP Pro) will fail to install the hardware drivers. This is not the Prop Tool software not seeing the Prop, but the FTDI Drivers are not getting "connected".
These are older computers, with USB1 connections. The same computers will connect just fine with Quick Start boards, as well as one of the initial runs of the PropBOE board that I picked up at a Prop Educators class (This was a limited run of about 50 boards, and there were issues with the power switch and they still had the WiFi connection...)
I've tried un-installing the FTDI Drivers, installing both current (from Parallax), as well as the Beta Drivers from FTDI.
Does anyone have any suggestions?
These are older computers, with USB1 connections. The same computers will connect just fine with Quick Start boards, as well as one of the initial runs of the PropBOE board that I picked up at a Prop Educators class (This was a limited run of about 50 boards, and there were issues with the power switch and they still had the WiFi connection...)
I've tried un-installing the FTDI Drivers, installing both current (from Parallax), as well as the Beta Drivers from FTDI.
Does anyone have any suggestions?
Comments
http://forums.parallax.com/showthread.php?139525-FTDI-Driver-problems-with-Windows-7-64-bit
The fault there was also with the PropBOE, the QuickStart would run but not the BOE. It was finally attributed to the USB 3.0 connectors.
You would think if the QS runs then the FTDI drivers were installed correctly and that the issues lay with either the PC or the BOE.
FTDI have software utilities on their site, mentioned in the above thread that were helpful in resolving the matter. Even though the thread was aimed at Win 7 it could be helpful in your case also.
Jeff T.
If that doesn't work, I guess we need to figure out what Parallax did to make that FTDI chip connection different...
Maybe I'd use FTDI's MProg program to probe the FTDI chip and see what's going on...
Is it possible the EEPROM may have a "bad" parameter, does the PropBOE that does work in your PC have the same device descriptor as the one that does not.
Jeff T.
I will try the powered USB hub tonight. I "think" we've tried that, but am not sure. I may have a chance to try during the day, but the current calendar does not look promising...
I have also submitted this to Parallax Support. We discussed this briefly at the Expo, but at the time, we were "assuming" it was a driver issue.
I don't know yet, again, will look more tonight. I don't know if I'd classify it as a "bad" parameter, but one would suspect something "different"... (other than mfg/product name...)
When I say "bad" parameter it seems to me that the device should at least have a serial number which in the previous post it did not, then again the device did eventually work without any modification. But I feel sure it should have a unique serial number and I would probably pop one in there if it was not present just for the hell of it.
Jeff T.
I agree, it is well worth the try. As for the serial number there is an option for FT_Prog to auto generate a unique number which I think should be in the format two alpha and upto six numeric.
Jeff T.
Based on past work with other FTDI devices, I can state that the Mfg, Device and S/N do not normally affect connectivity. (I've seen blank, and duplicates work with no issues.)
Newer PCs/Laptops do not seem to be a problem (other than the potential USB3 issues reported in the other thread).
http://www.ftdichip.com/Support/Utilities/Reassign%20COMNo%20Utility.zip
Ron wrote a great little utility to see what's connected to what port here
http://forums.parallax.com/showthread.php?133040-Problem-How-can-I-detect-which-usb-port-my-propeller-is-on-programatically
I see one for $8 on Amazon (low price compared to Prop BOE).
Went looking on PropBOE photo to see if there was anywhere to connect a Prop Plug, but don't see anything...
(Personally, I like to add a Prop Plug port even if I have a FTDI chip onboard...)
We are in ad admin account, and we can attach, and connect to virtually any other FTDI device I can get my hands on...
Nope, no space for an expansion card.
Short term, I can get around this because all of my kids except one have their own laptop that works just dandy. Brendan may have a laptop that works, or I can borrow him one of mine, or one from work. That has my current class covered, but does not help with potential "Saturday Afternoon at the Park" sessions coming up this summer.
I have received word through a submission to Parallax Support that Engineering was already aware of, and working on the issue.
I'm guessing Parallax bought the chips preprogrammed...
The only other possible fix for you that I can think of is to try a very, very old FDTI driver...
Maybe you can find an antique version of the Prop Tool install package somewhere...
That maybe a longshot though...
Nada, none, nope...
My immediate problem is resolved only because the various youth's parents stepped forward with laptops the kids could use. I will "poke the bear" and ask support for an update. This is still a problem for Columbia County 4-H in the long run.
PropBOE also has the buffer between FT232 and Prop
Jeff T.
I'm guessing (as in don't know, but think) this isn't the case, as the Quick Start boards work great...
Can you try plugging in a USB 2.0 Hub into your USB 3.0 port and then connecting the PropBOE to the USB 2.0 Hub?
I think that should work, but who knows...
After some delays for a number of reasons on both sides, Parallax support has come up with a solution, at least for the old USB ports. I have not had a chance (and may not get one) to find out if this resolves issues with USB3 ports.
Ultimately, we finally got down to "what's different about the PropBOE" from any other Parallax product. Ultimately, that was a simple question once we got down to it. The PropBOE (the production version, not the first lot from way back when), are the only Parallax product (so far) to have the FTDI chip programmed to ask for the full 500 mAmps of power that "may" be available on a USB Port. All other Parallax products are programmed to ask for 90 mAmps.
The solution involves getting the FT_PROG utility, available here: http://www.ftdichip.com/Support/Utilities.htm#FT_Prog You can then re-program the FTDI chip to only ask for 90 mAmps (or whatever value you choose).
The setting that needs to be changed is the "Max Bus Power" setting in the "USB Config Descriptor" section.
This has worked for my oldie but goodie ports on the 4-H computers. Again, I don't know if the same solution will work on the USB3 Port issues. You should also be aware of the following bullet points:
- The PropBOE has over current protection on the USB power. This is fixed at just under 500 mAmps by a resistor value. As a result, it is entirely possible that you could over draw the setting (i.e. the 90 mAmps) and have the USB port shut down. In order to prevent this, you will need to do one of the following:
- Preferably, provide external power (via the barrel jack) to the PropBOE.
- Alternately, make sure the PropBOE does not require more current than your setting.
- You need to be able to successfully connect to the PropBOE in order to use the FT_PROG utility. The utility uses the virtual serial port to enumerate and program the chip, so if the connection fails at the Windows level, you're out of luck.
I am leaving this thread marked as "unsolved" unless/until someone can verify that this also works for the USB3 port issues. I'm currently not able to monitor these forms as much as I would like (darned day gig and keeping a roof over your head thing), so if anyone can validate this solution for USB3, if you can either PM or e-mail me, I'll get the status changed.