2.6.19 wont load project

[LT401Vette]

the .jar does need to be there for sure, but be careful it isn't on twice if Windows is set to hide know types as it is by default...

Otherwise when TS is hanging, post the TunerStudioAppDebugLog.txt and we can see if there is any more info on why it is hanging.

[tmbryhn]

It only hangs if the filename for the D2XX.jar is wrong or simply altered. Well, it does not hang, it just won't proceed in the boot up sequence when loading a project - kinda because it can't find what it's looking for.

Are you testing the very same chipset? FT230X?
I have used the FT232RL chipset earlier with great success on the D2XX drivers in TS.

[LT401Vette]

Yeah that is just it, it hangs if it doesn't find the file.

I am testing against an MS3 with the older chipset. The only variable I could think of was updating the D2XX drivers bundled with TS to the latest, that is why I gave it a shot.
It seems like it should work with d2XX, the datasheet says it uses D2XX

[tmbryhn]

Indeed it does.

Would you care to either photograph or write down what data is written on your particular package?

[LT401Vette]

Just the AppDebug

[tmbryhn]

I was reffering to the chip package and what's printed on it.

[tmbryhn]

Nothing new in this case?
Does anyone know of any list of known FTDI chipsets that works with TS?
I'm already aware of the FT230RL chip and I'm considering it for the next batch of boards. Price is the biggest problem.

Phil, I know I have asked before, but could you please photograph the chip that you're using for your successful D2XX tests?

[jsmcortina]

What boards are you making?

James

[tmbryhn]

USB-adapter w. bluetooth option.

[tmbryhn]

I have started the re-design for the FT232RL chip.

I will implement a hardware reset function if the module latches. During my testing, this have been possible when I literally take the USB cable and wrap it around the ignition coils in my bench, lol! Sometimes, the FTDI-chip will latch and won't function because fot the intense EMI absorbed by the USB cable. When that happens, the only solution is to unplug and re-connect, consequently resetting the chip. Since the chip have its own reset pin (active low), I'm working on implement a sense circuit that resets the chip if the data string stops flowing, thus indicating a loss of communication between the PC and the MS.
The tests have been done successfully, and the link comes right back up after the reset

How is this being done on the MS3-pro if the FTDI-chip resets? I reckon the Pro uses the FT232RL chip also - at least it looks like that in the pictures?

[Suprazz]

I also have the same issue on my windows 10 machine.

Everything was working well then this message appears.

If I create a new project, everything is ok but I cannot reuse my older projects that have this error...

[NMBRPL8]

To raise a zombie from the dead, I just ran into this problem too, windows 10. Nothing I did was working, remove and reinstall drivers etc. I ended up trying a different usb-serial ftdi cable - connected right up. Tried the previously problematic cable - all working fine again. Odd. But overcome