And still not a single case of a consumer grade product affected by this, it's been a week, someone should have encounter one by now.
Actually when they say bad publicity is good publicity they might be right, it might actually help them.
They been on the news stating they are going to ensure their drivers won't talk to clones.
It shows a potential client that, the device is good enough to be cloned and that after FTDI clamps down to use only genuine chips the client will feel confident they are using genuine chips.
And still not a single case of a consumer grade product affected by this, it's been a week, someone should have encounter one by now.Probably because consumer goods use their own PID/VID which somehow are not affected. Somehow FTDI managed to shoot both their feet off by hitting the people they need to put their chips into actual designs the hardest
Then again if it is a consumer/consumeable device people just trash it and buy new. If one of my USB-to-serial cables stops working I'm not going to disect it; I just get a new one.Actually I'm pretty sure one if Bayer is using it then lots of medical device mfgs are using it too and they probably have very tight control on the supply chain. With a custom VID/PID the device will only work with the provided customized drivers so these won't update unless the mfg itself updates them. So if that is the case then even if the hobbyists market evaporates medical devices move so slow it will be decades and probably never when they even being to consider other options. (Medical devices move so slow, so much RnD on the simple things, so much double/triple/quad checking, its great but it is slow)
And still not a single case of a consumer grade product affected by this, it's been a week, someone should have encounter one by now.
In fact one member on my forum might have his product (Lumibox, a LED driver PWM controller) bricked.
It starts here (in french, sorry) http://aquaohm.xooit.eu/t1986-Rampe-LED-R-cifal-850-litres.htm?start=40#p31713 one day the product is OK, the next it's not recognised anymore (tested on 3 differents PC, tested another USB cable, etc.)
because it is not the *public at large* that designs their chips into products-- it is [in fact] people like me
I'm not going to design their chips into my client's products anymore. ... I would still be designing FTDI chips in-- I never would have started to look around for alternatives, and I never would have found the quite wonderful, low cost CP2104 from SiLabs, which does everything I needed the FTDI chip to do, but at 1/4 the price!
And still not a single case of a consumer grade product affected by this, it's been a week, someone should have encounter one by now.
In fact one member on my forum might have his product (Lumibox, a LED driver PWM controller) bricked.
It starts here (in french, sorry) http://aquaohm.xooit.eu/t1986-Rampe-LED-R-cifal-850-litres.htm?start=40#p31713 one day the product is OK, the next it's not recognised anymore (tested on 3 differents PC, tested another USB cable, etc.)
Actually when they say bad publicity is good publicity they might be right, it might actually help them.
They been on the news stating they are going to ensure their drivers won't talk to clones.
It shows a potential client that, the device is good enough to be cloned and that after FTDI clamps down to use only genuine chips the client will feel confident they are using genuine chips.
And still not a single case of a consumer grade product affected by this, it's been a week, someone should have encounter one by now.Probably because consumer goods use their own PID/VID which somehow are not affected. Somehow FTDI managed to shoot both their feet off by hitting the people they need to put their chips into actual designs the hardest
Then again if it is a consumer/consumeable device people just trash it and buy new. If one of my USB-to-serial cables stops working I'm not going to disect it; I just get a new one.Actually I'm pretty sure one if Bayer is using it then lots of medical device mfgs are using it too and they probably have very tight control on the supply chain. With a custom VID/PID the device will only work with the provided customized drivers so these won't update unless the mfg itself updates them. So if that is the case then even if the hobbyists market evaporates medical devices move so slow it will be decades and probably never when they even being to consider other options. (Medical devices move so slow, so much RnD on the simple things, so much double/triple/quad checking, its great but it is slow)There is life support medical and consumer medical. Consumer-medical isn't much beyond consumer grade equipment. Most of the low cost tele-healthcare medical devices like blood sugar and blood presure testers are made in China so the chance there is a FT232 compatible chip in there is very large (if it needs USB to UART and the designers choose for the FT232). The market for tele-healthcare devices is very competitive so every penny counts.
@a210210200:
You know, not once have I ever mentioned your online "handle" when accusing the FTDI "fixer" of hiring "shills" to inundate this forum with false propaganda and diversions from the real truth about FTDI's driver that contains a trojan malware. Yet, every time I did broach this subject, for some reason you felt the need to chime in, and proudly declare that you were not such person. So, since I didn't ever name names, why did you feel the need to defend yourself every time I did this?
[My TLDR response to you goes here] Followed by you saying the pronoun shown below.
You are obviously a "shill" for FTDI. AND, you are *WRONG*. Your use of the phrase "faking the VID/PID" shows a lack of understanding in how USB works. There are many other signatures that an O/S can use to determine what the device is-- not just the VID/PID, and your [FTDI's] MALWARE driver proves this-- as it has no problem identifying a chip that was not made by FTDI.
Aww Rufus? You're still here trolling? SMH...
My story is, I don't know if my chips are genuine or not.
I bought them from a legit source, and paid the $8-9 they normally cost. But I still can't tell if they're genuine or not, because I don't have access to their supplier's supply chain data. All it takes is for one person to screw up. I've had some trouble getting them to work, and when I looked into it, there's at least one device with a PID of 0x000. PID 0x0000 also happens to occur when there's a comm error, so how's a brother to know?
I installed Ubuntu on my main machine JUST TO CHECK IT OUT. At this point I've already lost a dozen hours or more. Ubuntu reports that the chip is ok, and I'm likely having some other problem. I asked FTDI how I can tell if they're fakes, and they told me that they're working on a detection tool, supposed to be released any day now. So I wait..
They're probably genuine, and I STILL lost all this time/money. I did my due diligence and still I'm stuck waiting for FTDI to release it's detection tool. If I were a big company, this would literally have cost me tens of thousands of dollars through no fault of my own.
Rufus, bite me. FTDI did the wrong thing. Even if I have the real deal, it still sucks ass. You call is bluster, but it's not: I don't trust FTDI anymore and will go FAR out of my way not to design them into future products. That's not bluster, that's pragmatism.
Here is a real live example of the problem that FTDI now faces. I wish to purchase a GPS module for a project and I have two choices, the cheapest unit includes in the manual the instruction "download the latest USB driver from www.ftdichip.com/FTDrivers.htm". A slightly more expensive device uses a driver specifically written for the module concerned.
I have purchased the more expensive product, the FTDI brand is now poisoned.
Here is a real live example of the problem that FTDI now faces. I wish to purchase a GPS module for a project and I have two choices, the cheapest unit includes in the manual the instruction "download the latest USB driver from www.ftdichip.com/FTDrivers.htm". A slightly more expensive device uses a driver specifically written for the module concerned.
I have purchased the more expensive product, the FTDI brand is now poisoned.The opposite is true. How long do you think a GPS module which immediately bricks itself and gets returned for refund is going to remain on the market? Probably already and certainly in the future something which claims to use an FTDI chip will very likely have a genuine FTDI chip while things that don't are more likely to have a fake or clone chip of unknown quality and origin.
I am now even more likely to choose a device using an FTDI chip because I will take it as an indication of quality - as it ever was.
Here is a real live example of the problem that FTDI now faces. I wish to purchase a GPS module for a project and I have two choices, the cheapest unit includes in the manual the instruction "download the latest USB driver from www.ftdichip.com/FTDrivers.htm". A slightly more expensive device uses a driver specifically written for the module concerned.
I have purchased the more expensive product, the FTDI brand is now poisoned.The opposite is true. How long do you think a GPS module which immediately bricks itself and gets returned for refund is going to remain on the market? Probably already and certainly in the future something which claims to use an FTDI chip will very likely have a genuine FTDI chip while things that don't are more likely to have a fake or clone chip of unknown quality and origin.
I am now even more likely to choose a device using an FTDI chip because I will take it as an indication of quality - as it ever was.
Just gotta love the logic here... A==B, B==C, therefore Z==42....
As simple as i see it is, i think, as simple as (almost all) people see it: you just can't buy or design nothing with a FTDI device on it. As simple as that.
This cycle will repeat until the FTDI drivers will produce false positives for devices with genuine FTDI chips inside. Do you want to take that risk?
As simple as i see it is, i think, as simple as (almost all) people see it: you just can't buy or design nothing with a FTDI device on it. As simple as that.
So when you ship product built with fake crap of unknown quality and origin you would rather there was less risk of the customer finding out. Thanks for confirming that and that I should continue to consider use of FTDI chips as an indication of quality.
It's ok, I understand french, I'm not saying that it didn't affect people, but not the general consumer.
I don't know what the Arduino Nano 328 based Lumi-Box is, but it seems like it's targeted for people that are experimenting with micro controllers.
Nevermind I did find the Lumi-Box and it seems Arduino based:
http://lumi-box.net/boutique/lumi-box-v2/
What I was asking was for a consumer grade product, because those are the ones that probably can take legal action. Easier than someone that hangs on electronic forums that will know quick how to revert what FTDI did.
Does it show up as an FT232R in the device manager on windows with no driver found error? If it doesn't enumerate (as in be detected not fully work) at all on multiple systems then something else is wrong.
It's ok, I understand french, I'm not saying that it didn't affect people, but not the general consumer.
I don't know what the Arduino Nano 328 based Lumi-Box is, but it seems like it's targeted for people that are experimenting with micro controllers.
Nevermind I did find the Lumi-Box and it seems Arduino based:
http://lumi-box.net/boutique/lumi-box-v2/
What I was asking was for a consumer grade product, because those are the ones that probably can take legal action. Easier than someone that hangs on electronic forums that will know quick how to revert what FTDI did.
Yeah so what? you don't have to use SMD everywhere just because the majority of the constructors do that...
I would like to give a perspective as an end user.
I have an interest in electronics - hobbyist level and some experience in computers...
I don't understand the comments that if something is broken then the user is less than useless if they don't do a google search to see what the problem may be.
...have hired PR firms [that hire others] to attempt to hijack this thread
...have hired PR firms [that hire others] to attempt to hijack this thread
Is this a known fact or a tin foil conspiracy? (edit: fixed it for you, took me a while to make sense of it)