开云体育

Paul, I would appreciate it if you could point out where in the documentation it makes the distinction about the pre and post amble bytes. I could never find it in the english documentation and I even

Sorry for the trouble. The details matter a lot in this kind of thing. It’s hard to talk through specific errors over email. If you put a copy of the file in the files area of the group (

Michael, No, you are confusing things here. The original LIUSB is a USB only device. It shipped with a server that allowed talking to it via a TCP/IP socket connection ( note that a TCP/IP socket does

Since you are also seeing: The messages you marked indicate you don't have the same stem configured right. In fact, this message ( which I have re-ordered, but appears before the one above ): Tells me

I have had problems since intalling test version previous to, and now 4.7.7+R177ca31 with failure to parse my layout. Initially I had numerous 'comment/' but no previous 'comment' which I deleted, and

Hi Egbert Thanks for your explanation. It has at least shown that I don't have to start over again defining a panel but I am somewhat uninspired at the amount of work that needs to be done still to

What do the 2; triple starred warning message mean to my system 2017-07-10 19:15:55,477 util.Log4JUtil INFO - * JMRI log ** [main] 2017-07-10 19:15:56,463 util.Log4JUtil INFO - This log is

I have been following this discussion with much interest as I have a Lenz system and will be using the LIUSB 'ethernet' connection when I finally get my household goods shipment. The ethernet

Paul; when I switch to LIUSB when the program opens up; the power button shows unknown & I have no control over it. I can't turn it on or off!

I did some work on the flow control entry and that was set to active. Changed it to no flow control, restarted the pc and JMRI and everything worked. That has been something I never has touched for

<jmriusers@...> wrote: If you are trying to actually communicate with your LIUSB, then the line above needs to change to LIUSB. You have currently told JMRI to simulate a layout connection

I am using version 4.7.4+Re0b7c98 with a 23151 LI USB My preferences are such Connections; top line XPressnet System manufacturer Lenz Connection XPressnet Simulator Settings Connection Prefix X

Dear Ken, Thanks for this. I will locate that code and have a look. Dave Price

Dear Ken, Thanks for looking into this - much appreciated. I suspected something like that but I had not had a chance to examine the code myself in detail. Dave Price

Dap, I just did a test of creating a simulator DCC++ system and I get both a DCCPPS0 and DCCPPS1 sensor showing in the table. So there were created by the startup of the system. It looks like a coding

Dave P, Automation is quite possible but simplest if you are all automated for a train. Passing between humans doing things and the computer doing things is the hard part. Biggest issue is keeping

Thanks Guys Opted to try MX622N and panic over as it worked a treat! Ray

Dear All, I forgot to say, some crude photos, one from each end, are in Photos -> Dave Price I do have extra sensors next to decouplers and I also have turnouts of course.

Dear All, I have a small shunting yard (originally inspired by the Inglenook Sidings shunting puzzle) which I am trying to use as a basis for some student computing/control projects. I have custom

Dear All, I have swapped to 4.7.7 and my previous reports of XML validation errors have ceased - great. However, another problem persists (and I had this with earlier versions of JMRI as well). The