Date   

Re: ATTN: QSI Staff - Update

g_pruss
 

KJ,

>>> 1/ ... Shouldn't the "About" pop up, on the first page, allow you to see or hear the type of decoder you have, so that you may
select the correct decoder? <<<

What if you already know the firmware model in your decoder? Do you want to wait 10 seconds or more every time your create
a new document for QCVM to retrieve the firmware information (in Service Mode) from the decoder?


>>> 2/ ... Where do I find CV55.1.1 and CV55.1.2 in CV Manager? <<<

(1) Click on "Edit | FindCV...".
(2) In the Find CV dialog, type in the keyword "cv55.1.1" or type "horn type".
(3) Select "CV55.1.1 Horn Type" from the list.
(4) Click "Goto".


>>> 4/  When the sound file is loaded at the 'factory' why not allocate the left 
over space as the 'reserved block' for  user sound files <<<

This might work. It would probably make sense to extend this to placing all the Cut&Paste sounds at the end of
memory. This would allow someone to change the native horn, for example, in addition to User Sounds with a shorter upgrade time.
Let me think about this some more.

Gerry Pruss
QSI


Re: Keep ALive Circuits

kjlovesya
 

Hi Rich,

  From the Files (above) folder - see the file named QSI Titan A Complete Diagram PDF.   In it is a drawing of the Titan A that we can use for reference.

  The TCS Keep Alive is designed for the 12 Volt DC with the Blue wire going to the + (positive) 12 V and the Black w/white striped wire going to the - (negative) post full-wave rectifier.

  On the diagram, the Titan A has the forward direction (Front headlight) on the right.   The +12V is top center, shown with a red wire connected to a smoke unit.   That's where the blue wire will go.

  To the extreme left of the diagram you can see the Yellow Reverse Headlight connection tabs, labelled, "Light 2".  Inboard of them you can see where the "Flywheel Capacitor" is connected.   You want to connect the Keep Alive's Black w/white striped wire to the - (negative) point of the Flywheel capacitor.


KJ


Keep ALive Circuits

Rich Randall
 

I am asking for the right places to connect a TCS Keep Alive circuit to my Titan A decoder.

I just finished an install and the engine drops out from time to time.

Thanks,

Rich

Gettysburg, PA



Re: ATTN: QSI Staff - Update

kjlovesya
 

Hi Gerry,

  Thank you for your reply.

1/  I didn't get to the page, where I had a choice of OPs Mode or Service Mode.  It was at the first page where you choose "New" and select your Quantum Decoder.   Shouldn't the "About" pop up, on the first page, allow you to see or hear the type of decoder you have, so that you may select the correct decoder?

2/  CV 55.1.1 or CV 55.1.2 either one for respective Horn selection.  I tried these with my NCE Powercab using POM however, that may have been using the version 9-2-5.    Using ver 9-3-2 and CV Manager,  I could not alter either the 'main' horn or the alternate horn.   No matter what 'notes' were selected (I didn't alter individual notes - I only tried different horns  e.g. Nathan P3 or a Leslie ... whatever) .   However, I did not notice a CV 55.1.1 in CV Manager.   I'll have to go look again.   Perhaps it is user error.  Where do I find CV55.1.1 and CV55.1.2 in CV Manager?

3/  I didn't manipulate CV55.1.1 in CV Manager so I'll have to get back to you on that.



4/  When the sound file is loaded at the 'factory' why not allocate the left over space as the 'reserved block' for  user sound files (that can be added by CV Manager.)   that way, no matter what options are chosen by the dealer (or 'factory') there is at least some room for a simple sound file or six.   *GRIN*

  If the owner chooses to rewrite the firmware, using Quantum Upgrade, he may do so with the variable parameters you mention above - the remaining memory can automatically be allocated to "user sound file slot".


KJ


Re: ATTN: QSI Staff - Update

g_pruss
 

KJ,

>>> 1/  "About Decoder" button brings up a pop-up screen in which only the "Close" button does anything. <<<

I just tried this using QCVM 3.1.0.7 and 1161-567v9_3_2 firmware. The About Decoder Firmware dialog worked correctly, both in Ops Mode and Service Mode.
Are you running in Ops Mode or Service Mode?


>>> 2/ Sound Tab -> WDH Pitch Tab - neither CV 130 or 131 render anything except rapid clicks - no horns.  (the clicks vary
 in cadence, depending on how many horn bells are selected) <<<

Do you have CV55.1.1 Horn Type set to 2 "User-defined Horn"?

What Semitone notes are you selecting?


>>> 3/ Features Tab --> Horn Tab -  pull down menu selection now has various horns.  However, selecting any one of them 
 changes nothing.   The Native Horn is all that plays. <<<

I just tried this using 1161-567v9_3_2 firmware.  If Auto Program is On, changing CV55.1.1 Horn Type causes the
selected horn to play a single hoot as positive feedback. Subsequent presses of the Horn button play the selected horn.


>>> 4/  Once you fix the above I would like to add a suggestion.    Can you make User Sound Files programmable using 
 CV Manager?    It's over an hour of Quantum Update programming just to add two or three minutes of user files.   
 Is that really necessary?   Perhaps more people would use the files I posted (in Files - above) if they were easier
 to load. <<<

This would require reserving a fixed blocks of flash memory for User Sound Files at a known location in memory. The current
implementation uses dynamically allocated blocks of memory allocated at QuantumUpgrade Cut&Paste time. The Cut&Paste operation shows
you how much memory is available so you know whether your User Sound Files will fit or not. This gives you the opportunity
to be a software engineer for a time, requiring you to decide which sounds are most important when you can't fit them
all into the available memory.

Some questions to be resolved:
  (1) How much memory should be reserved for User Sound Files?
      Reserving a fixed amount of memory for User Sound Files means a limitation on the size of User Sound Files.
      For example, 64k is reserved for User Sound Files, but a customer wants to use a 100 kbyte file.
  (2) Does reserving memory for User Sound Files prevent addition or improvement of new featuers, such as Horn Master
      or the Q3 Diesel Motor sounds?
  (3) Does reserving memory for User Sound Files mean other Cut&Paste operations cannot be carried out because not
      enough memory remains for dynamic allocation?
       

>>>  Varying Brake and Flange squeals are heard on the real thing.  Why not our models? <<<

I will pass this request on to our sound engineers.


Gerry Pruss
QSI


Re: ATTN: QSI staff - Software/Firmware glitch inside

g_pruss
 

KJ,

>>> Can one enable Horn Master without enabling all CVs? <<<

Enabling the Horn Master CV's in QCVM does enable the CV's in the decoder and does not mean that the decoder's firmware supports these CV's.
The Horn Master CV's are automatically enabled in the decoder's firmware if and only if the firmware supports the Horn Master CV's.

>> I am familiar with feature 145 (even if I didn't use the correct nomenclature).   My point, now rectified was that the ver9-2-5 firmware in this particular model did not
allow  Disconnect or Standby.  Double pressing F9 went straight to Shutdown. <<<

Your firmware had CV53.11.1 set to 143 "Shutdown" instead of 145 "Disconnect/Standby/Shutdown".

Gerry Pruss
QSI


Re: ATTN: QSI staff - Software/Firmware glitch inside

kjlovesya
 

Thanks Gerry!    Now can we answer the "ATTN: QSI - Update" post?


KJ


Re: ATTN: QSI staff - Software/Firmware glitch inside

kjlovesya
 

Hi Gerry,

  Thanks for your replies.   I don't have CV Manager running at this moment (as explained in another email - my system is dual boot).  

  In an earlier post (by Tim - CV Manager Issues) Bob instructed us that in order to manipulate the Horn Master files, one needed to click "Options" and  "Enable ALL CVs ".   I wanted to manipulate Horn Master so I enabled all CVs.

  Can one enable Horn Master without enabling all CVs?


  Either way, the version 9-2-5 was not the current version (9-3-2) so Horn Master was a Horn Bastard.


  I am familiar with feature 145 (even if I didn't use the correct nomenclature).   My point, now rectified was that the ver9-2-5 firmware in this particular model did not allow  Disconnect or Standby.  Double pressing F9 went straight to Shutdown.   That's why I mentioned it here in the forum.

  Thanks anyway.


KJ


Re: ATTN: QSI staff - Software/Firmware glitch inside

g_pruss
 

KJ,

A query of CV7 yields just the major version number. (CV7 is a standard NMRA CV of just one byte.)

Writing "1" to CV56.255 Play Build Information causes the decoder to speak out <major version> . <minor version> . <build number>.

Gerry Pruss
QSI


Re: ATTN: QSI staff - Software/Firmware glitch inside

g_pruss
 

KJ,

The order for feature 145 is Disconnect -> Standby -> Shutdown.

If the decoder is in neutral (NFF/NFR) double pressing F9 puts the decoder in Disconnect.

If the decoder is in Standby, double pressing F9 puts the decoder in Shutdown.

Gerry Pruss
QSI


Re: ATTN: QSI staff - Software/Firmware glitch inside

g_pruss
 

KJ,

If you select "Options | Enable Only Supported CV's" you will not have these issues.

If you select "Options | Enable All CV's" all the CV's in QuantumCVManager are enabled, whether or not the decoder's
firmware supports them.

For example, if you Enable All CV's, QCVM shows CV51.3 enabled, even though the E9 firmware does not support this CV.

I try to keep QCVM updated with the latest CV defaults for the CV's supported by the most recent production firmware for each model.
The "Enable All CV's" option is provided only for those (hopefully) rare occasions where the most recent production
firmware for a particular model has a new CV or two added since the last QCVM release.

So, in general, do not Enable All CV's. If you do, beware that the firmware may not support some of these CV's.

Gerry Pruss
QSI


ATTN: QSI Staff - Update

kjlovesya
 

Hello all,

   Using the Quantum Programmer and Quantum Update software (written for the neophytes who may be reading) I loaded the following sound file:   1161-567 version 9-3-2.    The original sound file, from the dealer, was version 9-2-5.   The dealer sold old (new) stock.

  The F9 Disconnect/Low idle/Shutdown has been restored.   However, there are still problems accessing the Horn Master.   I'll list a few problems I encountered using CV Manager 3.1.0.7 (the newest version).


1/  "About Decoder" button brings up a pop-up screen in which only the "Close" button does anything.

2/ Sound Tab -> WDH Pitch Tab - neither CV 130 or 131 render anything except rapid clicks - no horns.  (the clicks vary in cadence, depending on how many horn bells are selected)

3/ Features Tab --> Horn Tab -  pull down menu selection now has various horns.  However, selecting any one of them changes nothing.   The Native Horn is all that plays.

4/  Once you fix the above I would like to add a suggestion.    Can you make User Sound Files programmable using CV Manager?    It's over an hour of Quantum Update programming just to add two or three minutes of user files.   Is that really necessary?   Perhaps more people would use the files I posted (in Files - above) if they were easier to load.   Varying Brake and Flange squeals are heard on the real thing.  Why not our models?


KJ



Re: ATTN: QSI staff - Software/Firmware glitch inside

kjlovesya
 

Hi Bob,

  No, Kelly has not replied to me anywhere except this forum.   I presume that QSI is in fact looking into this issue.

  Last evening I loaded the 1161 - 567 ver. 9-3-2 firmware into the decoder.   When I did the first step in the operation I discovered that the locomotive had not been loaded with the current file.  The readout claimed that the 'new' decoder only had ver 9 - 2 - 5.   That would likely be a part of the issue, as I don't believe that ver 9-2-5 was equipped with Horn Master files.

  My computer system is dual boot so I have to reboot in order to access the QSI software (Quantum Upgrade and CV Manager).   I have to log off an do some more experimenting.

  I just hooked up the NCE Powercab to the test track and discovered that I cannot program the Horn Master file using POM CV55.1.1 .     The horn only stays on the "Native" file I programmed last night.

  Is there some other step I've neglected (using POM) to access the Horn Master selection?

  I'm going to reboot and do some experimenting with CV Manager.


KJ


Re: ATTN: QSI staff - Software/Firmware glitch inside

Bob Waldele
 


KJ
it looks like Kelly replied "off list"  for those of us that are now somewhat confused at this point, what was his response?  is there a problem with the Titan firmware, the specific file that you loaded, or the CV Manager software?
isn't a V7 a Q1a file?
thanks.
bob.waldele
 
 

----- Original Message -----
Sent: Sunday, September 04, 2016 3:40 PM
Subject: Re: [QSIndustries] ATTN: QSI staff - Software/Firmware glitch inside

 

Thanks Kelly!    I don't know if this makes any difference but I just did a query using CV64.   CV 7 = 9   not CV 7 = 9 point 3 point 2,   just "CV 7 = 9".    Looks like some dealer needs to update his sound files.

  I guess I'll just 'roll my own'.


KJ


Re: ATTN: QSI staff - Software/Firmware glitch inside

kjlovesya
 

Thanks Kelly!    I don't know if this makes any difference but I just did a query using CV64.   CV 7 = 9   not CV 7 = 9 point 3 point 2,   just "CV 7 = 9".    Looks like some dealer needs to update his sound files.

  I guess I'll just 'roll my own'.


KJ


Re: ATTN: QSI staff - Software/Firmware glitch inside

kelly dorf
 

We will investigate this right away.

Thanks

Kelly
QSI


Re: ATTN: QSI staff - Software/Firmware glitch inside

Bob Menzies <railscanner@...>
 

Working my phone error on my part. Mine were pre-loaded steam by Josh

On Sep 3, 2016 9:32 PM, "kjlovesya@... [QSIndustries]" <QSIndustries@...> wrote:

 

Hi Bob,

  I didn't load the firmware (using Quantum Upgrade).   I am using a new, stock decoder, pre-loaded with the diesel firmware.   I did notice another thing which I'll mention in my original post.


Curiousity:  why did you not reply to my existing post (instead posting a new topic)?


KJ


Re: ATTN: QSI staff - Software/Firmware glitch inside

kjlovesya
 

Hi Bob,

  I didn't load the firmware (using Quantum Upgrade).   I am using a new, stock decoder, pre-loaded with the diesel firmware.   I did notice another thing which I'll mention in my original post.


Curiousity:  why did you not reply to my existing post (instead posting a new topic)?


KJ


Re: ATTN: QSI staff - Software/Firmware glitch inside

kjlovesya
 

Hello all,

  I've noticed another anomaly.    Double pressing F9 (in idle) does not put the decoder into "Disconnect".   Instead the decoder goes into "Shut Down".   Comments?

Gerry?  Josh?  Kelly?  Anyone?


KJ


Re: ATTN: QSI staff - Software/Firmware glitch inside

Bob Menzies <railscanner@...>
 

Have the same issue KJ... it allows you to cut and paste when doing initial programming but you get the steam menu instead of the diesel menu. I bought some used Titans and they were probably programmed for steam . I wonder if this is a problem in the download process./Bob Menzies.

2801 - 2820 of 19606