开云体育

Hello, I don’t know if this has been reported before but as its repeated from 4.7.1 into the latest version I thought I would mention it.



This observation affects the `new loco’ routine and ZIMO decoders. I have just taken a brand new ZIMO MX 645R out of its packet and plugged it into a decoder test socket. I clicked the `new loco’ button and observed the CV’s being read. The routine then pretty much highlighted all ZIMO decoders except the MX645 family.

I hadn’t thought about it until writing it just but it’s pretty much reverse logic highlighting the ones it’s not.

Apologies if it’s an already known issue. It wasn’t a lot of consequence as I knew which decoder I had and selected it from the list but if it’s an easy fix then it’s worth changing.

Paul Martin

(an occasional DP user, don’t always know what it’s doing but I’d be lost without it)

Paul,



Please post what id values are in the decoder. So CV 7 and 8 as starters to
help see which entries should match or not. There may be other CV's that are
also used for ZIMO decoders, but I'm not sure. If you know of other values
that should help id which is which, please post those too. So you will have
to read the decoder to see what it is reporting.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

It would also be helpful to get the value of CV250. That’s used as part of identifying Zimo decoders.

Bob

On Jul 18, 2017, at 9:13 AM, 'Ken Cameron' kcameron@... [jmriusers] <jmriusers@...> wrote:

Please post what id values are in the decoder. So CV 7 and 8 as starters to
help see which entries should match or not. There may be other CV's that are
also used for ZIMO decoders, but I'm not sure. If you know of other values
that should help id which is which, please post those too. So you will have
to read the decoder to see what it is reporting.

--
Bob Jacobsen
rgj1927@...

Ken
CV 7 = 37
CV8 = 145
CV250 = 221

Just looked at the decoder manual and the CV7 value is the firmware version number and not the decoder type. The firmware is common to all the ZIMO decoders.


Paul

Hi guys
JMRI working fine here with MX645:
Using JMRI 4.7.8 with my ECoS (FW4.2.0), I just "added" a new Lok with a Zimo MX645P (Roco Swiss Re4/4 TEE Sound). I then read Decoder Type, which was identified OK as :


Zimo Unified Software (version32+) and then proposing one of the 4 MX645 available (MX645, MX645R, MX645F or MX645P22).


Reading a few CVs by themselves:
CV7=35
CV8=145
CV250=221


Alain

Hi Paul
I think I found the error you have, your decoder is in FW version 37 (CV7), not yet identified within JMRI (the highest version ID being 35).


Alain

Alain I was thinking that having seen your CV list. I was going to load v35 software in to a decoder to see if the problem went away but domestic chores got in the way.


Paul

It's more a matter of either managing or waiting:


Managing - it will probably be fine if you pick a lower firmware version for the decoder. Zimo usually just add features, or enhance a detail of running. They very very rarely take a feature away. So using a lower version in JMRI is almost guaranteed safe.

Managing(2). Update the decoder definitions with your new knowledge.

Waiting. In time, those who update the Zimo files will get round to updating things. Zimo firmware comes out frequently, but often without announcement. Later the manuals get updated with some details.



- Nigel (contributor to the Zimo files, but not the lead author of them )

Nigel

I am both managing and waiting.


I am afraid I am a grateful user and have no wish or the time to learn how to do things with definitions, I just mentioned something i had observed in case everyone else was thinking the mythical someone would have said or be doing something about it


Paul

Paul,



Since you have the new one maybe you can spot any differences in what it can
do vs the slightly older one that does have a decoder definition?? Clues
like that will help the folk who will take that existing one and add changes
so it will match the decoder you have. Finding the new docs isn't always
easy or automatic.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Paul,



PS: Most of the time a new user finds the new version before anyone on the
team happens across it. So it is very valuable to us to hear there is
something new and that research is needed to figure out what is the 'new
features'.



Only a couple of vendors directly let us know what is coming out. I only
know of two or three where the vendor creates the files for us, the rest are
done by the JMRI supporters after they hear about the new devices and
features.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Hello guys
Some updates: as a friend just received a new Roco lok with Zimo MX645P22 in SW release V37, I pushed to Github as issue #3846 a zip file including 5 updated Zimo_Unified_software_v36_*.xml decoder définitions (for MX644, MX645, MX646, MX648 and MX658).


It was tested OK yesterday by him with JMRI on his Lenc DCC, and his new lok (detected OK).


As there's no manual nor release note saying which improvements were made between v35 (latest manual) and the latest versions, those V36+ profiles are just accepting SW releases from 36 to 40, otherwise being similar to the previous latest version.


Thus it should be available soon in a future test release.


Regards from Paris

Alain