开云体育

Hi Hal, Bob's tutorials are the best and I have used them often when I need to learn something new. I think what you are missing is the signals are not identified for their physical location . Think

Hal, Do not be fooled into thinking that SSL is simpler than aspect based signaling. It most definitely is not. The 'Simple' in the name means Simplistic, not easy. You wind up having to do strange

The program calculates how many lines should fit.? Could you try printing to a pdf file and see if all of the lines are there?? Seems like a printer issue. Dan

I have my Manifests ready to print. ?First I want to print my CAR FILE. ?When I do print the car file (or my manifests) the page layout is larger than a normal page of printing and I lose the last

Jacques, The same OpSw 36 problem has been around since DCS 100/200 and our club has been working on that issue for several years. With a lot of help from Billybob and several other members on this

Thanks all for the clarifications. I'll try to digest it all (with a Tums or two), but for now, since I'm just starting with signalling, I think I'm gong back to SSL and signal heads. Thanks again!

Hello all. I'm trying to figure out how to use signal heads and SSL and am finding Robert Bucklew's tutorial 3 (

Billybob, This issue should now be fixed. Thanks for raising it. Best regards, Matt H

Petr, This issue should now be resolved - can you verify? Thanks. Best regards, Matt H

14 -> 27 and 28 -> 55 were Ugly Hacks built into some early command stations. Basically, the command station would rapidly switch back and forth between step N and N+1 to _effectively_ have step

55?? That's a new one on me!

My current theory revolves around 28/128 steps. For the problematic LE103 decoders: What happens if the EasyDCC throttle is changed to 128 steps ? Can the EasyDCC throttle now control the LE103 ? If

Hi Don, Both things I mentioned (speed values 0 and momentum huge) are pretty long shots more in desperation than anything else. Somewhere along the line I have confused issues in my mind - I thought

wouter, No, I haven't checked the JMRI speed table for this decoder recently. With EasyDCC I do normally have a start voltage set, and mid and full speed, often evenly divided with full speed at 100%.

Marc, CV1 and CV 66 are both short addresses. With that configuration, the only way to make the loco move is to send short address 66 speed packets. Having a non-zero CV19 overrides anything in CVs 1,

This is thought to be an unwanted side-effect of migrating the JMRI site to https: https://github.com/JMRI/website/issues/329 Bob -- Bob Jacobsen rgj1927@...

Conrad, I think that the loco decoder and VSD are in sync when the HALF_SPEED key is switched and the loco is not running. Prerequisite: the basic acceleration and deceleration times of the loco

Lately there is a strange message in the *Apperance table* for example https://www.jmri.org/xml/signals/AAR-1946/appearance-SL-3-high.xml *Error: This appearance does not appear in the aspect table.

PS: also a huge acceleration momentum value combined with a lack of patience can make it seem like a loco does nothing. Yes, the words 'clutching' and 'straws' may well spring to mind.

Hi Don, Have you checked the values of the speed table and of Vstart, Vmid and Vmax? If those were inadvertently all zero... Not likely, I'll readily admit, but as you're running out of likely things