Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Difference Between Compare and Reset
#decoderpro
toggle quoted message
Show quoted text
On 4 Apr 2025, at 11:46, Don Shroyer via groups.io <Donshroyer@...> wrote:
|
Testing the brake is simple. F11 is the default for these decoders. Make sure F11 is off.
-- Peter Ulvestad Linux Mint 22.1, JMRI 5.11.4plus, Java 21.0.6 JMRI Users Group Moderator ( /g/jmriusers ) JMRI Developers Group Moderator ( ) Tam Valley Group Moderator ( ) Sprog-DCC Group Moderator ( ) Edmonton Model Railroad Association ( ) |
开云体育OKAnother small step. Some decoders have a “disconnect” mode where you can power the prime mover WITHOUT engaging “drive”. If this is selected (or not actively unselected), you will experience the same symptoms
Do you have the original doc for the sound project??
Phil G? On 5 Apr 2025, at 10:21, Don Shroyer via groups.io <Donshroyer@...> wrote:
|
Don, if I have understood your problem correctly, then your locomotive runs after a decoder reset, but if you write your previously used CVs saved in DecoderPro back into the reset decoder, the locomotive no longer runs?
Yes, there may be CVs in the decoder that cannot be displayed with DecoderPro and therefore cannot be read or written. The CVs used are defined in the corresponding decoder template. To analyze your problem above, perform a decoder reset and then compare your saved CVs with the values in the decoder. You must check all the different CV values and evaluate them using the decoder documentation. Then you should be able to find the cause. Uli ? |
to navigate to use esc to dismiss