BMMECNYC rrinker I can't imagine ANYONE testing every possible long address to validate their code. It took long enought to go through and test half of the 36 suspect addresses to check for the error. I cant imagine trying to test ~10k address. One would go bonkers. Decoders arrived in my mailbox today. Might install and test one or two tomorrow. Will let you guys know.
rrinker I can't imagine ANYONE testing every possible long address to validate their code.
It took long enought to go through and test half of the 36 suspect addresses to check for the error. I cant imagine trying to test ~10k address. One would go bonkers.
Decoders arrived in my mailbox today. Might install and test one or two tomorrow. Will let you guys know.
After reading about other people having paragon 3 problems, I recalled this thread and decided to update you guys. I recently purchased a railroad space which happens to have other rooms on top of it (some of which are more railroad spaces).
I have not had time to replace the boards.
BMMECNYC After reading about other people having paragon 3 problems, I recalled this thread and decided to update you guys. I recently purchased a railroad space which happens to have other rooms on top of it (some of which are more railroad spaces). I have not had time to replace the boards.
Rich
Alton Junction
Well, two years later. The new boards are in.
BMMECNYC Well, two years later. The new boards are in.
Well,
I quit the club I was in, so I dont have a layout on which to operate them. The old decoders went back to BLI before Christmas.
My current modular layout will not support six axle locomotives by design.
I'll update you all when I finally get the home railroad up and running.
I'm bumping this hoping we don't forget this strange behavior. Personally, I'll be checking all my Paragon 2s tomorrow. I'm going to sleep now since it's 3:30.
Man, I love this forum...
WP Lives
softail86mark I'm bumping this hoping we don't forget this strange behavior. Personally, I'll be checking all my Paragon 2s tomorrow. I'm going to sleep now since it's 3:30. Man, I love this forum...
In my 15 years on the forum, this was perhaps the most interesting, albeit bizarre, thread to ever appear on the forum. It certainly was a lot of fun doing the detective work necessary to solve this issue.
softail86mark ...Personally, I'll be checking all my Paragon 2s tomorrow...
...Personally, I'll be checking all my Paragon 2s tomorrow...
Okay, I checked all one of them (in a row...I thought I had a pile of them, but, alas they're Paragon (1).)
Anyway, the only thing I can add is, running 28 forward, switching 128 stays forward, change direction, goes reverse, change direction again...STAYS REVERSE. Strange. I'll wait to see what BMMECNYC...gets from BLI. Or his new layout.
Paragon 1's are QSI decoders, completely different. Paragon 2 is BLI's first go at making their own decoder, Paragon 3 is a slightly updated version, mostly adding the radio link to send low frequency sounds to the Rolling Thunder subwoofer.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Thanks Randy, did not know that.
softail86mark softail86mark ...Personally, I'll be checking all my Paragon 2s tomorrow... Okay, I checked all one of them (in a row...I thought I had a pile of them, but, alas they're Paragon (1).) Anyway, the only thing I can add is, running 28 forward, switching 128 stays forward, change direction, goes reverse, change direction again...STAYS REVERSE. Strange. I'll wait to see what BMMECNYC...gets from BLI. Or his new layout.
Regarding your issue with the Paragon 1, I have a number of locomotives with the Paragon 1 decoder, so I tested several of them using the directional and speed step sequence that you used. All performed correctly and none of them failed to respond to the direction button. Whenever I toggled the Direction button, the loco changed direction as intended.
My system is an NCE PH-Pro. I don't recall if you mentioned your DCC system. Perhaps, the Direction button on your throttle is not working correctly.
richhotrain My system is an NCE PH-Pro. I don't recall if you mentioned your DCC system. Perhaps, the Direction button on your throttle is not working correctly. Rich
So sorry I wasn't following the thread, but I have an NCE Power Pro started set with an SB5 booster. Nothing much different from what others are using.
Anyway, thanks Rich and Randy...
Bump (waiting for updates, wish I could help with his layout...)
Hi all,
I guess I should give you all an update. The layout probably isnt going to happen. I have recently had a job change. I have left my $35.60 an hour job for one that pays $10.10 an hour to maintain my sanity. This was my choice, but this has a few side effects (no hobby dollars).
Next chance I get to run the locomotive on DCC I will let you know.
Tested, not fixed. Will be contacting BLI.
The only way they can fix that is a new decoder with new firmware, as we figured out pages ago, it's a serious bug in their firmware based on certain bit patterns appearing in a specified address.
I'm curious if the same thing happened in a different BLI loco - one would typically never address it with the address you are using because it doesn't match the cab number but the decoders likely all have the same firmware. Anyone else with the same vintage BLI loco want to give it a try and see if theirs acts strange as well? Even if it works fine on the address you normally use.
rrinker The only way they can fix that is a new decoder with new firmware, as we figured out pages ago, it's a serious bug in their firmware based on certain bit patterns appearing in a specified address. I'm curious if the same thing happened in a different BLI loco - one would typically never address it with the address you are using because it doesn't match the cab number but the decoders likely all have the same firmware. Anyone else with the same vintage BLI loco want to give it a try and see if theirs acts strange as well? Even if it works fine on the address you normally use. --Randy
Randy,
Ive got 4 BLI Paragon 2 locomotives. They all do this. And I doubt based on the conversation I had that they are going to fix this. They arent making Paragon 2 anymore, and Im the only one who has reported the problem.
Well, Rich confirmed it, it's a bug that appears in other Paragon 2 decoders as well. Would have been my guess that it appears across all of them, outside of the sound files there's little reason why they would have different firmware for each loco model.
Now - did they fix it with Paragon 3, or does it still exist there? The only real difference in the decoders is the addition of the radio to transmit the bass to the Rolling Thunder subwoofer, and that's probably all on or past the audio stage, shouldn't have required any changes to the motor drive and NMRA DCC packet decoder portion of the decoder, unless they realized there was a bug in Paragon 2 and fixed it.
Unfortunately, I don't own any BLI locomotives with the Paragon 3 decoder, so I am unable to test for the fault that occurs in Paragon 2 decoders.
Anyone out there with a Paragon 3, willing to perform the test?
richhotrain Unfortunately, I don't own any BLI locomotives with the Paragon 3 decoder, so I am unable to test for the fault that occurs in Paragon 2 decoders. Anyone out there with a Paragon 3, willing to perform the test? Rich
Ive got one or two. Ive just been lazy about it. Not wanting to have to hook up the tender to the locomotive.
BLI told me that they were going to perform the test on Paragon 3.
Yeah, I don't have any Paragon anythings, I got my Reading T1s as the original PCM offering with Loksound decoders. I'm pushing it so as it is to include them in my era (by a year or 2, so not a huge application of modeler's license) so I ha dno reason to get the re-release with Paragon 2 or the latest Paragon 3 ones. Two's enough, and as a Rush (the band from Canada) fan, I have my 2112. Which SO tempts me to replace one of the sounds with a clip from the song.... maybe the second whistle, which I never use. I DO have a Lokprogrammer........