Date   

Re: QSI Titan availability?

Terry Humerickhouse
 

My supplier no longer deals with QSI because of the lack of communication on Josh's part


On Dec 16, 2016, at 8:24 PM, cineplex23@... [QSIndustries] <QSIndustries@...> wrote:

 

Im also looking for decoders, everybody seems to be sold out.


Re: QSI Titan availability?

ELIE
 

Im also looking for decoders, everybody seems to be sold out.


Re: Switch off "holiday" sounds in BLI ON30 locomotive with Quantum sound

g_pruss
 

Nigel,

If I remember correctly, it is triggered by turning the bell on in FWD/REV and then blowing the horn for
2 to 3 seconds before lowering the throttle to enter neutral.

Gerry Pruss
QSI 


Re: Switch off "holiday" sounds in BLI ON30 locomotive with Quantum sound

hbblb35e6whcicwpzoxfxrtkzybyttx3vx4pxyl2@...
 

Gerry

Thanks for the information, much appreciated.

Just out of interest what triggers the holiday sounds ? 


Re: Switch off "holiday" sounds in BLI ON30 locomotive with Quantum sound

g_pruss
 

Nigel,

For information on Q1a upgrade firmware go to
http://www.qsisolutions.com/

Click on "Products" and then click on "Q1aUpgrade Chips".
 
Gerry Pruss
QSI


Re: Switch off "holiday" sounds in BLI ON30 locomotive with Quantum sound

hbblb35e6whcicwpzoxfxrtkzybyttx3vx4pxyl2@...
 

Hi Gerry

Thanks for the information.

Is the firmware a software upgrade or is it burnt onto a ROM or something ?

Either way I would be interested in finding out how to do it.

Thanks again - Nigel


Re: Switch off "holiday" sounds in BLI ON30 locomotive with Quantum sound

g_pruss
 

Nigel,

With model 304 firmware for the BLI ON30, the only way to avoid the holiday announcement is to avoid executing the bell and horn actions that trigger these sounds. There is no CV or Analog Programming Option
to disable this feature.

The alternative is to upgrade your locomotive with model 303 firmware for the BLI ON30. Model 303 and model 304 firmware are identical except that model 303 does not have the holiday announcement feature.

Gerry Pruss
QSI


Switch off "holiday" sounds in BLI ON30 locomotive with Quantum sound

hbblb35e6whcicwpzoxfxrtkzybyttx3vx4pxyl2@...
 

Hi all


I have a BLI ON30 locomotive with "holiday" voice announcements in the Quantum sound system.


I would like to make sure these sounds are off. 


The only information that came with the locomotive seems to indicate they only happen when run in DC but I would like to just get rid of them.


I have hunted all over the Internet to try to find how to do it but found nothing.


Could anyone advise ?


Thanks - Nigel   


Re: Programming Interface Issues (not the resistor)

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


Re: Programming Interface Issues (not the resistor)

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


Re: Q Programmer: no communication

Jon Heller
 

In electronic service the method to use in diagnosis is "divide and conquer". First thing to do is check the input, then the output. Work your way back from there. Of course a schematic is best to guide you, but there should at least be a troubleshooting guide available.

I had been in the service and repair business since 1974. I've written QSI offering to help with support program development and implementation. Never heard a word.

Jon Heller
San Diego


On Fri, Dec 9, 2016 at 7:02 AM, christophermcrane@... [QSIndustries]
wrote:
 

So this morning I tested the output resistor with a multi-meter set to 200 ohms. I got a reading of 2.5. That seems to tell me the resistor is still functional.
If that is the case, I am still stumped why I cannot communicate with any decoders on my test track.

Should I now try to measure voltage from the programmer to the test track during a read operation?


Re: Q Programmer: no communication

christophermcrane
 

So this morning I tested the output resistor with a multi-meter set to 200 ohms. I got a reading of 2.5. That seems to tell me the resistor is still functional.
If that is the case, I am still stumped why I cannot communicate with any decoders on my test track.

Should I now try to measure voltage from the programmer to the test track during a read operation?


Re: Programming Interface Issues (not the resistor)

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



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


Re: Q Programmer: no communication

Art
 

Anyone know where to purchase QSI Large Scale ET Q3 decoders ?

Art DeFazio

________________________________________
.


Re: Q Programmer: no communication

sverker.runeson@...
 

Good picture, thanks.

Obviously, when the resistor blew the heat unsoldered it from the pads and also broke it in two.
Reading it from the picture, the first character on it is a 2 and the last (third) character on it is a 0 (zero).

On my (unbroken) unit the characters are 2R0 meaning 2.0 ohms.

Clearly, the broken one was the same.

Makes sense: in agreement with Kelly saying 1/2 amps is the maximum allowed, at half an amp through the two ohms makes 1/2 watts of heat.  The size of the resistor is SMD-type 1210 which can take 1/2 watts. At more current it will overheat and blow up, the sooner the more the current exceeds a half amp.
This is a simpler type of protection than a fully short cirquit proof design.

To summarize the story, the critical resistor (limiting track output current in cases of shorts or overloads) is:
 2.0 ohms, 1/2 watts, SMD-type 1210.

What Kelly is saying is that if we want to avoid blowing the resistor each time we have a short on the tack output we need to insert a halfamp fuse in the leads to the track.  To make sure the fuse blows before the internal resistor  I will make sure to not use a slow-blow fuse and with a somewhat lower fuse value, say 400 mA.

Sverker



Where to find the E bell?

Steven Lansing
 

I haven't been able to find an E bell in the bell selections yet.Is there an E bell selection at all for the 'BellMaster'?

 


Re: Q Programmer: no communication

Ray Pilgrim
 

Colin

Go to the group Files section and look for QSI Programmer - Broken Component.JPG as it will show where the resistor was, parts of it are visible.

Regards,
Ray P


Re: Q Programmer: no communication

John Burkhardt
 

Christopher,



As I described to Sverker, the resistor is on the center line of the PCB and is large, there is no other resistor that large on the whole board on which you can read the number designation for the value – in my case 100 for the 10 Ohm or 2R0 for the 2Ohm respectively. You can measure the resistor in situ, no need to unsolder it and should get a value reading somewhere between 2 & 20 Ohm.



HTH!



Thanks and regards,



John Burkhardt

South Africa

where the sun always shines,

and steam still reigns!









From: QSIndustries@... [mailto:QSIndustries@...]
Sent: 02 December 2016 04:00 PM
To: QSIndustries@...
Subject: Re: [QSIndustries] Re: Q Programmer: no communication





Thank you Colin, though I still do not know which resistor would be the culprit


Re: Q Programmer: no communication

christophermcrane
 

Thank you Colin, though I still do not know which resistor would be the culprit

2681 - 2700 of 19606