Date   
Future of QSI

Rick Knight
 

 Hi Kelly, As an installer i am wrestling with whether to install QSI Titans or not. What do you see in the future for QSI and the Titan decoder. Where do I source the decoders? I have updated to a windows 10 computer and printed out "fly Rockets" eleven step instructions. Is that what you used to get your windows 10 working with the programmer. Thanks, Rick.

Re: Driver for Quantum Programmer Success!

William Lohman
 

Thanks, for the quick response Kelly and for all you do for us out here under the Fig Trees!  I understand you don't have a lot of resources to throw at the problem.  But, with all that expertise you have at QSI seems you could find a legal shortcut/way around it.    You and many of us out here have (gladly) spent a lot of time helping persons with the WIN workaround for years now.  Just saying maybe the time could be better spent fixing and documenting the process.  Easy for me to say.  In the meantime, keep up the good work.  Bill

Re: Driver for Quantum Programmer Success!

Bill Kohler
 

I'm watching this thread closely. While the SiLabs driver works perfectly on both my laptop and desktop (Win 7 Home), I have just received the notice that MS will drop support of Win 7 in mid-January 2020. 
At some point, I'll have to upgrade to Win 10 and I just can't wait to have all this fun... (NOT!)

Re: Driver for Quantum Programmer Success!

Simon Brown
 

FWIW i run Win 7 Pro (32bit) via a VM on my Mac and the QSI SW works fine. As does my ESU tools, Roc Rail and some other Lenz SW (also outdated and old)
I also have to use this machine for production work at home so this isnt a vanilla Mac either so the chances of me running up against issues is probably higher than most - point of this last statement is that whilst the drivers are giving some grief they aren't giving all of us grief.
Regards
Simon

Re: Driver for Quantum Programmer Success!

kjlovesya
 

Hi Kelly,

  Instead of the Silabs diver, perhaps QSI could use a driver that is already 'signed' by Microsoft.   Win Win?

KJ

P.S. I've got a Windows 7 Pro laptop and I can't get the bloody thing to work with the Silabs driver QSI recommends.   I can get JMRI and the NCE PowerCab USB to work, but not QSI.   It's frustrating!

Re: Driver for Quantum Programmer Success!

kelly dorf
 

Hi Bill:

We at QSI are focused on one thing. 1st class decoders, sound and ease of use.  We do not have the staff it takes to get a driver signed by Microsoft. In case you are wondering how much red tape or programming skills are involved, take a peek at this:  https://docs.microsoft.com/en-us/windows-hardware/drivers/device-and-driver-technologies
As always, we at QSI welcome your comments.

Oh, and BTW, I was successful in completing my Win 10 install last night.

Kelly

Re: Driver for Quantum Programmer Success!

William Lohman
 

As any "veteran" QSI decoder user/installer/programmer knows this driver issue has been around for several years and through several versions of Windows.

So for you at QSI, Kelly and all, why don't you fix it so the software can be installed without all the hassle -- like with other decoder brands.  Clearly you're sophisticated enough to have designed and built the QSI decoder software/firmware.  Still one of the most sophisticated decoders around.

C'mon QSI support what you sell. 

Re: Driver for Quantum Programmer Success!

Lou
 

Bitlocker is the encryption program in Windows since Vista.

 

Lou

 

From: QSIndustries@...
Sent: Wednesday, April 24, 2019 1:54 AM
To: QSIndustries@...
Subject: [QSIndustries] Re: Driver for Quantum Programmer Success!

 



Isn't "bitlocker" a virus or ransomware?!

Peteski

---In QSIndustries@..., <kelly.dorf@...> wrote :

Good for you Bruce.   I am still fighting a new windows 10 laptop.  After going thru the unsigned driver drill, I hit a new roadblock called "bitlocker". I finally got past that, installed everything, and I am getting the warning incompatable driver ver 0.0.0.0.    

OMG why does Microsoft make things so much harder?

I will keep banging away at it.

 

Kelly




Re: Driver for Quantum Programmer Success!

peteski7
 

Isn't "bitlocker" a virus or ransomware?!

Peteski
---In QSIndustries@..., <kelly.dorf@...> wrote :

Good for you Bruce.   I am still fighting a new windows 10 laptop.  After going thru the unsigned driver drill, I hit a new roadblock called "bitlocker". I finally got past that, installed everything, and I am getting the warning incompatable driver ver 0.0.0.0.    
OMG why does Microsoft make things so much harder?
I will keep banging away at it.

Kelly

Re: Driver for Quantum Programmer Success!

kelly dorf
 

Good for you Bruce.   I am still fighting a new windows 10 laptop.  After going thru the unsigned driver drill, I hit a new roadblock called "bitlocker". I finally got past that, installed everything, and I am getting the warning incompatable driver ver 0.0.0.0.    
OMG why does Microsoft make things so much harder?
I will keep banging away at it.

Kelly

Re: Driver for Quantum Programmer Success!

Bruce Shanks
 

I've managed to get Quantum CV Manager running with Driver 3.2

First I took a few steps from the instructions for installing the driver in Windows XP Vista or Win 7 which are in the Quantum Programmer Installation Guide. I unplugged the programmer and made a file named SiLabs in C:Programs. Into that folder I downloaded the qprog_winxp_3_2 compressed file using administrator privileges to allow it.

Then I switched to the instructions for installing the driver in Win 10, which several folks had referenced. I stepped thru the instructions to force Win 10 to accept an unsigned driver. After clicking Startup Setting 7 to disable driver signature enforcement and waited for the re-start, I went to the downloaded compressed file in the SiLabs folder and clicked on it. When the "Extract" page came up I browsed for the C:Programs&#92;Silabs folder as the target for extracted files. I then clicked on the install application in those files. Things progressed normally from there, I was warned about unsigned drivers and then had to allow the installation. Finally I got the message that the driver was installed. Plugged in the Programmer and nothing happened.

Turned out I was half-way there! I downloaded and installed CV Manager, clicked on it and it gave me the warning that it wouldn't work right with driver 3.1, just like before. I tried the installer again, but it told me that driver 3.2 was installed and working properly. At this point I opened Control Panel and started Device Manager. Down at the bottom of the list appeared a USBExpress device that I don't think was there before. Clicking on it revealed it was a device with driver version 3.1 which had an "update driver" click box. Selecting the update and allowing the machine to find the driver worked.

Now CV Manager and Quantum Upgrade open happily.

Sincere thanks to all who have been supportive in my quest. I hope this epistle will help others who are having trouble getting the Quantum Programmer driver installed in Win 10.

Bruce Shanks

Re: Driver for Quantum Programmer

Tom K.
 

Bruce, did you see the eleven point procedure at the bottom of my message?

Re: Engine runs away when first powering up

Nicholas Geti
 

That's great. Thanks a lot.

Nicholas

Re: Driver for Quantum Programmer

Bruce Shanks
 

In digest 3842 Kelly pointed out the need to set up Win 10 to accept unsigned drivers, and where the instructions are in the QP Install guide. Followed them twice now, and every thing seems to be working fine until it scans, begins "copying driver files" then halts with the notice

The specified INF files could not be copied and installed.
Please check your installation and try again.

I get the messages in digest, and can't figure out how to select message 16373 on the group site, but from what I read in these recent messages, apparently I'm dealing with a different issue.

Fervently hoping someone understands why I'm getting this message about INF files.

Bruce Shanks

QSI Titans and Programmer for sale

Steven Lansing
 

I have 2 NIB QSI Solutions Titan-A boards a used Atlas OEM Titan and a lightly used like new condition QSI programmer for sale.

$350 shipped. If interested contact me off list at nneverused@...


Re: Engine runs away when first powering up

Kevin Strong
 

Turn off the "Run on analog DC" bit on CV29 on the QSI decoder. If the Airwire Convertr does not see a valid signal coming from the transmitter, it will pass along full battery voltage through the Convertr to the DCC decoder. If the QSI--or any--decoder is prorgammed to operate on analog DC, it will see this and take off running. Once you turn on the transmitter, the receiver sees the DCC instructions and instead passes the DCC signal to the decoder.


Yeah, took me a while to figure that one out, too...


Later,


K


On April 17, 2019 at 12:14 PM "ngeti@... [QSIndustries]" <QSIndustries@...> wrote:

 

 

I have converted a locomotive to battery power with Airwire radio control. I have added a switch to the setup so that I can disconnect power from the battery to the Titan-U decoder. When I flip the switch and power up the decoder, the engine starts moving and rapidly picks up speed. To avoid this I have to first power up my control hand set and set it to the locomotive number then power up the locomotive.

Shouldn't the Titan decoder hold the last settings that were live at the time it is powered off? Is there a way to avoid losing these settings when shutting down?

Nicholas

 


 


 

Engine runs away when first powering up

Nicholas Geti
 

I have converted a locomotive to battery power with Airwire radio control. I have added a switch to the setup so that I can disconnect power from the battery to the Titan-U decoder. When I flip the switch and power up the decoder, the engine starts moving and rapidly picks up speed. To avoid this I have to first power up my control hand set and set it to the locomotive number then power up the locomotive.

Shouldn't the Titan decoder hold the last settings that were live at the time it is powered off? Is there a way to avoid losing these settings when shutting down?

Nicholas

Re: Driver for Quantum Programmer

Tom K.
 

    I've had success re-installing the drivers using this procedure.  Above on the 'New Messages' link click "See All".  You can now search for message #16373 above to the right. Josh goes into a lot of detail as to why we have a problem with windows 10 and drivers.
   In case you can't find the message, here is the brunt of it:  -  Best of luck.....
Here’s the procedure:
  1. Disconnect the programmer
  2. Click the Start Menu
  3. Click the Power icon
  4. Hold the shift key and click “restart”. (this can take a minute so don’t panic)
  5. When asked to “Choose and option” click “Troubleshoot”
  6. Click “Advanced Options”
  7. Click “Startup Settings”
  8. Click “Restart” (The computer will partially reboot and you’ll be presented with an options list)
  9. Press the 7 key to select “Disable Driver Signature Enforcement” (The computer will now finish booting and look normal)
  10. Install the driver per the instructions presented in the Install Wizard.
  11. Connect the programmer.

Re: Rating on QSI Titan-U

Nicholas Geti
 

I am installing it in an O-scale tender rather than with the motor in the engine. I have other O-scale engines made by Sunset which are using the Titan-U so I should be safe there. I also have several DC engines which I haven't tested yet for current rating.

I am converting all of my engines to battery power with Airwire radio control which is why I am asking about maximum current loads.

Nicholas

Re: Rating on QSI Titan-U

kjlovesya
 

Hi Nicholas,

  I'm assuming you are installing the decoder in an HO scale locomotive.

  According to QSI's Kelly Dorf, the Titan's motor drive circuitry is a very efficient H-bridge chip.  Which means very little heat buildup, even at 1.5 Amperes.

  Electrical engineer, Mark Gurries recommends keeping the decoder away from the motor, if at all possible.  The motor is going to be the hottest component in the chain.


KJ