|
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 image in the command station is ok. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
|
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 prior answer. It isn't doing retries from JMRI. Something in the command station is being really slow. Any chance of dirty track or wheels? The CV says that's a Heller decoder. And it read the long address, so that's the mode it is using. I've got no idea except something odd in the command station would cause it to take so long to reply to each command from JMRI. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
|
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 crashing on you. Unfortunately, there¡¯s only a little DCC++ expertise here; only a small number of JMRI users have DCC++ command stations, and many of them are beginners at all of this. If there was a DCC++ list, that might be a better place to get things like this sorted out. Bob -- Bob Jacobsen jacobsen@... +1-510-708-5988 AIM, Skype JacobsenRG |
|
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
16:34:56.256:? Prog Read Cmd:?
CV: 17
Callback Num: 0
Callback Sub: 82
16:36:26.250:? Prog Read Cmd:?
CV: 17
Callback Num: 0
Callback Sub: 82
16:36:27.469:? Program Reply:?
Callback Num: 0
Callback Sub: 82
CV: 17
Value: 192
16:36:27.500:? Prog Read Cmd:?
CV: 18
Callback Num: 0
Callback Sub: 82
16:37:57.486:? Prog Read Cmd:?
CV: 18
Callback Num: 0
Callback Sub: 82
16:37:58.720:? Program Reply:?
Callback Num: 0
Callback Sub: 82
CV: 18
Value: 218
16:37:58.736:? Prog Read Cmd:?
CV: 7
Callback Num: 0
Callback Sub: 82
16:39:28.736:? Prog Read Cmd:?
CV: 7
Callback Num: 0
Callback Sub: 82
16:39:29.986:? Program Reply:?
Callback Num: 0
Callback Sub: 82
CV: 7
Value: 43
16:39:30.001:? Prog Read Cmd:?
CV: 8
Callback Num: 0
Callback Sub: 82
16:40:59.998:? Prog Read Cmd:?
CV: 8
Callback Num: 0
Callback Sub: 82
16:41:01.248:? Program Reply:?
Callback Num: 0
Callback Sub: 82
CV: 8
Value: 151
? |
|
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: stopping due to error: time exceeded for communication with the dcc control panel (306)
Direct Byte or Direct bit it's the same I will test again with Connection monitor, I come back. thank's |
|
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 going on. Also other errors might be showing up in the system console. So open that (Help->System Console) too. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Six minutes sounds very long.
What¡¯s the status line showing while that¡¯s happening? Is it retrying a read multiple times? What programming mode are you using? Bob On May 28, 2019, at 6:33 AM, fcot2002@... wrote:-- Bob Jacobsen rgj1927@... |
|
Locked
DECODERPRO VERY LONG IDENTIFICATION TIME
Hello @ all,
In recent days the time to identify a locomotive with Decoder Pro has become extremely long. About 6 minutes.?Before that was going much faster.
?
I came back to an earlier version of JMRI, no change.
?
Here is the description of my system: Digital Central: DCC++
JMRI: 4.14+Rd060e0b
Java: 1.8.0_211
PC with W10 family 1809 version: 17763.503
Proc: Intel Intel Core I3 5005U 2.00GHZ
RAM: 4Go / 3.87Go free
|
FCOT2002
Ken Cameron
Bob Jacobsen