I created a new issue to officially request an increase in function support in JMRI

See more details

Phil G

Sent from my iPad

And please accept my apologies for turning simple questions into complicated answers - that's probably my IT history coming into? play. I find it really hard to give partial answers to questions :(

Please take SMALL steps and perhaps "play" with some simple decoders to start with

Phil G

On 15/04/2023 20:55, Duncan via groups.io wrote:

That’s one heck of a lot to digest, let alone for the ?programmers in the early days to design. ?It is amazing that there is the NMRA to bring everything together under one umbrella.?

You are correct, it all goes above my head currently. ?I will take a look at DecoderPro again with what you have mentioned in my mind. ?Thank you for taking the time to explain, again this group never ceases to raise to the challenge of the questioner (if that is such a word)!

Thanks again for your help and making dcc and it’s elements clearer and easier to get to grips with.?

Duncan

On Saturday, April 15, 2023, 8:23 pm, Phil G <phil@...> wrote:

Now there's a $64,000 (or ?64,000) question!

EVERY decoder has a set of cvs (configuration variables) that it uses to define how the decoder will behave

Decoders can have as few as a dozen or so cvs, or as many as a couple of thousand! The more complex the decoder (whether it has sound or other actions) the more cvs are needed to define them

Luckily most cvs are defined by the NMRA and always mean the same thing. For example, cv1 is ALWAYS the short address of a decoder. This common list is defined here ->

BUT this does not tell you which decoder supports or needs which cvs - that information is (or should be) provided by the decoder manufacturer

Luckily (for most of us) the awesome people behind JMRI have digested as much documentation as they can find and have built DecoderPro. Using this tool, you can largely forget about cvs, and who requires which ones. The different panes in DecoderPro provide you easily understandable translations of the different aspects of decoder configuration and behind the scenes translate that into the cvs needed and what values to set into each one

Next time you are in DecoderPro, take a look at the different panes there are for your chosen decoder. Behind this facade it's all cvs!

SO, if you look in the NMRA list of cvs, you will see that cvs 15 and 16 control decoder lock IN THOSE DECODERS THAT SUPPORT DECODER LOCKING. Not all do

This is a LOT to digest. Many of us here are lucky in that we learnt about cvs when there were less than a dozen (and probably less than a dozen decoders too!!)

Phil G

On 15/04/2023 20:02, Duncan via groups.io wrote:

Hi Nigel,

Now your loosing me, how do you know what cv’s do what, and why please?

Thanks

Duncan

On Saturday, April 15, 2023, 7:44 pm, Nigel Cliffe <nigel.cliffe@...> wrote:

Decoder Locking (CV15+CV16) is one way to deal with several decoders in the same train with the same address and not wanting all to change together to programming-on-the-main.?

Decoder Locks are usually set and released manually (single CV programming, rather than decoder files).??

If using Advanced Consists, then will need to look at CV's 21 and 22 to indicate which functions are controlled by Consist Address and which by Loco Address.? ?

- Nigel

------ Original Message ------

From "Duncan via groups.io" <dunradar09@...>

To "[email protected]" <[email protected]>

Date 15/04/2023 19:11:02

Subject Re: [jmriusers] Which decoder information Bachmann 39-737ADC BR Mk2F DBSO coach

Will do Phil G, thanks

I may look at consisting as well?just incase, I see what you mean.?

Regards

Duncan?

On Saturday, April 15, 2023, 6:50 pm, Phil G <phil@...> wrote:

What I usually do (where I have a decoder at each “end” of a train) is to give them the SAME address. This usually does the trick

You might need to change the “normal direction” to “reverse” on the Basic pane for the one at the “back”. It depends on how it’s directional lights are configured?

Bear in mind though - if you have two decoders with the same address on the layout at the same time, be VERY careful with any programming “on the main”

Phil G

On 15 Apr 2023, at 18:04, Duncan via groups.io <dunradar09@...> wrote:

? Good afternoon JMRI Team,

I am successfully reporting that I have control of the above?Bachmann DBSO lighting under Roster. ?Firstly I?put the coach on the program track. ?I?have been able to re-label the function keys with the actual names of the?areas the lights illuminate, including directional lights.

? Initially the cab light wouldn’t stay on, I wasn’t happy as you would appreciate. ?So I had a look at the advanced area and looked at the cv list. ?These didn’t match the cv list and the corresponding values they had in comparison to those that Shaun from Bachmann supplied. ?I then pressed the Read All Sheets from the bottom few rows of buttons, after the information was received and I could see values changing. ?

My last task/objective, is it possible to have this DBSO and the loco it runs with to ‘linked in a consist’ within JMRI so that if I change direction of the loco then the directional?lights of the loco and the DBSO will both change at the same time, instaa we as of me having to goto the separate?DBSO ID?in the roster and change the direction?

Thanks for your help in this subject - brilliant!

Duncan?

On Friday, April 14, 2023, 9:34 pm, Duncan via groups.io <dunradar09@...> wrote:

Cheers Phil,

I’m enjoying digital and seeing its advantages. ?The moths are not so happy as they have been exposed to daylight quite a few times of late.?

I am on Facebook and like computer tech even thought I’m no good on code etc.?

Kind regards?

Duncan

On Friday, April 14, 2023, 9:04 pm, Phil G <phil@...> wrote:

Welcome to the World of Digital Duncan - pretty sure you won't regret it

As you've discovered, there's plenty of help here with JMRI-related issues. If you are on FaceBook, I also suggest you consider joining the NCE Corporation FaceBookgroup () as they can help with any NCE issues/questions you may have

Don't worry too much about being a "newbie" - sometimes the only difference between a newbie and an "expert" is how many pages further ahead in the manual the expert is :)

Phil G

On 14/04/2023 20:45, Duncan via groups.io wrote:

Thanks Dave,

I’m new to DCC and this week?have?just received?an interface for my NCE PowerCab, which I got last summer. ?Since then my layout was analogue. ?Hence JMRI is a totally new thing and what it does, along with what different cv’s do. ?

Kind regards?

Duncan

On Friday, April 14, 2023, 1:44 am, Dave Heap <dgheap@...> wrote:

?All,

On 13 Apr 2023, at 11:42 pm, Duncan via groups.io <dunradar09@...> wrote:

ESU Roco 10745

???Either Roco 10745 old

???Or ?????Roco 10745 v56

ESU SwitchPilot

???Either SwitchPilot

???Or ??????SwitchPilot Servo

???Or ??????SwitchPilot Servo (MA)

???Or ??????SwitchPilot Servo (2013)

???Or ??????SwitchPilot V2.0

???Or ??????SwitchPilot Servo V2.0

For those decoders (CV 007 < 255 and CV 008 = 151) it's not possible to uniquely determine the decoder model. CV7 is only a firmware version and subject to change (LokProgrammer software/hardware allows user to update firmware).

Only those decoders that return CV7=255 and CV8=151 support indexed CV mapping and access to the RailCom Product ID CVs.

These are?CV="0.255.261"to?CV="0.255.264" and make a 4 byte?Little Endian value. The LokProgrammer software has a Supported Decoders menu item and this has a "many to one" mapping of Product IDs to Decoder Models .

Before my health failed I used LokProgrammer's "Supported Decoders t"o maintain a mapping list for JMRI definitions use:

<>

Dave in Australia

That’s one heck of a lot to digest, let alone for the ?programmers in the early days to design. ?It is amazing that there is the NMRA to bring everything together under one umbrella.?

You are correct, it all goes above my head currently. ?I will take a look at DecoderPro again with what you have mentioned in my mind. ?Thank you for taking the time to explain, again this group never ceases to raise to the challenge of the questioner (if that is such a word)!

Thanks again for your help and making dcc and it’s elements clearer and easier to get to grips with.?

Duncan

On Saturday, April 15, 2023, 8:23 pm, Phil G <phil@...> wrote:

Now there's a $64,000 (or ?64,000) question!

EVERY decoder has a set of cvs (configuration variables) that it uses to define how the decoder will behave

Decoders can have as few as a dozen or so cvs, or as many as a couple of thousand! The more complex the decoder (whether it has sound or other actions) the more cvs are needed to define them

Luckily most cvs are defined by the NMRA and always mean the same thing. For example, cv1 is ALWAYS the short address of a decoder. This common list is defined here ->

BUT this does not tell you which decoder supports or needs which cvs - that information is (or should be) provided by the decoder manufacturer

Luckily (for most of us) the awesome people behind JMRI have digested as much documentation as they can find and have built DecoderPro. Using this tool, you can largely forget about cvs, and who requires which ones. The different panes in DecoderPro provide you easily understandable translations of the different aspects of decoder configuration and behind the scenes translate that into the cvs needed and what values to set into each one

Next time you are in DecoderPro, take a look at the different panes there are for your chosen decoder. Behind this facade it's all cvs!

SO, if you look in the NMRA list of cvs, you will see that cvs 15 and 16 control decoder lock IN THOSE DECODERS THAT SUPPORT DECODER LOCKING. Not all do

This is a LOT to digest. Many of us here are lucky in that we learnt about cvs when there were less than a dozen (and probably less than a dozen decoders too!!)

Phil G

On 15/04/2023 20:02, Duncan via groups.io wrote:

Hi Nigel,

Now your loosing me, how do you know what cv’s do what, and why please?

Thanks

Duncan

On Saturday, April 15, 2023, 7:44 pm, Nigel Cliffe <nigel.cliffe@...> wrote:

Decoder Locking (CV15+CV16) is one way to deal with several decoders in the same train with the same address and not wanting all to change together to programming-on-the-main.?

Decoder Locks are usually set and released manually (single CV programming, rather than decoder files).??

If using Advanced Consists, then will need to look at CV's 21 and 22 to indicate which functions are controlled by Consist Address and which by Loco Address.? ?

- Nigel

------ Original Message ------

From "Duncan via groups.io" <dunradar09@...>

To "[email protected]" <[email protected]>

Date 15/04/2023 19:11:02

Subject Re: [jmriusers] Which decoder information Bachmann 39-737ADC BR Mk2F DBSO coach

Will do Phil G, thanks

I may look at consisting as well?just incase, I see what you mean.?

Regards

Duncan?

On Saturday, April 15, 2023, 6:50 pm, Phil G <phil@...> wrote:

What I usually do (where I have a decoder at each “end” of a train) is to give them the SAME address. This usually does the trick

You might need to change the “normal direction” to “reverse” on the Basic pane for the one at the “back”. It depends on how it’s directional lights are configured?

Bear in mind though - if you have two decoders with the same address on the layout at the same time, be VERY careful with any programming “on the main”

Phil G

On 15 Apr 2023, at 18:04, Duncan via groups.io <dunradar09@...> wrote:

? Good afternoon JMRI Team,

I am successfully reporting that I have control of the above?Bachmann DBSO lighting under Roster. ?Firstly I?put the coach on the program track. ?I?have been able to re-label the function keys with the actual names of the?areas the lights illuminate, including directional lights.

? Initially the cab light wouldn’t stay on, I wasn’t happy as you would appreciate. ?So I had a look at the advanced area and looked at the cv list. ?These didn’t match the cv list and the corresponding values they had in comparison to those that Shaun from Bachmann supplied. ?I then pressed the Read All Sheets from the bottom few rows of buttons, after the information was received and I could see values changing. ?

My last task/objective, is it possible to have this DBSO and the loco it runs with to ‘linked in a consist’ within JMRI so that if I change direction of the loco then the directional?lights of the loco and the DBSO will both change at the same time, instaa we as of me having to goto the separate?DBSO ID?in the roster and change the direction?

Thanks for your help in this subject - brilliant!

Duncan?

On Friday, April 14, 2023, 9:34 pm, Duncan via groups.io <dunradar09@...> wrote:

Cheers Phil,

I’m enjoying digital and seeing its advantages. ?The moths are not so happy as they have been exposed to daylight quite a few times of late.?

I am on Facebook and like computer tech even thought I’m no good on code etc.?

Kind regards?

Duncan

On Friday, April 14, 2023, 9:04 pm, Phil G <phil@...> wrote:

Welcome to the World of Digital Duncan - pretty sure you won't regret it

As you've discovered, there's plenty of help here with JMRI-related issues. If you are on FaceBook, I also suggest you consider joining the NCE Corporation FaceBookgroup () as they can help with any NCE issues/questions you may have

Don't worry too much about being a "newbie" - sometimes the only difference between a newbie and an "expert" is how many pages further ahead in the manual the expert is :)

Phil G

On 14/04/2023 20:45, Duncan via groups.io wrote:

Thanks Dave,

I’m new to DCC and this week?have?just received?an interface for my NCE PowerCab, which I got last summer. ?Since then my layout was analogue. ?Hence JMRI is a totally new thing and what it does, along with what different cv’s do. ?

Kind regards?

Duncan

On Friday, April 14, 2023, 1:44 am, Dave Heap <dgheap@...> wrote:

?All,

On 13 Apr 2023, at 11:42 pm, Duncan via groups.io <dunradar09@...> wrote:

ESU Roco 10745

???Either Roco 10745 old

???Or ?????Roco 10745 v56

ESU SwitchPilot

???Either SwitchPilot

???Or ??????SwitchPilot Servo

???Or ??????SwitchPilot Servo (MA)

???Or ??????SwitchPilot Servo (2013)

???Or ??????SwitchPilot V2.0

???Or ??????SwitchPilot Servo V2.0

For those decoders (CV 007 < 255 and CV 008 = 151) it's not possible to uniquely determine the decoder model. CV7 is only a firmware version and subject to change (LokProgrammer software/hardware allows user to update firmware).

Only those decoders that return CV7=255 and CV8=151 support indexed CV mapping and access to the RailCom Product ID CVs.

These are?CV="0.255.261"to?CV="0.255.264" and make a 4 byte?Little Endian value. The LokProgrammer software has a Supported Decoders menu item and this has a "many to one" mapping of Product IDs to Decoder Models .

Before my health failed I used LokProgrammer's "Supported Decoders t"o maintain a mapping list for JMRI definitions use:

<>

Dave in Australia

Now there's a $64,000 (or ?64,000) question!

EVERY decoder has a set of cvs (configuration variables) that it uses to define how the decoder will behave

Decoders can have as few as a dozen or so cvs, or as many as a couple of thousand! The more complex the decoder (whether it has sound or other actions) the more cvs are needed to define them

Luckily most cvs are defined by the NMRA and always mean the same thing. For example, cv1 is ALWAYS the short address of a decoder. This common list is defined here ->

BUT this does not tell you which decoder supports or needs which cvs - that information is (or should be) provided by the decoder manufacturer

Luckily (for most of us) the awesome people behind JMRI have digested as much documentation as they can find and have built DecoderPro. Using this tool, you can largely forget about cvs, and who requires which ones. The different panes in DecoderPro provide you easily understandable translations of the different aspects of decoder configuration and behind the scenes translate that into the cvs needed and what values to set into each one

Next time you are in DecoderPro, take a look at the different panes there are for your chosen decoder. Behind this facade it's all cvs!

SO, if you look in the NMRA list of cvs, you will see that cvs 15 and 16 control decoder lock IN THOSE DECODERS THAT SUPPORT DECODER LOCKING. Not all do

This is a LOT to digest. Many of us here are lucky in that we learnt about cvs when there were less than a dozen (and probably less than a dozen decoders too!!)

Phil G

On 15/04/2023 20:02, Duncan via groups.io wrote:

Hi Nigel,

Now your loosing me, how do you know what cv’s do what, and why please?

Thanks

Duncan

On Saturday, April 15, 2023, 7:44 pm, Nigel Cliffe <nigel.cliffe@...> wrote:

Decoder Locking (CV15+CV16) is one way to deal with several decoders in the same train with the same address and not wanting all to change together to programming-on-the-main.?

Decoder Locks are usually set and released manually (single CV programming, rather than decoder files).??

If using Advanced Consists, then will need to look at CV's 21 and 22 to indicate which functions are controlled by Consist Address and which by Loco Address.? ?

- Nigel

------ Original Message ------

From "Duncan via groups.io" <dunradar09@...>

To "[email protected]" <[email protected]>

Date 15/04/2023 19:11:02

Subject Re: [jmriusers] Which decoder information Bachmann 39-737ADC BR Mk2F DBSO coach

Will do Phil G, thanks

I may look at consisting as well?just incase, I see what you mean.?

Regards

Duncan?

On Saturday, April 15, 2023, 6:50 pm, Phil G <phil@...> wrote:

What I usually do (where I have a decoder at each “end” of a train) is to give them the SAME address. This usually does the trick

You might need to change the “normal direction” to “reverse” on the Basic pane for the one at the “back”. It depends on how it’s directional lights are configured?

Bear in mind though - if you have two decoders with the same address on the layout at the same time, be VERY careful with any programming “on the main”

Phil G

On 15 Apr 2023, at 18:04, Duncan via groups.io <dunradar09@...> wrote:

? Good afternoon JMRI Team,

I am successfully reporting that I have control of the above?Bachmann DBSO lighting under Roster. ?Firstly I?put the coach on the program track. ?I?have been able to re-label the function keys with the actual names of the?areas the lights illuminate, including directional lights.

? Initially the cab light wouldn’t stay on, I wasn’t happy as you would appreciate. ?So I had a look at the advanced area and looked at the cv list. ?These didn’t match the cv list and the corresponding values they had in comparison to those that Shaun from Bachmann supplied. ?I then pressed the Read All Sheets from the bottom few rows of buttons, after the information was received and I could see values changing. ?

My last task/objective, is it possible to have this DBSO and the loco it runs with to ‘linked in a consist’ within JMRI so that if I change direction of the loco then the directional?lights of the loco and the DBSO will both change at the same time, instaa we as of me having to goto the separate?DBSO ID?in the roster and change the direction?

Thanks for your help in this subject - brilliant!

Duncan?

On Friday, April 14, 2023, 9:34 pm, Duncan via groups.io <dunradar09@...> wrote:

Cheers Phil,

I’m enjoying digital and seeing its advantages. ?The moths are not so happy as they have been exposed to daylight quite a few times of late.?

I am on Facebook and like computer tech even thought I’m no good on code etc.?

Kind regards?

Duncan

On Friday, April 14, 2023, 9:04 pm, Phil G <phil@...> wrote:

Welcome to the World of Digital Duncan - pretty sure you won't regret it

As you've discovered, there's plenty of help here with JMRI-related issues. If you are on FaceBook, I also suggest you consider joining the NCE Corporation FaceBookgroup () as they can help with any NCE issues/questions you may have

Don't worry too much about being a "newbie" - sometimes the only difference between a newbie and an "expert" is how many pages further ahead in the manual the expert is :)

Phil G

On 14/04/2023 20:45, Duncan via groups.io wrote:

Thanks Dave,

I’m new to DCC and this week?have?just received?an interface for my NCE PowerCab, which I got last summer. ?Since then my layout was analogue. ?Hence JMRI is a totally new thing and what it does, along with what different cv’s do. ?

Kind regards?

Duncan

On Friday, April 14, 2023, 1:44 am, Dave Heap <dgheap@...> wrote:

?All,

On 13 Apr 2023, at 11:42 pm, Duncan via groups.io <dunradar09@...> wrote:

ESU Roco 10745

???Either Roco 10745 old

???Or ?????Roco 10745 v56

ESU SwitchPilot

???Either SwitchPilot

???Or ??????SwitchPilot Servo

???Or ??????SwitchPilot Servo (MA)

???Or ??????SwitchPilot Servo (2013)

???Or ??????SwitchPilot V2.0

???Or ??????SwitchPilot Servo V2.0

For those decoders (CV 007 < 255 and CV 008 = 151) it's not possible to uniquely determine the decoder model. CV7 is only a firmware version and subject to change (LokProgrammer software/hardware allows user to update firmware).

Only those decoders that return CV7=255 and CV8=151 support indexed CV mapping and access to the RailCom Product ID CVs.

These are?CV="0.255.261"to?CV="0.255.264" and make a 4 byte?Little Endian value. The LokProgrammer software has a Supported Decoders menu item and this has a "many to one" mapping of Product IDs to Decoder Models .

Before my health failed I used LokProgrammer's "Supported Decoders t"o maintain a mapping list for JMRI definitions use:

<>

Dave in Australia

Hi Nigel,

Now your loosing me, how do you know what cv’s do what, and why please?

Thanks

Duncan

On Saturday, April 15, 2023, 7:44 pm, Nigel Cliffe <nigel.cliffe@...> wrote:

Decoder Locking (CV15+CV16) is one way to deal with several decoders in the same train with the same address and not wanting all to change together to programming-on-the-main.?

Decoder Locks are usually set and released manually (single CV programming, rather than decoder files).??

If using Advanced Consists, then will need to look at CV's 21 and 22 to indicate which functions are controlled by Consist Address and which by Loco Address.? ?

- Nigel

------ Original Message ------

From "Duncan via groups.io" <dunradar09@...>

To "[email protected]" <[email protected]>

Date 15/04/2023 19:11:02

Subject Re: [jmriusers] Which decoder information Bachmann 39-737ADC BR Mk2F DBSO coach

Will do Phil G, thanks

I may look at consisting as well?just incase, I see what you mean.?

Regards

Duncan?

On Saturday, April 15, 2023, 6:50 pm, Phil G <phil@...> wrote:

What I usually do (where I have a decoder at each “end” of a train) is to give them the SAME address. This usually does the trick

You might need to change the “normal direction” to “reverse” on the Basic pane for the one at the “back”. It depends on how it’s directional lights are configured?

Bear in mind though - if you have two decoders with the same address on the layout at the same time, be VERY careful with any programming “on the main”

Phil G

On 15 Apr 2023, at 18:04, Duncan via groups.io <dunradar09@...> wrote:

? Good afternoon JMRI Team,

I am successfully reporting that I have control of the above?Bachmann DBSO lighting under Roster. ?Firstly I?put the coach on the program track. ?I?have been able to re-label the function keys with the actual names of the?areas the lights illuminate, including directional lights.

? Initially the cab light wouldn’t stay on, I wasn’t happy as you would appreciate. ?So I had a look at the advanced area and looked at the cv list. ?These didn’t match the cv list and the corresponding values they had in comparison to those that Shaun from Bachmann supplied. ?I then pressed the Read All Sheets from the bottom few rows of buttons, after the information was received and I could see values changing. ?

My last task/objective, is it possible to have this DBSO and the loco it runs with to ‘linked in a consist’ within JMRI so that if I change direction of the loco then the directional?lights of the loco and the DBSO will both change at the same time, instaa we as of me having to goto the separate?DBSO ID?in the roster and change the direction?

Thanks for your help in this subject - brilliant!

Duncan?

On Friday, April 14, 2023, 9:34 pm, Duncan via groups.io <dunradar09@...> wrote:

Cheers Phil,

I’m enjoying digital and seeing its advantages. ?The moths are not so happy as they have been exposed to daylight quite a few times of late.?

I am on Facebook and like computer tech even thought I’m no good on code etc.?

Kind regards?

Duncan

On Friday, April 14, 2023, 9:04 pm, Phil G <phil@...> wrote:

Welcome to the World of Digital Duncan - pretty sure you won't regret it

As you've discovered, there's plenty of help here with JMRI-related issues. If you are on FaceBook, I also suggest you consider joining the NCE Corporation FaceBookgroup () as they can help with any NCE issues/questions you may have

Don't worry too much about being a "newbie" - sometimes the only difference between a newbie and an "expert" is how many pages further ahead in the manual the expert is :)

Phil G

On 14/04/2023 20:45, Duncan via groups.io wrote:

Thanks Dave,

I’m new to DCC and this week?have?just received?an interface for my NCE PowerCab, which I got last summer. ?Since then my layout was analogue. ?Hence JMRI is a totally new thing and what it does, along with what different cv’s do. ?

Kind regards?

Duncan

On Friday, April 14, 2023, 1:44 am, Dave Heap <dgheap@...> wrote:

?All,

On 13 Apr 2023, at 11:42 pm, Duncan via groups.io <dunradar09@...> wrote:

ESU Roco 10745

???Either Roco 10745 old

???Or ?????Roco 10745 v56

ESU SwitchPilot

???Either SwitchPilot

???Or ??????SwitchPilot Servo

???Or ??????SwitchPilot Servo (MA)

???Or ??????SwitchPilot Servo (2013)

???Or ??????SwitchPilot V2.0

???Or ??????SwitchPilot Servo V2.0

For those decoders (CV 007 < 255 and CV 008 = 151) it's not possible to uniquely determine the decoder model. CV7 is only a firmware version and subject to change (LokProgrammer software/hardware allows user to update firmware).

Only those decoders that return CV7=255 and CV8=151 support indexed CV mapping and access to the RailCom Product ID CVs.

These are?CV="0.255.261"to?CV="0.255.264" and make a 4 byte?Little Endian value. The LokProgrammer software has a Supported Decoders menu item and this has a "many to one" mapping of Product IDs to Decoder Models .

Before my health failed I used LokProgrammer's "Supported Decoders t"o maintain a mapping list for JMRI definitions use:

<>

Dave in Australia

Decoder Locking (CV15+CV16) is one way to deal with several decoders in the same train with the same address and not wanting all to change together to programming-on-the-main.?

Decoder Locks are usually set and released manually (single CV programming, rather than decoder files).??

If using Advanced Consists, then will need to look at CV's 21 and 22 to indicate which functions are controlled by Consist Address and which by Loco Address.? ?

- Nigel

------ Original Message ------

From "Duncan via groups.io" <dunradar09@...>

To "[email protected]" <[email protected]>

Date 15/04/2023 19:11:02

Subject Re: [jmriusers] Which decoder information Bachmann 39-737ADC BR Mk2F DBSO coach

Will do Phil G, thanks

I may look at consisting as well?just incase, I see what you mean.?

Regards

Duncan?

On Saturday, April 15, 2023, 6:50 pm, Phil G <phil@...> wrote:

What I usually do (where I have a decoder at each “end” of a train) is to give them the SAME address. This usually does the trick

You might need to change the “normal direction” to “reverse” on the Basic pane for the one at the “back”. It depends on how it’s directional lights are configured?

Bear in mind though - if you have two decoders with the same address on the layout at the same time, be VERY careful with any programming “on the main”

Phil G

On 15 Apr 2023, at 18:04, Duncan via groups.io <dunradar09@...> wrote:

? Good afternoon JMRI Team,

I am successfully reporting that I have control of the above?Bachmann DBSO lighting under Roster. ?Firstly I?put the coach on the program track. ?I?have been able to re-label the function keys with the actual names of the?areas the lights illuminate, including directional lights.

? Initially the cab light wouldn’t stay on, I wasn’t happy as you would appreciate. ?So I had a look at the advanced area and looked at the cv list. ?These didn’t match the cv list and the corresponding values they had in comparison to those that Shaun from Bachmann supplied. ?I then pressed the Read All Sheets from the bottom few rows of buttons, after the information was received and I could see values changing. ?

My last task/objective, is it possible to have this DBSO and the loco it runs with to ‘linked in a consist’ within JMRI so that if I change direction of the loco then the directional?lights of the loco and the DBSO will both change at the same time, instaa we as of me having to goto the separate?DBSO ID?in the roster and change the direction?

Thanks for your help in this subject - brilliant!

Duncan?

On Friday, April 14, 2023, 9:34 pm, Duncan via groups.io <dunradar09@...> wrote:

Cheers Phil,

I’m enjoying digital and seeing its advantages. ?The moths are not so happy as they have been exposed to daylight quite a few times of late.?

I am on Facebook and like computer tech even thought I’m no good on code etc.?

Kind regards?

Duncan

On Friday, April 14, 2023, 9:04 pm, Phil G <phil@...> wrote:

Welcome to the World of Digital Duncan - pretty sure you won't regret it

As you've discovered, there's plenty of help here with JMRI-related issues. If you are on FaceBook, I also suggest you consider joining the NCE Corporation FaceBookgroup () as they can help with any NCE issues/questions you may have

Don't worry too much about being a "newbie" - sometimes the only difference between a newbie and an "expert" is how many pages further ahead in the manual the expert is :)

Phil G

On 14/04/2023 20:45, Duncan via groups.io wrote:

Thanks Dave,

I’m new to DCC and this week?have?just received?an interface for my NCE PowerCab, which I got last summer. ?Since then my layout was analogue. ?Hence JMRI is a totally new thing and what it does, along with what different cv’s do. ?

Kind regards?

Duncan

On Friday, April 14, 2023, 1:44 am, Dave Heap <dgheap@...> wrote:

?All,

On 13 Apr 2023, at 11:42 pm, Duncan via groups.io <dunradar09@...> wrote:

ESU Roco 10745

???Either Roco 10745 old

???Or ?????Roco 10745 v56

ESU SwitchPilot

???Either SwitchPilot

???Or ??????SwitchPilot Servo

???Or ??????SwitchPilot Servo (MA)

???Or ??????SwitchPilot Servo (2013)

???Or ??????SwitchPilot V2.0

???Or ??????SwitchPilot Servo V2.0

For those decoders (CV 007 < 255 and CV 008 = 151) it's not possible to uniquely determine the decoder model. CV7 is only a firmware version and subject to change (LokProgrammer software/hardware allows user to update firmware).

Only those decoders that return CV7=255 and CV8=151 support indexed CV mapping and access to the RailCom Product ID CVs.

These are?CV="0.255.261"to?CV="0.255.264" and make a 4 byte?Little Endian value. The LokProgrammer software has a Supported Decoders menu item and this has a "many to one" mapping of Product IDs to Decoder Models .

Before my health failed I used LokProgrammer's "Supported Decoders t"o maintain a mapping list for JMRI definitions use:

<>

Dave in Australia

What I usually do (where I have a decoder at each “end” of a train) is to give them the SAME address. This usually does the trick

You might need to change the “normal direction” to “reverse” on the Basic pane for the one at the “back”. It depends on how it’s directional lights are configured?

Bear in mind though - if you have two decoders with the same address on the layout at the same time, be VERY careful with any programming “on the main”

Phil G

On 15 Apr 2023, at 18:04, Duncan via groups.io <dunradar09@...> wrote:

? Good afternoon JMRI Team,

I am successfully reporting that I have control of the above?Bachmann DBSO lighting under Roster. ?Firstly I?put the coach on the program track. ?I?have been able to re-label the function keys with the actual names of the?areas the lights illuminate, including directional lights.

? Initially the cab light wouldn’t stay on, I wasn’t happy as you would appreciate. ?So I had a look at the advanced area and looked at the cv list. ?These didn’t match the cv list and the corresponding values they had in comparison to those that Shaun from Bachmann supplied. ?I then pressed the Read All Sheets from the bottom few rows of buttons, after the information was received and I could see values changing. ?

My last task/objective, is it possible to have this DBSO and the loco it runs with to ‘linked in a consist’ within JMRI so that if I change direction of the loco then the directional?lights of the loco and the DBSO will both change at the same time, instaa we as of me having to goto the separate?DBSO ID?in the roster and change the direction?

Thanks for your help in this subject - brilliant!

Duncan?

On Friday, April 14, 2023, 9:34 pm, Duncan via groups.io <dunradar09@...> wrote:

Cheers Phil,

I’m enjoying digital and seeing its advantages. ?The moths are not so happy as they have been exposed to daylight quite a few times of late.?

I am on Facebook and like computer tech even thought I’m no good on code etc.?

Kind regards?

Duncan

On Friday, April 14, 2023, 9:04 pm, Phil G <phil@...> wrote:

Welcome to the World of Digital Duncan - pretty sure you won't regret it

As you've discovered, there's plenty of help here with JMRI-related issues. If you are on FaceBook, I also suggest you consider joining the NCE Corporation FaceBookgroup () as they can help with any NCE issues/questions you may have

Don't worry too much about being a "newbie" - sometimes the only difference between a newbie and an "expert" is how many pages further ahead in the manual the expert is :)

Phil G

On 14/04/2023 20:45, Duncan via groups.io wrote:

Thanks Dave,

I’m new to DCC and this week?have?just received?an interface for my NCE PowerCab, which I got last summer. ?Since then my layout was analogue. ?Hence JMRI is a totally new thing and what it does, along with what different cv’s do. ?

Kind regards?

Duncan

On Friday, April 14, 2023, 1:44 am, Dave Heap <dgheap@...> wrote:

?All,

On 13 Apr 2023, at 11:42 pm, Duncan via groups.io <dunradar09@...> wrote:

ESU Roco 10745

???Either Roco 10745 old

???Or ?????Roco 10745 v56

ESU SwitchPilot

???Either SwitchPilot

???Or ??????SwitchPilot Servo

???Or ??????SwitchPilot Servo (MA)

???Or ??????SwitchPilot Servo (2013)

???Or ??????SwitchPilot V2.0

???Or ??????SwitchPilot Servo V2.0

For those decoders (CV 007 < 255 and CV 008 = 151) it's not possible to uniquely determine the decoder model. CV7 is only a firmware version and subject to change (LokProgrammer software/hardware allows user to update firmware).

Only those decoders that return CV7=255 and CV8=151 support indexed CV mapping and access to the RailCom Product ID CVs.

These are?CV="0.255.261"to?CV="0.255.264" and make a 4 byte?Little Endian value. The LokProgrammer software has a Supported Decoders menu item and this has a "many to one" mapping of Product IDs to Decoder Models .

Before my health failed I used LokProgrammer's "Supported Decoders t"o maintain a mapping list for JMRI definitions use:

<>

Dave in Australia

On 15 Apr 2023, at 18:04, Duncan via groups.io <dunradar09@...> wrote:

? Good afternoon JMRI Team,

I am successfully reporting that I have control of the above?Bachmann DBSO lighting under Roster. ?Firstly I?put the coach on the program track. ?I?have been able to re-label the function keys with the actual names of the?areas the lights illuminate, including directional lights.

? Initially the cab light wouldn’t stay on, I wasn’t happy as you would appreciate. ?So I had a look at the advanced area and looked at the cv list. ?These didn’t match the cv list and the corresponding values they had in comparison to those that Shaun from Bachmann supplied. ?I then pressed the Read All Sheets from the bottom few rows of buttons, after the information was received and I could see values changing. ?

My last task/objective, is it possible to have this DBSO and the loco it runs with to ‘linked in a consist’ within JMRI so that if I change direction of the loco then the directional?lights of the loco and the DBSO will both change at the same time, instaa we as of me having to goto the separate?DBSO ID?in the roster and change the direction?

Thanks for your help in this subject - brilliant!

Duncan?

On Friday, April 14, 2023, 9:34 pm, Duncan via groups.io <dunradar09@...> wrote:

Cheers Phil,

I’m enjoying digital and seeing its advantages. ?The moths are not so happy as they have been exposed to daylight quite a few times of late.?

I am on Facebook and like computer tech even thought I’m no good on code etc.?

Kind regards?

Duncan

On Friday, April 14, 2023, 9:04 pm, Phil G <phil@...> wrote:

Welcome to the World of Digital Duncan - pretty sure you won't regret it

As you've discovered, there's plenty of help here with JMRI-related issues. If you are on FaceBook, I also suggest you consider joining the NCE Corporation FaceBookgroup () as they can help with any NCE issues/questions you may have

Don't worry too much about being a "newbie" - sometimes the only difference between a newbie and an "expert" is how many pages further ahead in the manual the expert is :)

Phil G

On 14/04/2023 20:45, Duncan via groups.io wrote:

Thanks Dave,

I’m new to DCC and this week?have?just received?an interface for my NCE PowerCab, which I got last summer. ?Since then my layout was analogue. ?Hence JMRI is a totally new thing and what it does, along with what different cv’s do. ?

Kind regards?

Duncan

On Friday, April 14, 2023, 1:44 am, Dave Heap <dgheap@...> wrote:

?All,

On 13 Apr 2023, at 11:42 pm, Duncan via groups.io <dunradar09@...> wrote:

ESU Roco 10745

???Either Roco 10745 old

???Or ?????Roco 10745 v56

ESU SwitchPilot

???Either SwitchPilot

???Or ??????SwitchPilot Servo

???Or ??????SwitchPilot Servo (MA)

???Or ??????SwitchPilot Servo (2013)

???Or ??????SwitchPilot V2.0

???Or ??????SwitchPilot Servo V2.0

For those decoders (CV 007 < 255 and CV 008 = 151) it's not possible to uniquely determine the decoder model. CV7 is only a firmware version and subject to change (LokProgrammer software/hardware allows user to update firmware).

Only those decoders that return CV7=255 and CV8=151 support indexed CV mapping and access to the RailCom Product ID CVs.

These are?CV="0.255.261"to?CV="0.255.264" and make a 4 byte?Little Endian value. The LokProgrammer software has a Supported Decoders menu item and this has a "many to one" mapping of Product IDs to Decoder Models .

Before my health failed I used LokProgrammer's "Supported Decoders t"o maintain a mapping list for JMRI definitions use:

<>

Dave in Australia