|
I just upgraded my JMRI to 4.13.6, and I can¡¯t now get it to write indexed CVS in a Soundtraxx ECO-100 UK decoder. ?Non indexed CVS are ok, but as soon as it hits an indexed one I get first a 308 error and then a JMRI programmer in use error (not the 302 system programmer in use error), and the console shows a stack trace.
I¡¯ve localised it to Digitrax support. ?I¡¯ve tried connecting the DCS240 as both DCS240 and DCS100 with the same result, all via a LocobufferUSB. ? I can successfully write al the CVS to the loco with a SPROG, so the loco and decoder are not at fault.
I think this is a new issue with 4.13.6, as I don¡¯t recall having similar issues with 4.13.5. I have to go out now, but will be back in a few hours. ?I can try again then and post console info, anything else required?
Mick Moignard
________________________________
Mick Moignard
m: +44 7774 652504
Skype: mickmoignard
, so please excuse the typos.
|
Mick
I had this six months ago - ended up totally deleting Java and
loading a fresh download of Java.
Worked OK ever since then.
Gerry
On 11/12/2018 9:47 pm, Mick Moignard
wrote:
I just upgraded my
JMRI to 4.13.6, and I can¡¯t now get it to write indexed CVS in
a Soundtraxx ECO-100 UK decoder. ?Non indexed CVS are ok, but
as soon as it hits an indexed one I get first a 308 error and
then a JMRI programmer in use error (not the 302 system
programmer in use error), and the console shows a stack trace.
I¡¯ve
localised it to Digitrax support. ?I¡¯ve tried connecting the
DCS240 as both DCS240 and DCS100 with the same result, all via
a LocobufferUSB. ? I can successfully write al the CVS to the
loco with a SPROG, so the loco and decoder are not at fault.
I think
this is a new issue with 4.13.6, as I don¡¯t recall having
similar issues with 4.13.5. I have to go out now, but will be
back in a few hours. ?I can try again then and post console
info, anything else required?
Mick
Moignard
________________________________
Mick
Moignard
m: +44
7774 652504
Skype:
mickmoignard
, so
please excuse the typos.
--
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder
NMRA Australasian Region
Contest & AP Chairman
Web Administrator
|
Sorry for the trouble, and thanks for your efforts to track this down. Could you post the stack trace you¡¯re seeing please? Bob On Dec 11, 2018, at 2:47 AM, Mick Moignard <mick@...> wrote:
I just upgraded my JMRI to 4.13.6, and I can¡¯t now get it to write indexed CVS in a Soundtraxx ECO-100 UK decoder. Non indexed CVS are ok, but as soon as it hits an indexed one I get first a 308 error and then a JMRI programmer in use error (not the 302 system programmer in use error), and the console shows a stack trace.
I¡¯ve localised it to Digitrax support. I¡¯ve tried connecting the DCS240 as both DCS240 and DCS100 with the same result, all via a LocobufferUSB. I can successfully write al the CVS to the loco with a SPROG, so the loco and decoder are not at fault.
I think this is a new issue with 4.13.6, as I don¡¯t recall having similar issues with 4.13.5. I have to go out now, but will be back in a few hours. I can try again then and post console info, anything else required? -- Bob Jacobsen rgj1927@...
|
There's a known issue with the possibility of "Programmer in Use" if you Write All Sheets on any pane rather than Write Full Sheet on the CVs pane. This has been around for along time and is not yet resolved.
--
Dave in Australia
toggle quoted message
Show quoted text
On 11 Dec 2018, at 9:47 PM, Mick Moignard <mick@...> wrote:
I just upgraded my JMRI to 4.13.6, and I can¡¯t now get it to write indexed CVS in a Soundtraxx ECO-100 UK decoder. Non indexed CVS are ok, but as soon as it hits an indexed one I get first a 308 error and then a JMRI programmer in use error (not the 302 system programmer in use error), and the console shows a stack trace.
I¡¯ve localised it to Digitrax support. I¡¯ve tried connecting the DCS240 as both DCS240 and DCS100 with the same result, all via a LocobufferUSB. I can successfully write al the CVS to the loco with a SPROG, so the loco and decoder are not at fault.
|
Dave: I think I used write Full sheet and write changes on sheet on the CV pane because I'm aware of this issue, and it still borked on me.? I also noted that while I had JMRI working in Direct Byte mode, Loconet monitor said that the commands were being done in Page mode.? I also got issues with writes from the CV pane when in Ops mode and also with single CVs.??
I'm just about to post some logs... .
Mick
|
Log files in Problemsbeingworkedon/Mik Moignard DCS240 JMRI 4.13.6 and Indexed Cvs
|
Thanks for uploading those logs. Could you try something for me? Open JMRI, open Preferences, select the Roster pane, then _unselect_ (no checkmark) ¡°Allow caching when writing index CVs for read or write operations¡±, save and restart. It¡¯ll be helpful to know if that makes the problem change or perhaps even go away. Bob On Dec 11, 2018, at 2:47 AM, Mick Moignard <mick@...> wrote:
I just upgraded my JMRI to 4.13.6, and I can¡¯t now get it to write indexed CVS in a Soundtraxx ECO-100 UK decoder. Non indexed CVS are ok, but as soon as it hits an indexed one I get first a 308 error and then a JMRI programmer in use error (not the 302 system programmer in use error), and the console shows a stack trace.
I¡¯ve localised it to Digitrax support. I¡¯ve tried connecting the DCS240 as both DCS240 and DCS100 with the same result, all via a LocobufferUSB. I can successfully write al the CVS to the loco with a SPROG, so the loco and decoder are not at fault.
I think this is a new issue with 4.13.6, as I don¡¯t recall having similar issues with 4.13.5. I have to go out now, but will be back in a few hours. I can try again then and post console info, anything else required?
Mick Moignard
-- Bob Jacobsen rgj1927@...
|
Bob
Done that: tests
with Allow caching when writing index CVs for read or write operations
unchecked. ?I've added two files about it to the folder in ProblemsBeingWorkedon.
One is a Loconet log file and the other is some text and screenshots. ?It
notes specifically two things:
- JMRI working
in Page mode when the setup request Direct Byte mode
- the fact that
the command station is a DCS240, which I know from experience is flaky
in Page mode, and that I've used DP 4.13.6 - same computer, too - with
a genuine DCS100 to program an ESU L4 ?in Ops mode with no issues.
Mick
______________________________________________________________________
Mick Moignard
Specialising in DCC Sound
p: +44 7774 652504
e: mick@...
skype: mickmoignard
IBM
Notes and Domino: still has what it takes as an App Dev and Collaboration
platform.
|
Thanks for all the effort on this. One problem with indexed writes did show up, and that will be fixed shortly. I think you could be seeing issues in the DCS240, either that one in particular or more generally. You mentioned testing with a DCS100 and JMRI 4.13.5 which went OK. That might point to the problem being the DCS240 command station, which would be good to know. But it might also be something new in JMRI 4.13.6 There were some changes in this area, though they weren¡¯t expected to make trouble like this. Is there any chance you could try the DCS100 with JMRI 4.13.6? Thanks again. Bob On Dec 13, 2018, at 6:43 AM, Mick Moignard <mick@...> wrote:
Bob
Done that: tests with Allow caching when writing index CVs for read or write operations unchecked. I've added two files about it to the folder in ProblemsBeingWorkedon. One is a Loconet log file and the other is some text and screenshots. It notes specifically two things:
- JMRI working in Page mode when the setup request Direct Byte mode
- the fact that the command station is a DCS240, which I know from experience is flaky in Page mode, and that I've used DP 4.13.6 - same computer, too - with a genuine DCS100 to program an ESU L4 in Ops mode with no issues.
Mick
______________________________________________________________________
Mick Moignard
Specialising in DCC Sound
p: +44 7774 652504
e: mick@...
skype: mickmoignard
IBM Notes and Domino: still has what it takes as an App Dev and Collaboration platform.
-- Bob Jacobsen rgj1927@...
|
I did try 4.13.6 with the DCS100 and the Loksound decoder, and all was fine, but that was on ops mode only. ?I can try it in service track mode, too.
Mick
________________________________
Mick Moignard
m: +44 7774 652504
Skype: mickmoignard
, so please excuse the typos.
|
I¡¯ve tried some stuff with the DCS100 and 4.13.6
1 ?Soundtraxx Eco-21PNEM Uk steam, program track write full sheet from the CV pane. No errors noted, but DP is using Page mode according to the Loconet monitor, when the mode selector on the foot of the page says Direct Byte.
2. ESU Loksound 4, program track write full sheet from the CV pane. Again, while the ?CV pane showed Direct Byte as the mode, Loconet monitor said it was doing it in Page mode. ?No errors.
So the DCS240 would seem to be a chunk of the issue, however the defect where DP is doing stuff in Page mode when commanded to use Direct Byte could well be apiece of it too, given that I¡¯m aware that the DCS240 is less than reliable using Page mode.
Mick
________________________________
Mick Moignard
m: +44 7774 652504
Skype: mickmoignard
, so please excuse the typos.
|
Bob Jacobsen