开云体育

oh cool if there is anything i can do to help, I don't know when I'm going to buy hardware as that depends on when I get money in my hobby fund. I'd love to help beta test and maybe it's about time i

Hi Matthew, I thought you might like to no that JMRI does not support dcc4pc railcom reader hardware at present and has not done so for the last three years, in fact I've loaded and run back releases

Try “Save Location and Size”. This was designed for this purpose. Sent from my iPhone - Dave

Terry, Please add how. Imagimne someone with the same problem, trying search term after search term, finally stumbling on this thread, looking in eager anticipation at the responses and only finding

Dave, thank you for this. ?Of course, i will need two turnouts. ?Silly me for not realising the obvious! Terry

Marc, They are one and the same for you. They are not one and the same for many users, particularly those using Dropbox/OneDrive or those sharing User Files Location between Simulator and Layout

Oh Billybob, sorry. Don't mind my last mail - the mails was late to me so I didn't see that the case has evolved further. Nice to see that you seem to understand what might be happening. Thanks,

There was a typo in a link making an image not appear. I have a fix for that going through the process. That section is new, and refers to as yet unreleased ( at least officially ) things the consist

Hej That log seems to have interesting info !?! To make the log clearer I took both logs and put them together sorted in time order. The lines in blue are from the log for the Z21 interface and lines

Thank You. ?I will download it...Frank

Billibob, OK, I went back and re-read the Z21 Documentation on this, and now I understand the problem. The A4 messages are supposed to be sent by the Z21 in response to LocoNet messages sent by

Paul, the example message you present would be valid (so long as the required "checksum" byte is added. Unfortunately, the log provided by Bosse includes some Z21 "A4" messages where the remainder of

Paul, All I am saying is that the passing logic will need to do something more than simply pass a bunch of bytes as a LocoNet message, because the bytes you seem to be planing to pass as a LocoNet

For what it's worth, the example message in the Z21's documentation is: 0x07 0x00 0xA4 0x00 0x81 0xF8 0x03 that makes the loconet message 0x81 0xF8 0x03. Paul

Be careful when interpreting the "track status" messages shown in the LocoNet slot data (and visualized in the LocoNet monitor). Some command stations provide erroneous information about track status,

Billlybob, Regardless of whether or not the LocoNet payload in the message is valid, the Z21's A4 opcode indicates the payload is a LocoNet Detection message and we aren't currently passing that to

Steve G, Strange, I've not heard of problems with using JMRI for control of the layout power. Yes, issues with the built in USB on the newer command stations. Do you have a GitHub issue id I should

Paul, Simply removing the first 4 bytes will NOT result in a valid LocoNet message! The first byte of a LocoNet message (the "OpCode" byte) _must_ have its most-significant bit set. Using your

<snip> I believe the problem is that messages like the ones above should be translated by the Z21 code into LocoNet messages, but that isn’t happening. The good news is that should be quick to fix

There are a number of issues around Digitrax track power that have not yet been resolved. The best advice is to ensure that track power is on before starting JMRI PanelPro or DecoderPro. And do not