开云体育

  1. Jmriusers
  2. Topics

BDL 716 etc #digitrax

 

Why doesn't JMRI? "see" my DS74s, BDL 716 and BXpa1s.
?
I would love to be able to configure them using JMRI, the way I can my DS64s, BDL16 and PM42.
Is there some licensing dispute or other disagreement between Digitrax and the JMRI community?
?
David Richie
 

DS74's are in JMRI
BDL716 appear to be brand new.
Unfortunately, like most manufacturers, Digitrax does not do their own definitions so JMRI users must wait for someone to to produce them. To my knowledge Digitrax does not provide developers with any info on new boards so it takes developers quite awhile to learn how these boards operate.

--
Peter Ulvestad
Linux Mint 22.1, JMRI 5.11.2plus, 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 ( )
 

On 1/28/2025 10:16 AM, Peter Ulvestad via groups.io wrote:
DS74's are in JMRI
BDL716 appear to be brand new.
Unfortunately, like most manufacturers, Digitrax does not do their own definitions so JMRI users must wait for someone to to produce them. To my knowledge Digitrax does not provide developers with any info on new boards so it takes developers quite awhile to learn how these boards operate.
Well, it really takes one of JMRI's LocoNet developers some time _to figure out_ how a piece of new hardware _can be used in JMRI_, much less "make it do something" in JMRI. That takes some time, once that developer gets the hardware.

FWIW, I _would expect_ JMRI's support for the BDL716 to look more like what the DS74, DS78V, SE74, and PM74 have, not the DS54. And not like the DS64, SE8C, BDL16/162/168, and PM42. This is because the newer hardware uses different LocoNet messaging than the older stuff. But I have not touched any BDL716 hardware, so I cannot tell...

Currently, the latest JMRI "test release" has, I believe, the "ability" to show one _type_ of BDL716 message in LocoNet Monitor. That message is one which can show the BDL716 serial number and hardware revision and firmware version number. But that does not provide much "functionality".

Some day that will change, though.
 

On 1/28/2025 10:56 AM, billybob experimenter via groups.io wrote:
On 1/28/2025 10:16 AM, Peter Ulvestad via groups.io wrote:
DS74's are in JMRI
BDL716 appear to be brand new.
Unfortunately, like most manufacturers, Digitrax does not do their own definitions so JMRI users must wait for someone to to produce them. To my knowledge Digitrax does not provide developers with any info on new boards so it takes developers quite awhile to learn how these boards operate.
Well, it really takes one of JMRI's LocoNet developers some time _to figure out_ how a piece of new hardware _can be used in JMRI_, much less "make it do something" in JMRI.? That takes some time, once that developer gets the hardware.
FWIW, I _would expect_ JMRI's support for the BDL716 to look more like what the DS74, DS78V, SE74, and PM74 have, not the DS54.? And not like the DS64, SE8C, BDL16/162/168, and PM42.? This is because the newer hardware uses different LocoNet messaging than the older stuff.? But I have not touched any BDL716 hardware, so I cannot tell...
Currently, the latest JMRI "test release" has, I believe, the "ability" to show one _type_ of BDL716 message in LocoNet Monitor.? That message is one which can show the BDL716 serial number and hardware revision and firmware version number.? But that does not provide much "functionality".
Some day that will change, though.
Most Digitrax LocoNet accessories can be handled via the "Roster" feature, and that includes the support for DS74, DS78, SE74, and PM74 devices as mentioned above. Some Digitrax accessory devices do not, because they haven't been "figured out" - like the BDL716. Or they do not support any "known" LocoNet configuration - like the BXPA1.
 

On Jan 28, 2025, at 9:41?AM, David Richie via groups.io <david.r.richie@...> wrote:

Why doesn't JMRI "see" my DS74s, BDL 716 and BXpa1s.

What do you mean that JMRI doesn’t see your DS74s? What exactly is happening, and what do you expect to happen? I think that should be working.

The BXpa1’s don’t have any LocoNet-configurable options, so there’s not much we can do with those.



The BDL716 does have a few Op Switches that can be configured, so we could right a decoder definition for that. But first we need to confirm which of several types of messages should be used to read/write those Op Switches. It would be really helpful to get somebody with access to a physical BDL716 to checki that. Would you be willing to help with this? Thanks in advance.

Bob
—
Bob Jacobsen
rgj1927@...
 

As stated previously, the DS74 is operational in JMRI, I am using three at the moment. The BDL716 is functioning in JMRI for me for detection. I have not attempted to to use signal functions. I have all four ports for the test boards populated and they are also working. I am using the BDL716 on a speed profiling circle with 12 blocks and all is working fine out-of-the-box.
?
James M. Johnson
 

Plese note, I received three new DS74's and out of the box only the first turnout worked correctly. I had to update the firmware to get them to work correctly. I would suggest if your system is not seeing the devices to take a look at command station and device firmware. No problems with the BDL716 with respect to detection out of the box.
?
James M. Johnson
 

@BobJacobsen - not sure if anyone responded. We are using a 716 (and a 168) - and have the latest version of JMRI and can install test versions/etc. What do you need to write a decoder definition for it? We can help.
?
While the 716 seems to be working, I have noticed unexpected behavior on occasion. For example, a sensor(s) will go inactive when occupied and nothing has moved. The hack is to clear the section/re-occupy the section and the sensor is back active (and behaving). It may be related to toggling layout power or restarting JMRI - but have not found a pattern.
?
Paul.
?
?
?
 

Thanks for getting back to me.

Somebody volunteered to help with some testing. Unfortunately, none of the four methods JMRI knows for setting op switches seemed to work for the BDL716. So we’re somewhat stuck at this point. The next step is to try to do some reverse engineering of what the BDL716 understands, but that’s a slow and complicated process, and I don’t have direct access to a BDL716.

Bob

On Mar 17, 2025, at 10:49?AM, Paul Wash via groups.io <paul.wash@...> wrote:

@BobJacobsen - not sure if anyone responded. We are using a 716 (and a 168) - and have the latest version of JMRI and can install test versions/etc. What do you need to write a decoder definition for it? We can help.
While the 716 seems to be working, I have noticed unexpected behavior on occasion. For example, a sensor(s) will go inactive when occupied and nothing has moved. The hack is to clear the section/re-occupy the section and the sensor is back active (and behaving). It may be related to toggling layout power or restarting JMRI - but have not found a pattern.
—
Bob Jacobsen
rgj1927@...

1 - 9 of 9