¿ªÔÆÌåÓý

Locked Re: XpressNet Session Log errors


 

¿ªÔÆÌåÓý

Paul,

As you were. Slight hitch in link. Clicked it and noted that (.) missing ...jmri.tagadab....in URL address bar in browser.

Sorted. Will look at it a little later and let you know.

Cheers

Tom

On 05/01/2019 14:21, Paul Bender wrote:

Tom,

I think I have this fixed, at least I no longer see the error with an Atlas Commander connected to JMRI.

When you get a chance, please download a daily build from


To confirm you no longer see it either.

Thanks!

Paul


On Dec 28, 2018, at 3:43 AM, Tom Busza via Groups.Io <tombee50@...> wrote:

Many thanks Paul, I look forward to the fix.

Meantime Happy New Year to one and all.

Tom

On 28/12/2018 07:08, Paul Bender wrote:

On Dec 25, 2018, at 3:25 PM, Tom Busza via Groups.Io <tombee50@...> wrote:

I am just intrigued why this is happening.

The annoying part is that when I open JMRI, I have to wait for JMRI to check things, give me an error message:

System connection XpressNet provides a null manager for interface CommandStation Unable to to run startup due to earlier failures.?? Please check logs for more details. The Preferences window will open so this can be fixed.

This happens because you are using a Compact which doesn¡¯t provide support for sending raw packets to the rails.

BUT you shouldn¡¯t get this Error message because the command station option should be disabled when the compact is connected.

I¡¯ll pull out an Atlas Commander (rebadged Compact ) so I can replicate the issue and fix it. ?This might take me a few days however.

Paul


Virus-free.

Join [email protected] to automatically receive all group messages.