|
Before anyone tells me about CV217, I am aware of this issue.?
?
I cannot read or write to one of my BLI locomotives using JMRI's Decoder Pro. Things that I have tried, what am I missing.
- Used another BLI locomotive of same decoder type, and confirmed that everything is connected and working as expected.
- I am able to read CV217 on this other locomotive and change it to a lower value and read and program without issue.
- I started thinking that maybe the decoder was dead, but I can run it and access all functions on Short Address 03.
- I am trying to change the address and lower the volume.
- Tried both Direct Byte and Paged.
- Tried writing CV217 to 70, over and over again, hoping that it would take.? I can run the loco both before and after, confirming that I have connection/control on the track.
Any thoughts?
?
(I stopped using BLI locomotives about 1.5 years ago due to all the issues I was having with P3 decoders. But the P4 decoders had less issues, so I decided I would get them out and try running them again. Three of them have been fine, but this one is not cooperating)
?
JMRI version: 5.10 (last stable release)
BLI Locomotive: 3930, SW7, ACL #645, Paragon 4 (I have too many of these NW2/SW7 switchers, when they work, they are nice)
Command Station: YD7001 (Digikeijs DR5000 upgraded to YaMoRC)
I also have an ESU programmer, but not sure how to use it with BLI locos? Is there a way to try to use the ESU programmer to change CV217 to 70?
?
Thanks
--
|
You may need a programming track booster such as a Soundtraxx PTB-100. -- Peter Ulvestad Linux Mint 22.1, JMRI 5.11.3plus, Java 21.0.5 JMRI Users Group Moderator ( /g/jmriusers ) JMRI Developers Group Moderator ( ) Tam Valley Group Moderator ( ) Sprog-DCC Group Moderator ( ) Edmonton Model Railroad Association ( )
|
Heath,
?
I long ago adopted using POM for all BLI Paragon programming.
?
BLI tech support recommended POM for Paragon 2, and Paragon 3 (CV7=5 or lower) if you were unable to ‘read’ CVs on a service mode programming track.
?
When CV217 was introduced (Paragon 3, CV7=6 or higher), I assisted one person in setting it up.? It’s a trial and error setup and took way too much time.? I went back to POM (right out of the box) and haven’t
looked back.
?
FWIW – I haven’t found a PTB helpful with Paragon decoders.
?
My 2 cents.? YMMV.
?
Ross
?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]>
On Behalf Of Human[c]ity Junction
Sent: Monday, February 24, 2025 12:15 PM
To: [email protected]
Subject: [jmriusers] Decoder Pro and BLI locomotive, No Acknowledge from locomotive
?
Before anyone tells me about CV217, I am aware of this issue.?
I cannot read or write to one of my BLI locomotives using JMRI's Decoder Pro. Things that I have tried, what am I missing.
-
Used another BLI locomotive of same decoder type, and confirmed that everything is connected and working as expected.
-
I am able to read CV217 on this other locomotive and change it to a lower value and read and program without issue.
-
I started thinking that maybe the decoder was dead, but I can run it and access all functions on Short Address 03.
-
I am trying to change the address and lower the volume.
-
Tried both Direct Byte and Paged.
-
Tried writing CV217 to 70, over and over again, hoping that it would take.? I can run the loco both before and after, confirming that I have connection/control on the track.
(I stopped using BLI locomotives about 1.5 years ago due to all the issues I was having with P3 decoders. But the P4 decoders had less issues, so I decided I would get them out and try running them again. Three of them have been fine, but
this one is not cooperating)
JMRI version: 5.10 (last stable release)
BLI Locomotive: 3930, SW7, ACL #645, Paragon 4 (I have too many of these NW2/SW7 switchers, when they work, they are nice)
Command Station: YD7001 (Digikeijs DR5000 upgraded to YaMoRC)
I also have an ESU programmer, but not sure how to use it with BLI locos? Is there a way to try to use the ESU programmer to change CV217 to 70?
|
On Mon, Feb 24, 2025 at 01:53 PM, Peter Ulvestad wrote:
You may need a programming track booster such as a Soundtraxx PTB-100
?
If a booster is the solution, I might try and get my hands on the new BLI CV setter, which I am assuming is designed to work with their (difficult to program) decoders. Unfortunately I have yet to find one in stock anywhere.
--
|
On Mon, Feb 24, 2025 at 02:12 PM, Ross Kudlick wrote:
I long ago adopted using POM for all BLI Paragon programming.
?
POM makes me nervous with all the locomotives I have on the layout, and the thought of having to take all the locos off the layout or turn off power to all the other tracks just means that I will likely screw up more than just the loco I am trying to program.
?
I know a lot of people use it successfully, I just do not trust myself not to make things worse.
--
|
I also have an ESU programmer, but not sure how to use it with BLI locos? Is there a way to try to use the ESU programmer to change CV217 to 70? ? Heath:
The ESU LokProgrammer is designed for LokSound decoders, not BLI Paragon decoders. However, I have heard and seen on one of the LokProgrammer panes that it will do POM. If that means true NMRA POM, then I guess you might be able to use the LokProgrammer to do POM on a Paragon. I’ve never tried it. But I can’t see how that would be any different or better than POM using your DCC command station.
Mark
|
I just went through troubles with a BLI E1A unit with a Paragon 4 decoder trying to program it with Decoder Pro and an NCE PowerCab. I'd make a change, like to the decoder address or sound volume, and then lose the connection with it. It wouldn't respond to the new address or the original "3" address. After a period of banging my head against the wall I found that the changes appeared to "take" after removing the engine from the programming track and putting it back on. It was like the decoder had to be rebooted in order for the changes to take effect.
With this knowledge I successfully made the rest of the changes, using a toggle switch between the PowerCab and track, to kill power and let the decoder reboot. When I got to the E1B unit I made all necessary changes without any trouble using this routine.
Rick Jones
Why don't sheep shrink when it rains?
toggle quoted message
Show quoted text
On 2/24/2025 11:14 AM, Human[c]ity Junction wrote: Before anyone tells me about CV217, I am aware of this issue.
I cannot read or write to one of my BLI locomotives using JMRI's Decoder Pro. Things that I have tried, what am I missing.
* Used another BLI locomotive of same decoder type, and confirmed that
everything is connected and working as expected.
o I am able to read CV217 on this other locomotive and change it
to a lower value and read and program without issue.
* I started thinking that maybe the decoder was dead, but I can run it
and access all functions on Short Address 03.
o I am trying to change the address and lower the volume.
* Tried both Direct Byte and Paged.
* Tried writing CV217 to 70, over and over again, hoping that it would
take.? I can run the loco both before and after, confirming that I
have connection/control on the track.
Any thoughts?
(I stopped using BLI locomotives about 1.5 years ago due to all the issues I was having with P3 decoders. But the P4 decoders had less issues, so I decided I would get them out and try running them again. Three of them have been fine, but this one is not cooperating)
JMRI version: 5.10 (last stable release)
BLI Locomotive: 3930, SW7, ACL #645, Paragon 4 (I have too many of these NW2/SW7 switchers, when they work, they are nice)
Command Station: YD7001 (Digikeijs DR5000 upgraded to YaMoRC)
I also have an ESU programmer, but not sure how to use it with BLI locos? Is there a way to try to use the ESU programmer to change CV217 to 70?
|
Heath,
?
POM is a very valuable DCC tool most users leaved ‘packed in the box.’
?
I started using POM on my test track with DecoderPro.? My initial programming (address, normal direction, and a few other features) is ‘at the bench.’?
?
Then I move to the railroad, always using DecoderPro.? Only the address in the DecoderPro file I have open will be programmed.
?
POM is fast, reliable, and provides instant feedback (sound level, light intensity or characteristic, speed).? DecoderPro makes it very safe.
?
Give it a try.? I’ve demonstrated to many people who were reluctant and have since added to their tool bag.
?
Give it a try.
?
Ross
?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]>
On Behalf Of Human[c]ity Junction
Sent: Monday, February 24, 2025 2:18 PM
To: [email protected]
Subject: Re: [jmriusers] BLI locomotive, No Acknowledge from locomotive #bli
?
On Mon, Feb 24, 2025 at 02:12 PM, Ross Kudlick wrote:
I long ago adopted using POM for all BLI Paragon programming.
POM makes me nervous with all the locomotives I have on the layout, and the thought of having to take all the locos off the layout or turn off power to all the other tracks just means that I will likely screw up more than just the loco
I am trying to program.
I know a lot of people use it successfully, I just do not trust myself not to make things worse.
|
On Mon, Feb 24, 2025 at 02:25 PM, Mark Granville wrote:
The ESU LokProgrammer is designed for LokSound decoders
?
I had heard of some people using them with other deciders to program CVs, so I was not sure if it was worth trying.
?
I tried POM with both the ESU Programmers and my command station and nothing.
?
And of course it was running fine before, but now it is only making A LOT of noise, no movement.
--
|
I agree with everything Ross has said. PTB-100 doesn't help. The CV217 I discussed in my blog post?
doesn't always work and it takes a longer time to work with than it's worth. The only consistent way to program BLI decoders?is either 1. gut and replace the decoder or 2.?use POM. POM has never failed.
?
On Mon, Feb 24, 2025 at 12:13?PM Ross Kudlick via <Ross_Kudlick= [email protected]> wrote:
Heath,
?
I long ago adopted using POM for all BLI Paragon programming.
?
BLI tech support recommended POM for Paragon 2, and Paragon 3 (CV7=5 or lower) if you were unable to ‘read’ CVs on a service mode programming track.
?
When CV217 was introduced (Paragon 3, CV7=6 or higher), I assisted one person in setting it up.? It’s a trial and error setup and took way too much time.? I went back to POM (right out of the box) and haven’t
looked back.
?
FWIW – I haven’t found a PTB helpful with Paragon decoders.
?
My 2 cents.? YMMV.
?
Ross
?
?
Before anyone tells me about CV217, I am aware of this issue.?
I cannot read or write to one of my BLI locomotives using JMRI's Decoder Pro. Things that I have tried, what am I missing.
-
Used another BLI locomotive of same decoder type, and confirmed that everything is connected and working as expected.
-
I am able to read CV217 on this other locomotive and change it to a lower value and read and program without issue.
-
I started thinking that maybe the decoder was dead, but I can run it and access all functions on Short Address 03.
-
I am trying to change the address and lower the volume.
-
Tried both Direct Byte and Paged.
-
Tried writing CV217 to 70, over and over again, hoping that it would take.? I can run the loco both before and after, confirming that I have connection/control on the track.
(I stopped using BLI locomotives about 1.5 years ago due to all the issues I was having with P3 decoders. But the P4 decoders had less issues, so I decided I would get them out and try running them again. Three of them have been fine, but
this one is not cooperating)
JMRI version: 5.10 (last stable release)
BLI Locomotive: 3930, SW7, ACL #645, Paragon 4 (I have too many of these NW2/SW7 switchers, when they work, they are nice)
Command Station: YD7001 (Digikeijs DR5000 upgraded to YaMoRC)
I also have an ESU programmer, but not sure how to use it with BLI locos? Is there a way to try to use the ESU programmer to change CV217 to 70?
-- John Griffin
Model Railroading Topics
|
Heath,
?
I've also posted about CV 217 settings, but I always use a programming track. And my programmer is a SPROG 3 (while my layout track power comes from an EVOXD Digitrax system).
?
My procedure is to write a new value to it, and then try to read it back. If a value of 70 isn't working, try higher values. My locos settings range from 20 to 70, but you might need a larger value.
?
Regards
|
Heath @ Human[c]ity Junction
Peter Ulvestad
Rick Jones