Locked
Re: JMRI Operations : "Mole Yard"
Mike this stupid box won't let me follow the email addy my addy is cascaderwy@... Matt
By
cascaderwy
·
#160279
·
|
Locked
Re: JMRI Operations : "Mole Yard"
Matt, My email is mkisser@... let¡¯s take this off line. I am glad to share more of what I have done. Maby we can work together to help each other out. Mike
By
Michael Kisser
·
#160278
·
|
Locked
Re: JMRI Operations : "Mole Yard"
Thanks Mike, So there are 2 double ended tracks for trains, 7 single ended tracks for car storage, and then an actual loco and caboose tracks the number doesn't matter as long as they will hold the
By
cascaderwy
·
#160277
·
|
Locked
Re: Train print/export enhancement request
#operationspro
Hi Jon, Try looking at the operation train xml file (OperationsTrainRoster.xml).? It contains everything about each train. Dan
By
Dan Boudreau
·
#160276
·
|
Locked
Re: DS51K1 turnout decoder - detection
Rizwan: A good resource for sorting out how Kato turnouts work electrically is Alan Gartner's http://www.wiringfordcc.com/switches_kato.htm. The discussion is around a turnout being "DCC friendly"
By
Jan Carr
·
#160275
·
|
Locked
Re: JMRI Operations : "Mole Yard"
Sorry I think I missed an earlier email. Which prototype Mole is this about? Andy
By
Andy Reichert
·
#160274
·
|
Locked
Re: JMRI Operations : "Mole Yard"
Hi Matt, I took my ¡°mole Yard¡± and split it in half and changed the tracks to ¡°Spurs¡± and that got me a working solution I think. Q1 = Yes Except for the A/D tracks. Q2 = 7 total. Q3 = There
By
Michael Kisser
·
#160273
·
|
Locked
Re: JMRI Operations : "Mole Yard"
Hi Mike, Couple of questions. 1) All tracks in Mole are single ended? 2)How many tracks in mole yard? 3)Do you have paper or real loco and caboose tracks at mole? 4) could you give me the names you
By
cascaderwy
·
#160272
·
|
Locked
Re: DS51K1 turnout decoder - detection
Jim¡¯s explanation makes sense, and looking closer at the picture I think he¡¯s right. So, move the red + black leads along the turnout to the right hand end of the moving switch parts. One tip for
By
Nigel Cliffe
·
#160271
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
There was no change to the station and DCC ++ code. The station had been working properly since last November, CV reading and identification was fast.
By
FCOT2002
·
#160270
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Could it be something like a debug mode left on in the command station and its sending messages out another port? Waiting for an answer there and timing out? That would be my guess, presuming there
By
Ken Cameron
·
#160269
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Yes I also think that the problem comes from the station. The rail and wheels are clean ;-)
By
FCOT2002
·
#160268
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Wow! That command trace says the delay is all something in the command station. If you pair the commands, you would see that JMRI is asking for the next CV within 100mS or less from receiving the
By
Ken Cameron
·
#160267
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Bob: Seems there is on Facebook groups... Quick read of first several posts isn't "expert..." I've built a test rig for our club based on Steve Todd's RPi-JMRI plus the DCC++ command station... No
By
jimalbanowski
·
#160266
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
There are some forums / groups DCC ++, but not found that kind of problem. As I have another arduino I will test to see if it does not come from the card itself.
By
FCOT2002
·
#160265
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Is there a DCC++ support list somewhere? We¡¯re seeing more and more reports of odd (i.e. not good) behavior of DCC++ command stations. This is an example: It looks like the DCC++ command station is
By
Bob Jacobsen
·
#160264
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
monitor connection console result 16:34:55.006:? Prog Read Cmd: CV: 29 Callback Num: 0 Callback Sub: 82 16:34:56.240:? Program Reply: Callback Num: 0 Callback Sub: 82 CV: 29 Value: 39
By
FCOT2002
·
#160263
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Hello All, @ John I said that I had no problem with my locomotives before the last days. The decoders are for example:?Laisdcc86010?or?LokPilot v3.0 dcc @Ken Bob Error message: Decoderpro status:
By
FCOT2002
·
#160262
·
|
Locked
Re: Web Server / Operations Internal Server Error
#operationspro
Randall, This has been done. Sam
By
Sam Simons
·
#160261
·
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Fcot, I'd suggest that you open the connection monitor (DCC++->Traffic Monitor) to trace the traffic between JMRI and the command station. That will show if it is doing a bunch of retries or what it
By
Ken Cameron
·
#160260
·
|