开云体育

  1. Jmriusers
  2. Topics

Zimo MS450P22 CVs above #841 #zimo #definitions

 

I have just taken delivery of a loco fitted with the above decoder and carried out a CV “read all sheets” with DecoderPro. It appears to not display CV numbers greater than 841. How do I read/write these? I am familiar with ESU’s Indexing process to access a large number of CVs, but can only find a process called scripted CVs in the Zimo instruction manual. Maybe I am dumb, but definitely need help here. Thanks in advance.
 

开云体育


They're not in the decoder file.? I wrote the original version.? When I wrote it, I couldn't find any explanation of what they did, or why they were useful? (all I can deduce is some connection between scripted activity created in the sound project and the CVs, but nothing that actually tells me anything about them).? ?
That may have changed with newer manuals, in which case an update is required.? ? ?Do you know what those CV's do, and why they might be needed ?

All the usual CVs for moving things around inside a Zimo decoder don't need indexing, unlike ESU.??


- Nigel



------ Original Message ------
From "david.hull12 via groups.io" <david.hull12@...>
Date 12/03/2025 14:37:52
Subject [jmriusers] Zimo MS450P22 CVs above #841

I have just taken delivery of a loco fitted with the above decoder and carried out a CV “read all sheets” with DecoderPro. It appears to not display CV numbers greater than 841. How do I read/write these? I am familiar with ESU’s Indexing process to access a large number of CVs, but can only find a process called scripted CVs in the Zimo instruction manual. Maybe I am dumb, but definitely need help here. Thanks in advance.
 

开云体育

To me it looks like these scripts are how you tell a Zimo decoder to do more complex things (like an uncoupling sequence perhaps?)

Then the aforementioned CVs allow some variables to be passed into the scripts to modify the script behaviour (guessing, things like how far to shuffle on an uncouple request??)

But this is guesswork on my part

Phil G

On 12 Mar 2025, at 17:27, Nigel Cliffe via groups.io <nigel.cliffe@...> wrote:

?

They're not in the decoder file.? I wrote the original version.? When I wrote it, I couldn't find any explanation of what they did, or why they were useful? (all I can deduce is some connection between scripted activity created in the sound project and the CVs, but nothing that actually tells me anything about them).? ?
That may have changed with newer manuals, in which case an update is required.? ? ?Do you know what those CV's do, and why they might be needed ?

All the usual CVs for moving things around inside a Zimo decoder don't need indexing, unlike ESU.??


- Nigel



------ Original Message ------
From "david.hull12 via groups.io" <david.hull12@...>
Date 12/03/2025 14:37:52
Subject [jmriusers] Zimo MS450P22 CVs above #841

I have just taken delivery of a loco fitted with the above decoder and carried out a CV “read all sheets” with DecoderPro. It appears to not display CV numbers greater than 841. How do I read/write these? I am familiar with ESU’s Indexing process to access a large number of CVs, but can only find a process called scripted CVs in the Zimo instruction manual. Maybe I am dumb, but definitely need help here. Thanks in advance.
 

Nigel, thanks for your help. The reason for the query is because they are referred to in the manual for the new Dapol/Rails Class 88 sound fitted loco. The function of each is as follows:
CV981/2/3 variation of flange squeal between light and loaded engine.
CV984 Cab door closing volume
CV988 Traction motors volume?
CV990 Variable delay between pantograph contacting OLE and startup of motors.
I haven’t contacted Dapol regarding how to access these scripted CVs in order to change them. Maybe a call to them will help? Any help you could provide will be most appreciated.
 

开云体育

Think this helps a lot

The CVs should be accessible but as Nigel says, JMRI has no idea what they’re for or what values are expected

It seems that the CVs are not only decoder-specific, but sound project-specific too

Phil G

On 12 Mar 2025, at 19:44, david.hull12 via groups.io <david.hull12@...> wrote:

?
Nigel, thanks for your help. The reason for the query is because they are referred to in the manual for the new Dapol/Rails Class 88 sound fitted loco. The function of each is as follows:
CV981/2/3 variation of flange squeal between light and loaded engine.
CV984 Cab door closing volume
CV988 Traction motors volume?
CV990 Variable delay between pantograph contacting OLE and startup of motors.
I haven’t contacted Dapol regarding how to access these scripted CVs in order to change them. Maybe a call to them will help? Any help you could provide will be most appreciated.
 

开云体育

David, My understanding is that Zimo does not use indexed CVs even though the CV# may be in the NMRA indexed range. But it doesn’t matter in this case since CVs above 841 are not indexed anyway. If the DecoderPro xml file for this decoder does not include those CVs, you should still be able to read/write those using DecoderPro’s single CV programmer.

?

Mark Granville
 

开云体育


David,?
Looks like we need to put another element into the Zimo file, but it will be a fairly generic table as what each sound project does is likely unique to that project.? ?

It would be a list of the CVs (if we can establish the full range possible), listed by CV number, with a comment above the pane indicating that users need to consult the documentation for what they do in their specific sound project.? ??

That's not going to take long to write, once I can find the full range of permitted CV's? ?-? clearly CV981 to CV990 are in range, but may be more.? ?



In terms of changing them inside JMRI for now, use the single CV programmer.? There's nothing special about accessing them.??


- Nigel



------ Original Message ------
From "david.hull12 via groups.io" <david.hull12@...>
Date 12/03/2025 19:44:05
Subject Re: [jmriusers] Zimo MS450P22 CVs above #841 #zimo #definitions

Nigel, thanks for your help. The reason for the query is because they are referred to in the manual for the new Dapol/Rails Class 88 sound fitted loco. The function of each is as follows:
CV981/2/3 variation of flange squeal between light and loaded engine.
CV984 Cab door closing volume
CV988 Traction motors volume?
CV990 Variable delay between pantograph contacting OLE and startup of motors.
I haven’t contacted Dapol regarding how to access these scripted CVs in order to change them. Maybe a call to them will help? Any help you could provide will be most appreciated.
 

开云体育


I think I've found the CV range from the ZSP Scripting documentation - CV's 980 to 1019,? so that's 30 CVs.? ?
I'll look at writing the files and a JMRI change request in the next few days.? ??


- Nigel



------ Original Message ------
From "Nigel Cliffe via groups.io" <nigel.cliffe@...>
Date 12/03/2025 21:58:06
Subject Re: [jmriusers] Zimo MS450P22 CVs above #841 #zimo #definitions


David,?
Looks like we need to put another element into the Zimo file, but it will be a fairly generic table as what each sound project does is likely unique to that project.? ?

It would be a list of the CVs (if we can establish the full range possible), listed by CV number, with a comment above the pane indicating that users need to consult the documentation for what they do in their specific sound project.? ??

That's not going to take long to write, once I can find the full range of permitted CV's? ?-? clearly CV981 to CV990 are in range, but may be more.? ?



In terms of changing them inside JMRI for now, use the single CV programmer.? There's nothing special about accessing them.??


- Nigel



------ Original Message ------
From "david.hull12 via groups.io" <david.hull12@...>
Date 12/03/2025 19:44:05
Subject Re: [jmriusers] Zimo MS450P22 CVs above #841 #zimo #definitions

Nigel, thanks for your help. The reason for the query is because they are referred to in the manual for the new Dapol/Rails Class 88 sound fitted loco. The function of each is as follows:
CV981/2/3 variation of flange squeal between light and loaded engine.
CV984 Cab door closing volume
CV988 Traction motors volume?
CV990 Variable delay between pantograph contacting OLE and startup of motors.
I haven’t contacted Dapol regarding how to access these scripted CVs in order to change them. Maybe a call to them will help? Any help you could provide will be most appreciated.
 

Thanks to all who helped, the use of Single CV Programmer worked perfectly for my needs: to be honest, I hadn’t used it for years and had completely forgotten of its existence. Will be testing the draft files sent by Nigel which should make the full Zimo MS CV range accessible through the normal process.
 

Nigel,
?
Just a little tip (but you probably already know that): The two CVs 837 and 841 for deactivating scripts are also part of this CV overview.
 

开云体育


Thanks for the reminder.? Yes I know they're relevant (CV837 and CV843? not 841! ),? and they need to be part of the same "pane" in the JMRI programmer interface.? ?

I'll update those in the file for CV700-899 when submitting the change request.??


For now my first files covering the script variables only are out with David who posted the question.? I'm confident they'll work because its just access to a decimal CV.? But I prefer testing a feature with an actual decoder.? ??



regards

Nigel



------ Original Message ------
From "uligg100 via groups.io" <uligg100@...>
Date 14/03/2025 09:09:42
Subject Re: [jmriusers] Zimo MS450P22 CVs above #841 #zimo #definitions

Nigel,
?
Just a little tip (but you probably already know that): The two CVs 837 and 841 for deactivating scripts are also part of this CV overview.
 

Yes, of course CV837 and CV843.
 

Can you also add the new MS decoder MS591N18 CV250=15 ?
?
The type of decoder can be read out from the value of CV #250 if required:
?1 = MS500 2 = MS480 3 = MS490 4 = MS440 5 = MS580
?6 = MS450 7 = MS990 8 = MS590 9 = MS950 10 = MS560
11 = MS001* 12 = MS491 13 = MS581 14 = MS540 15 = MS591
16 = MS481 *?
119 = MN140 120 = MN250 121 = MN150 122 = MN160 123 = MN340
124 = MN170 125 = MN300 126 = MN330 127 = MN180
 

开云体育


OK,? now added to my local file.? ? I've also removed the comments around the MS540E24 decoder, as I think its likely available.??

They'll be in the update when it goes to the JMRI approvals processes.??



- Nigel



------ Original Message ------
From "uligg100 via groups.io" <uligg100@...>
Date 14/03/2025 13:03:58
Subject Re: [jmriusers] Zimo MS450P22 CVs above #841 #zimo #definitions

Can you also add the new MS decoder MS591N18 CV250=15 ?
?
The type of decoder can be read out from the value of CV #250 if required:
?1 = MS500 2 = MS480 3 = MS490 4 = MS440 5 = MS580
?6 = MS450 7 = MS990 8 = MS590 9 = MS950 10 = MS560
11 = MS001* 12 = MS491 13 = MS581 14 = MS540 15 = MS591
16 = MS481 *?
119 = MN140 120 = MN250 121 = MN150 122 = MN160 123 = MN340
124 = MN170 125 = MN300 126 = MN330 127 = MN180
 

开云体育


Now in JMRI GitHub as issue #13945



And from there, should find its way through approvals to a JMRI test release.??


- Nigel



------ Original Message ------
From "Nigel Cliffe via groups.io" <nigel.cliffe@...>
Date 14/03/2025 14:50:26
Subject Re: [jmriusers] Zimo MS450P22 CVs above #841 #zimo #definitions


OK,? now added to my local file.? ? I've also removed the comments around the MS540E24 decoder, as I think its likely available.??

They'll be in the update when it goes to the JMRI approvals processes.??



- Nigel



------ Original Message ------
From "uligg100 via groups.io" <uligg100@...>
Date 14/03/2025 13:03:58
Subject Re: [jmriusers] Zimo MS450P22 CVs above #841 #zimo #definitions

Can you also add the new MS decoder MS591N18 CV250=15 ?
?
The type of decoder can be read out from the value of CV #250 if required:
?1 = MS500 2 = MS480 3 = MS490 4 = MS440 5 = MS580
?6 = MS450 7 = MS990 8 = MS590 9 = MS950 10 = MS560
11 = MS001* 12 = MS491 13 = MS581 14 = MS540 15 = MS591
16 = MS481 *?
119 = MN140 120 = MN250 121 = MN150 122 = MN160 123 = MN340
124 = MN170 125 = MN300 126 = MN330 127 = MN180

1 - 15 of 15