开云体育

Hello All.

I am receiving Packet Delays and Timeouts in the System Console between JMRI 4.12 and SPROG3. Can't figure it. After a while, JMRI pops up a window telling me it has turned off power due to timeout with command.?

- JMRI startup is clean. Auto-starting WiThrottle. No errors. Will sit idle for hours. (I let it sit overnight, idle after a fresh boot - no issues, no new messages)
- As soon as any message is sent from any throttle, packet delays start. (Not just WiThrottle.. can be power on/off from any JMRI panel or a JMRI Throttle)
- Does NOT matter if connected to track or not.?
- I have switched USB Ports
- I have changed USB cables
- I reverted back to 4.8 and this does NOT happen. There are actual, serious delays.. but no reports in Console or power off.

I'm at a loss.. anyone else seeing this?

--
RockPro - San Diego, CA
Raspi2 B+,?SPROG3, LocoBuffer USB, BDL168 & 10 switches on a 4x8

Hi, I am seeing the same issue with the Pi-SPROG one and? raspberry pi 3b. Unfortunately I have not had time to start to look at why yet and am not sure where to start. Can someone point me in the right direction?

I have noticed that after a fresh start.. with or without reboot of Pi.. I have to switch track power off/on at least once before any throttle data is actually at the rails.. even though power is on at startup configuration.?

Thinking all this might be endemic to some of the other warnings and things we see with SPROG-Pi and SPROG-1. Our SPROG3''s might also be affected.


--
RockPro - San Diego, CA
Raspi2 B+,?SPROG3, LocoBuffer USB, BDL168 & 10 switches on a 4x8

Same here.?? Pi-Sprog (just got it the other day).??? Using Steve Todd's image on a Raspberry 3 B+.?? Everything works great except track power goes off automatically goes off randomly for no apparent reason, especially when programming locos.?? Have to check the Power Control applet all the time to ensure track power is really on or not.

More of an annoyance than anything else.?? Happy with the purchase and glad that I don't need to mess with service mode programming using the Digitrax DCC system ayout any longer.??

Hi All,

No Sprog hardware but in an earlier message Rockpro says "Thinking all this might be endemic to some of the other warnings and things".

What warnings are these?

Is there any weird activity in the main JMRI console when this behaviour occurs?
If so, please post here, would make it much easier for people to track down issues,

Steve.

This is how SPROG in programming mode works. When you are programming (Read or Write) track power is OFF and you are using the programming track power levels. The whole layout/track you are linked to.?
When you open a throttle, the track power goes ON, and you can use the (single) throttle to test your settings.
SPROG in Operation mode has power ON, unless you switch to programming, when the power goes off, and you are in programming mode with lower track power etc.

Check the preferences for the mode you are using.
I generally set Decoder Pro to SPROG (Programming) and Panel Pro to SPROG Command (Operating) to avoid confusion. Then open DP to program, or PP to run.

Hi, maybe i am not understanding this but? I am using command station and turn on a throttle and almost immediately get

2018-12-06 09:21:52,183 PanelPro.PanelPro???????????????????? INFO? - Main initialization done [main]
2018-12-06 09:22:49,352 sprog.SprogCommandStation???????????? WARN? - Packet delay was 180 ms [SPROG slot thread]
2018-12-06 09:22:53,782 sprog.SprogCommandStation???????????? WARN? - Packet delay was 83 ms [SPROG slot thread]
2018-12-06 09:22:58,736 sprog.SprogCommandStation???????????? WARN? - Packet delay was 79 ms [SPROG slot thread]


Is this OK?

Same for me.. definitely not ok or normal. Eventually the delays get so bad it shuts down.


--
RockPro - San Diego, CA
Raspi2 B+,?SPROG3, BDL168 & 10 switches on a 4x8

Hi,

I have seen a similar problem with Pi-SPROGs connected to the R-Pi which I thought were fixed in 4.12, with some workarounds which are listed in the release notes. I have not been aware of it happening with USB SPROGs connecteed to a Pi.

Can you tell me:
What Raspbian version?
What other JMRI windows do you have open?
Does the problem still occur if the SPROG Console and the JMRI console are NOT open (the release notes say to not open them).
Do you have any debug enabled in default.lcf (probably not of you do not know what that means).
Is operation OK immediately after startup?
Do you know how long you can let it sit idle before the problem starts?

The theory is that he flash file system on the Pi is too slow, and affects the serial comms, when any of the log files get too large.

Andrew

Another point: The Steve Todd image alone may not be suitable for the Pi-SPROG. The SPROG DCC image applies the miniuart-bt-overlay which may affect the serial comms.

Hi on my system ...

Pi version

? PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
? NAME="Raspbian GNU/Linux"
? VERSION_ID="9"
? VERSION="9 (stretch)"
? ID=raspbian
? ID_LIKE=debian
? HOME_URL="http://www.raspbian.org/"
? SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
? BUG_REPORT_URL=

The only windows I have open are the PanelPro main window and the throttle window.

The SPROG console is not opened. I see the messages when logged on to the Raspberry Pi.

Do you have any debug enabled in default.lcf (probably not of you do not know what that means). - Do not belive so

Is operation OK immediately after startup? – yes

Do you know how long you can let it sit idle before the problem starts?

?

With PanelPro main window open and throttle window open and power Unknown – sits forever ok.

Turn power to Off – sits forever OK

Turn power on -? 10-15 seconds and then warning messages start, and are issued every 8 seconds.

?overlay in /boot/config.txt

? dtoverlay=pi3-miniuart-bt-overlay
? enable_uart=1

Thanks Jim.

Thanks. I should also have asked, what firmware version is the Pi-SPROG? You can obtain this in the SPROG menu.

Andrew

Hi, version 2.3

Hi James,

Are you suffering the same sluggish response as 'rockpro', or just seeing the WARN messages?

The WARN messages you show below only seem to be every few seconds in your listing. If this is the only symptom and everything is otherwise working then you can ignore these messages.

If you are experiencing sluggish response please try closing the console window (wheer you see the WARN messages). Does it make a difference?

Andrew Crosland
SPROG DCC

Hi, response for me seems to be OK, just the WARN messages popping up every 8/9 seconds.

On Fri, Dec 14, 2018 at 08:44 AM, James Anderson wrote:

Hi, response for me seems to be OK, just the WARN messages popping up every 8/9 seconds.

Thanks. It is working as expected in your case. As I said, I think the R-Pi becomes unresponsive at times. i have seen similar issue with Flash file systems on embedded hardware.

Andrew

Thanks for looking at this.

Hi all! I've been a long time Sprog user and joined to answer this question that has been driving me crazy. In JMRI, select SPROG Programmer from the menu and select Sprog Console. Under "Configuration", find SPROG Throttle Speed Step Mode. Click on 128 step (it may already be selected) and click on Apply.

Hope that helps someone!

Scott