开云体育

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Re: jynstrument error for USB throttle in 4.17.6 #scripting

 

Allen,

Great!

That change to the script is now in the main JMRI repository so will be correct in future releases.

Thanks for your help confirming this.

Best regards,

Matt H
Locked Re: jynstrument error for USB throttle in 4.17.6 #scripting

 

Matt,
That did it!
Thanks for the help,

Allen
Locked Re: speed matching

 

开云体育

Bachmann decoders are a good reason for using DecoderPro. It’s easy to get confused when manually programming these decoders, especially when dealing with CV29. Why? Because the NMRA, most books, and other manufacturers number the bits of a CV as 0-7, but Bachmann numbers them 1-8.

?

Mark Granville
Locked Re: Integrating JMRI to my MERG CBUS Layout #layouteditor

 

开云体育

Good evening Steve. I am going to have another marathon run tonight. I take your points but will read through them again carefully. I said to PeteB tonight, the help you all have given has been tremendous. I was not sticking with using Internal Turnouts but thought it was necessary because I could not establish what system names I should use for the turnouts. Pete pointed to 3 tools in JMRI that may help, CBUS Node Manager, CBUS Event Capture Tool to list 2. I shall play with these tonight.

Best wishes

Peter

From: jmriusers@groups.io <jmriusers@groups.io> On Behalf Of steve young via Groups.Io
Sent: 28 November 2019 23:44
To: jmriusers@groups.io
Subject: Re: [jmriusers] Integrating JMRI to my MERG CBUS Layout #panelpro #layouteditor

?

Hi Peter,

I'm still unsure as to why you're using Internal Turnouts rather than MERG CBUS Turnouts.

If you look at the JMRI CBUS Turnout Table, click on show Feedback Information.

If you now operate the Turnout via your non-JMRI panel, you'll notice that only the "Feedback" ( state ) is updated, not the ( commanded ) "State".
If you setup the Turnout as a CBUS Turnout, the ( commanded ) state will also update when the Turnout event is heard incoming to JMRI.

This also enables the physical Turnout to be set via clicking on the Layout Editor Panel or in the CBUS Turnout Table.
Your system will be a lot more in-sync if it knows there's a discrepancy between the Commanded and Feedback states.

There is absolutely no harm in JMRI knowing what the Commanded State is, so would recommend changing from Internal to CBUS Turnouts.
You don't HAVE to use JMRI for sending Turnout events, but if you did in future it's a lot easier to set it up now.

Consider the following CBUS events,

Event 1 is taught to operate a Servo
Event 2 is the Servo Closed Feedback Event
Event 3 is the Servo Thrown Feedack Event

23:39:39.252 JMRI < < CBUS | Short Event On EN:1 Command Turnout Thrown 23:39:39.334 JMRI < < CBUS | Short Event Off EN:2 Closed Off
23:39:41.531 JMRI < < CBUS | Short Event On EN:3 Thrown On
23:39:56.905 JMRI < < CBUS | Short Event Off EN:1 Command Turnout Closed 23:39:57.695 JMRI < < CBUS | Short Event Off EN:3 Thrown Off 23:39:59.896 JMRI < < CBUS | Short Event On EN:2 Closed On

In this common scenario, light the panel LEDs by teaching the LED module events 2 and 3.


If you require a single Sensor to trigger a Route, have you looked at Routes?


When the Route is confirmed with all Turnouts feedback set correctly, you can have Sensors / Turnouts triggered to illuminate LEDs on Control Panels.

These are a lot easier to configure than Logix imho!
As you are using Internal Turnouts, the commanded state would not be known, so you would not be able to trigger routes, only monitor them.

Routes can be also triggered on JMRI Startup, handy for sending a Start of Day CBUS Event when your panel has been initialised and tables loaded,

You could specify multiple SOD events with a time gap between them by selecting an additional delay between Turnout commands.

Steve.
Locked Re: Integrating JMRI to my MERG CBUS Layout #layouteditor

 

Hi Peter,

I'm still unsure as to why you're using Internal Turnouts rather than MERG CBUS Turnouts.

If you look at the JMRI CBUS Turnout Table, click on show Feedback Information.

If you now operate the Turnout via your non-JMRI panel, you'll notice that only the "Feedback" ( state ) is updated, not the ( commanded ) "State".
If you setup the Turnout as a CBUS Turnout, the ( commanded ) state will also update when the Turnout event is heard incoming to JMRI.

This also enables the physical Turnout to be set via clicking on the Layout Editor Panel or in the CBUS Turnout Table.
Your system will be a lot more in-sync if it knows there's a discrepancy between the Commanded and Feedback states.

There is absolutely no harm in JMRI knowing what the Commanded State is, so would recommend changing from Internal to CBUS Turnouts.
You don't HAVE to use JMRI for sending Turnout events, but if you did in future it's a lot easier to set it up now.

Consider the following CBUS events,

Event 1 is taught to operate a Servo
Event 2 is the Servo Closed Feedback Event
Event 3 is the Servo Thrown Feedack Event

23:39:39.252 JMRI < < CBUS | Short Event On EN:1 Command Turnout Thrown 23:39:39.334 JMRI < < CBUS | Short Event Off EN:2 Closed Off
23:39:41.531 JMRI < < CBUS | Short Event On EN:3 Thrown On
23:39:56.905 JMRI < < CBUS | Short Event Off EN:1 Command Turnout Closed 23:39:57.695 JMRI < < CBUS | Short Event Off EN:3 Thrown Off 23:39:59.896 JMRI < < CBUS | Short Event On EN:2 Closed On

In this common scenario, light the panel LEDs by teaching the LED module events 2 and 3.


If you require a single Sensor to trigger a Route, have you looked at Routes?


When the Route is confirmed with all Turnouts feedback set correctly, you can have Sensors / Turnouts triggered to illuminate LEDs on Control Panels.

These are a lot easier to configure than Logix imho!
As you are using Internal Turnouts, the commanded state would not be known, so you would not be able to trigger routes, only monitor them.

Routes can be also triggered on JMRI Startup, handy for sending a Start of Day CBUS Event when your panel has been initialised and tables loaded,

You could specify multiple SOD events with a time gap between them by selecting an additional delay between Turnout commands.

Steve.
Locked Re: ESU Select Question

 

That's the one.

Seriously, sometimes I don't know what or where I am.

John

---------- Original Message ----------
From: Dave Heap <dgheap@...>
Date: November 28, 2019 at 4:44 PM


Marc and John,

On 29 Nov 2019, at 9:36 AM, forfoum@... wrote:

On Thu, Nov 28, 2019 at 04:58 PM, John wrote:
In the files section there should be either a pdf or Word document listing
folks
willing to help other ESU users, someone may live close to you...make a new
friend?
Maybe in the ESU forum but not in here. I searched for it out of curiousity.
The list is in the Files section of the LokSound group, recently moved from
Yahoo to groups.io

Dave in Australia
Locked Re: ESU Select Question

 

开云体育

Marc and John,

On 29 Nov 2019, at 9:36 AM, forfoum@... wrote:

On Thu, Nov 28, 2019 at 04:58 PM, John wrote:
In the files section there should be either a pdf or Word document listing folks
willing to help other ESU users, someone may live close to you...make a new
friend?
Maybe in the ESU forum but not in here. I searched for it out of curiousity.

The list is in the Files section of the LokSound group, recently moved from Yahoo to

Dave in Australia
Locked Re: speed matching

forfoum@videotron.ca
 

I thought mallet sounded a little less violent : -)

Marc
Locked Re: ESU Select Question

forfoum@videotron.ca
 

On Thu, Nov 28, 2019 at 04:58 PM, John wrote:
In the files section there should be either a pdf or Word document listing folks
willing to help other ESU users, someone may live close to you...make a new
friend?
Maybe in the ESU forum but not in here. I searched for it out of curiousity.

Marc
Locked Re: ESU Select Question

 

Hello Brad,

There are Select micros and V4 micros but there are not Select V4 micros. The
Select line is a "dumbed down" version of the V4. The selct can only be loaded
with ESU sound files, with the V4 the modeller can make their own sound files
and load them into whatever sound slot they may desire.

To install the Full Throttle features you will need a LokProgrammer. In the
files section there should be either a pdf or Word document listing folks
willing to help other ESU users, someone may live close to you...make a new
friend?

ESU uses a proprietary communications method to talk to their decoders, Decoder
Pro can only manipulate CVs within the decoder, it cannot load sound files or
firmware updates into the decoder, again the LokProgrammer is required for this.

Hope this helps.

John

---------- Original Message ----------
From: "Brad Kobielusz via Groups.Io" <bkobielusz@...>
Date: November 28, 2019 at 1:42 PM



Hi all
I am have been looking into the possibility of using decoder pro to
upgrade Micro Select V4 decoders to the FUll Throttle version. My guess is
that it can’t be done I had considered trying to use a Full Throttle version
to clone to an older version with the same prime mover type. My guess is the
sound file is different enough that it needs a full new sound file loaded from
ESU. However knowing there are some pretty smart people on this list I
figured I would ask.
Thanks Brad
Locked Re: Webserver layout editor panel showing incorrect block occupation for a crossover

 

Andy, I'd suggest a new thread for the performance issue. Include details such as your OS, processor and amount of memory. I'd also include testing with a browser on the server machine.
--SteveT
Locked Re: Fatal crash - JMRI V 4.16

 

Hi John,

No need for a system log unless you spot another error !!.
Thanks for confirming sorted,

Steve.
Locked Re: speed matching

 

开云体育

PMSL

There is no engineering problem that cannot be resolved by the use of a bigger hammer!

Dave


On 28/11/2019 11:37, Dave Audley wrote:

I like the last sentence!
?
Dave Audley
?
From: forfoum@...
Sent: Wednesday, November 27, 2019 11:06 PM
To: jmriusers@groups.io
Subject: Re: [jmriusers] speed matching
?
Googlng, I came upon this instruction sheet for the Bachmann 36-550, 4 function decoder.

? :

Bit 5 of? CV29 must be set too enable " USER defined Speed table "?? When you go into DecoderPro and Bachmann 36-550, Speed Table Tab, you must select the? "Use Speed Table" button? so that CV29. bit 5? gets set to proper value. Fail to do this and the User Speed Table will have no effect.

If DecoderPro can not IDENTIFY the decoder and match it to an existing roster entry,? you have issues with your program setup or the decoder in question.
When you read CV7 and CV8? you should get? 46 and 101, which you are getting from somewhere.? These are also used by DecoderPro to match with the roster.?

If you are still unsuccessful, use Program on Main? and fire out the User Speed Table and? CV29 value to the decoder..

If this still does not work. Give up, give in,? Remove decoder and place on table. Take mallet in hand and " convince " the decoder.?

Marc

Locked Re: Decoder Pro & Tsunami Decoders #tsunami #pr3

 

PS
7 - and toggling back and forth unnecessarily on DecoderPro between Service mode programming(Programning track) and Programming on main subsequently to make more changes and test when toggling the DPDT switch was all that was needed.
Locked Re: ESU Select Question

 

Brad:

You need the ESU/Lok programmer to download the full project to a Lok decoder. Then you can program the CV with DecoderPro.

If your particular locomotive has an FT project, I think most (US) do.

If you don't have a programmer available check that the sound project you would want is available and let us know with an approximate location and if there's someone who might be able to help we might be able to put folks together.

Happy Thanksgiving!

Jim Albanowski
Locked Re: Decoder Pro & Tsunami Decoders #tsunami #pr3

 

Marc, Yes and no, both.

1 - Opening DecoderPro and setting it for Service mode programming.
2 - Opening the ROSTER entry for programming.
3 - Programming/Setting CV values.
4 - Issuing a Write changes to sheet, still getting 308.? Sheet write operations would come back 308 and change to red, even when the actual functionality became enabled upon testing with throttle.
5 - Toggling to Program on Main (Didn't need to do that, just needed to reset the DPDT to main track) - just needed to test with throttle with DPDT switch set to main and not reset to POM.
6 - Testing adjusted functionality and finding that values actually saved as expected, except on ditch light programming(multiple values had to be in sync, so had a conflict of two fx keys calling the same command, my fault. Now ditch lights are alternating).

So basically the programming is working, but I just tested again, by adjusting bulb brightness and although I received a 308 on Write, the change took.? Track was set to Service mode programming.? I can totally live with the 308, if somehow the decoder isn't acking properly.? If there's anything else I can try or adjust my sequence of operations, that would be great.

Thanks again for all of the assistance.? I've worked in support and I know that it can be "interesting".??

Russ
Locked Re: Fatal crash - JMRI V 4.16

 

Steve and Matt
That fix worked. After installing 3541 I opened PanelPro, Debug Message log and Script Output panel - NO FATAL ERROR.
I then opened my Layout panel and ran a script without problems and Quit. No Fatal Error here either.
I repeated that successfully, then re-instated my previous Users\name\JMRI set up and ran that, again with no problems.
I didn't load any updates later than 3541. However, that appears to have cured the problem.
Thank you both for your efforts.
(I presume Steve that it's not necessary to upload any System Log now)?
Regards
John
Locked ESU Select Question

 

Hi all
I am have been looking into the possibility of using decoder pro to upgrade Micro Select V4 decoders to the FUll Throttle version. My guess is that it can’t be done I had considered trying to use a Full Throttle version to clone to an older version with the same prime mover type. My guess is the sound file is different enough that it needs a full new sound file loaded from ESU. However knowing there are some pretty smart people on this list I figured I would ask.
Thanks Brad
Locked Re: speed matching

Dave Audley
 

开云体育

I like the last sentence!
?
Dave Audley
?

From: forfoum@...
Sent: Wednesday, November 27, 2019 11:06 PM
To: jmriusers@groups.io
Subject: Re: [jmriusers] speed matching
?
Googlng, I came upon this instruction sheet for the Bachmann 36-550, 4 function decoder.

https://www.toottoot.co.nz/downloads/files/Bachmann%2036550%20DCC%20Decoder.pdf? :

Bit 5 of? CV29 must be set too enable " USER defined Speed table "?? When you go into DecoderPro and Bachmann 36-550, Speed Table Tab, you must select the? "Use Speed Table" button? so that CV29. bit 5? gets set to proper value. Fail to do this and the User Speed Table will have no effect.

If DecoderPro can not IDENTIFY the decoder and match it to an existing roster entry,? you have issues with your program setup or the decoder in question.
When you read CV7 and CV8? you should get? 46 and 101, which you are getting from somewhere.? These are also used by DecoderPro to match with the roster.?

If you are still unsuccessful, use Program on Main? and fire out the User Speed Table and? CV29 value to the decoder..

If this still does not work. Give up, give in,? Remove decoder and place on table. Take mallet in hand and " convince " the decoder.?

Marc

Locked Re: DC Occupancy Detectors for Signal Systems?

 

Nick, Keith, Thomas, Dick, Steve, GoeffB -- so far:

I greatly appreciate you all taking the time to respond -- it has been very helpful.? As they say, I didn't know what I didn't know.? And I've now got a lot more information and options than I had before.? Much more exploring ahead!

Many thanks,

Hilary Smith?
Pacific NW USA
73761 - 73780 of 239631