Hi Bob, thanks for answer.
That's what I originally set out to do last summer, before getting
distracted by a bunch of other uses. The program now has some
limited capabilities to do that; it can throw and track turnouts,
animate a little track plan as things change, etc. But it will
probably never be in the same "point&click" league as the commercial
products such as WinLok and RR&Co; it's more aimed at being a library
you can use to write your own programs more easily.<
OK, and what about monitoring of track/block occupation (from
detectors)?
That's part of it. It turns out that's a little more complicated than throwing turnouts, as there are _lots_ of different ways that information comes into the system. So the basic code has to be pretty flexible.
>>What practically mean your plan "Lenz XpressNet support to JMRI"?<<
First, make it possible for DecoderPro to program decoders with an
XpressNet command station (Lenz or Atlas Commander) via a LI100
interface. Then add turnout control, throttles, etc.<
I am not sure, but XpressNet and Li(F)100 with PC communication is
separate and different things (programs, protocols...)?
The XpressNet itself is not something that can be easily done with a PC serial port. It requires some timing & bit-banging that's beyond my capabilities. So the first thing I'm working on for Lenz command stations is communication through a LI100. The messages are pretty-much the same as XpressNet itself, but the serial port control is much simpler.
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
Bob Jacobsen