You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by mmosher5501 on 2007-06-19 14:03 UTC
When "Read type from decoder" with a QSI v7 decoder, if the model name of the read product ID is exactly the same as the same ID in the V6 file, DP select the V6 model instead of the V7 model. I watched Loconet monitor, CV values on Loconet are correct.
If the model name is different between V6 & V7 of a given product ID then DP selects the correct model.
JMRI 1.7.7
Java 1.4.2-08
Windows 98SE
DSC200
Locobuffer
PowerPax
What I suspect is happening:
read manufacturer ID - OK
read version ID - likely OK (gets to V7 file?)
read QSI productID - OK
associate product ID to model name - likely OK error likely here
load definition based on model name ignoring version ID, using first model name match found (ie V6 instead of correct V7).
Note likely a problem with the QSI product ID mechanism, as NCE 3.0-3.4 and NCE 3.5 decoder families have model names in common and do not exhibit this problem.
The text was updated successfully, but these errors were encountered:
Reported by mmosher5501 on 2007-06-19 14:03 UTC
When "Read type from decoder" with a QSI v7 decoder, if the model name of the read product ID is exactly the same as the same ID in the V6 file, DP select the V6 model instead of the V7 model. I watched Loconet monitor, CV values on Loconet are correct.
If the model name is different between V6 & V7 of a given product ID then DP selects the correct model.
JMRI 1.7.7
Java 1.4.2-08
Windows 98SE
DSC200
Locobuffer
PowerPax
What I suspect is happening:
read manufacturer ID - OK
read version ID - likely OK (gets to V7 file?)
read QSI productID - OK
associate product ID to model name - likely OK
error likely here
load definition based on model name ignoring version ID, using first model name match found (ie V6 instead of correct V7).
Note likely a problem with the QSI product ID mechanism, as NCE 3.0-3.4 and NCE 3.5 decoder families have model names in common and do not exhibit this problem.
The text was updated successfully, but these errors were encountered: