Programming Interface Issues (not the resistor)


Kevin Strong
 

I posted earlier about this, but I think it got lost in the noise of the discussion about the resistor on the programming interface.

I’m having trouble re-programming my Titan.

Windows XP

CV Manager software interfaces just fine with the decoder. I spent the morning programming and fine-tuning the decoder to my satisfaction to the extent the Q2 file loaded onto the decoder would allow. No trouble reading or writing CVs, nor controlling the loco via the PC command interface.

I’d like to upgrade it to the Q3 file. I’ve done this on two other Titan decoders with no issues in the year or so. This one, I get the “cannot read manufacturer ID” error when I try to read it with Quantum Upgrade. I’ve tried two different versions; the older Q2 Upgrade (which I used successfully to upgrade the other Titans) and the newer Quantum Upgrade software.

I loaded the CV Manager and Quantum Upgrade software onto my Windows 10 laptop, and while I think I have the driver installed and operating properly, I can’t get CV Manager to recognize the decoder, and I get the same “cannot read…” error with Quantum Manager. I’m thinking that still may be a driver issue with the Win10 machine despite it saying it’s working fine.

So, as I see it, there are two issues. The first is trying to figure out why the Q2 Upgrade and Quantum Upgrade software on the XP machine can’t interface with the decoder when the CV Manager software does so quite readily. Second, what’s up with the USB interface driver set-up (which I followed to the letter from QSI’s instructions) that’s keeping the CV Manager and Quantum Upgrade software from recognizing the decoder?

Later,

K


Eugene Azzopardi <EugsStation@...>
 

Kevin

I would say from what you have stated that the problem is not with the driver or software but the decoder itself. Have you tried to read/write to one of the other QSI decoders. Is it only this decoder that you are having problems with. I would say that if CV manager on the XP machine is communicating with the decoder then your setup, driver and programmer must be ok, and the decoder is the problem. On the win 10 machine if CV manager or the upgrade software is recognizing that the programmer is connected then again the install should be ok. If the driver has not installed properly then it will give the message of programmer not found.
Let us know if you can read/write to the other QSI decoders, if you can then my guess is the decoder, if you cannot then it may still be a programmer issue, but as you can use the programmer on your XP machine with CV manager then this is not likely.

Cheers,,,,,,,,,,,,,Eugene



On Fri, Dec 9, 2016 at 5:48 PM, Kevin Strong kcstrong@... [QSIndustries] <QSIndustries@...> wrote:
 

I posted earlier about this, but I think it got lost in the noise of the discussion about the resistor on the programming interface.

I’m having trouble re-programming my Titan.

Windows XP

CV Manager software interfaces just fine with the decoder. I spent the morning programming and fine-tuning the decoder to my satisfaction to the extent the Q2 file loaded onto the decoder would allow. No trouble reading or writing CVs, nor controlling the loco via the PC command interface.

I’d like to upgrade it to the Q3 file. I’ve done this on two other Titan decoders with no issues in the year or so. This one, I get the “cannot read manufacturer ID” error when I try to read it with Quantum Upgrade. I’ve tried two different versions; the older Q2 Upgrade (which I used successfully to upgrade the other Titans) and the newer Quantum Upgrade software.

I loaded the CV Manager and Quantum Upgrade software onto my Windows 10 laptop, and while I think I have the driver installed and operating properly, I can’t get CV Manager to recognize the decoder, and I get the same “cannot read…” error with Quantum Manager. I’m thinking that still may be a driver issue with the Win10 machine despite it saying it’s working fine.

So, as I see it, there are two issues. The first is trying to figure out why the Q2 Upgrade and Quantum Upgrade software on the XP machine can’t interface with the decoder when the CV Manager software does so quite readily. Second, what’s up with the USB interface driver set-up (which I followed to the letter from QSI’s instructions) that’s keeping the CV Manager and Quantum Upgrade software from recognizing the decoder?

Later,

K



Kevin Strong
 

I could read/write to an old-school Quantum decoder in my BLI C-16 a month back with CV Manager, but I never bothered with checking it against the Q2 Upgrade software since it wasn’t upgradable. (I “upgraded” it by replacing it with a Tsunami2.) My two Titans are installed in battery R/C installations, paired with G-wire receivers. They’re not exactly accessible without a fair deal of work disassembling locomotives, which I’m currently disinclined to do. I’ll live with the Q2 sounds; they’re not at all unreasonable. I just wanted different whistles.

 

Having said that, I’m still curious what may be up with my Win10 laptop; why does CV Manager work on the XP but not Win10 on the same decoder? It is a newer version, but I wouldn’t think the differences between them would preclude one from working versus the other. And if so, that’s probably a bug that needs to be fixed, since it’s the newer version that’s not working.

 

Later,

 

K


Nick
 

Kevin,

I am using W-10 with the programmer. I bought a new system with W-10 and loaded the new CV manager and Q2 upgrade (the new version) and it works fine. I have an ancient XP system that was my old system. I took the old files and moved them to the new machine and I can read/write to any decoder. I also have the Q1 software and writing to the upgraded OEM decoders is no problem either. Your problem sounds like it is in the decoder.

Only tip I can think of is to watch the RED LED when trying to write to the flaky decoder. If it starts flashing fast, it is "confused" by some thing . I kill power to the programmer and reload the upgrade . If it works with CV manager and not the upgrade software, try to re-install the upgrade software. It might have been an incomplete install. I had that happen once and it took me days to figure it out.

Good luck,
Nick Kulp