Locked
Re: JMRI for dispatching
Thanks for the reply.?
No, JMRI will not be sensing the layout, and I understand the concept of the simulator interface.
It's just that I'm getting confused with Logix etc, and am looking for some "guidance" through the set up process.
I can draw a schematic of the track, add turnouts, add sensors and memory variables, but I'm getting lost from there.
Are there any tutorials, step by step guides you can recommend I watch / read? Really appreciated you help.
John
|
Locked
Re: DECODERPRO VERY LONG IDENTIFICATION TIME
Good evening Jim,
?
So I just re-check everything, I switched to fixed IP on the Mega and the PC, then in DHCP on the Mega and the PC ...
?
Same result 5 to 6 minutes to identify a locomotive.
?
Next test: replace the switch
?
Thanks everyone
|
Yup, but they wouldn't look anything like modeled switch stands, or their scale size. Andy On 6/6/2019 8:28 AM, Larry Sloan via Groups.Io wrote: For that matter, I could pick up some ground throws and not use any of this stuff at all. ?*wink*
Larry Sloan --- This email has been checked for viruses by AVG.
|
For that matter, I could pick up some ground throws and not use any of this stuff at all. ?*wink*
toggle quoted message
Show quoted text
On Jun 6, 2019, at 6:40 AM, Andy Reichert < andy_r@...> wrote:
Why use any toggle switches to set turnouts at all? . Touch or mechanical). You are relying on being able to clearly see (or know) all the relevant turnout settings immediately prior. Which is not always obvious. If you want touch panel switches, just have separate closed and thrown ones. then you won't accidentally change a correctly set turnout.
Andy
|
Why use any toggle switches to set turnouts at all? . Touch or mechanical). You are relying on being able to clearly see (or know) all the relevant turnout settings immediately prior. Which is not always obvious. If you want touch panel switches, just have separate closed and thrown ones. then you won't accidentally change a correctly set turnout. Andy On 6/5/2019 10:44 PM, Larry Sloan via Groups.Io wrote: I will have to check out the Monitoring thing. Doing what I mentioned doing I was able to get all the routes I wanted to create (so far) working. With that done, my next step will be to use Touch Toggles on the panel that will control the yard.
Larry Sloan
On Jun 5, 2019, at 8:30 PM, Ken Cameron <kcameron@...> wrote:
Larry,
Focus on getting the turnouts working right from the turnout table first.
Each turnout is a pair of events, thrown/closed. The feedback is normally
MONITORING. Once that is correct, then the Routes would be a route has one
or more turnouts, each turnout is selected to be thrown or closed. Keep in
mind for a given route you may have one to N turnouts in that path, you set
what they need for direction. Other turnouts are not included in the route.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org --- This email has been checked for viruses by AVG.
|
Locked
Re: JMRI for dispatching
John,
When you say 'not connected', do you mean to develop a panel or for the
operating it? If the later, then you are using it like a big magnet board.
You can use 'markers' with the train id and move them around a layout
drawing. You could also use buttons to flag which tracks are occupied, again
manual operation, if there is no sensing of the layout.
If you mean develop it offline, that is why almost all system connection
types have a 'simulator' interface. That lets you tell it what hardware will
be there and make assignments for what inputs and outputs do what.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Hi all. I'm a complete newbie at JMRI, (I have downloaded JMRI v.4.14), and have a couple of questions pertaining its use as a dispatchers panel, even though it's not connected to the track!
1/ Can I build a Panel that highlights occupied track and by which Train?
2/ Apart from the JMRI instructions,is there a step by step guide to setting it up?
I've spent sometime searching for answers, (maybe I'm thick!), but cant seem to find solutions!
Thanks in advance for any helpful responses
John
|
Locked
Re: DCC++ Arduino booster does not ack Raspberry Pi message
Hi Terry,
Sorry for the late reply. ?I haven't any direct experience of using a Pi with the Arduino DCC++ standard base station but I have played with JMRI DCC++ in conjunction with my own Arduino sketch. ?There may be some simple checks worth doing if you have not already done so. ?I assume here that you're using a USB/serial connection rather than the Ethernet option.
Can you load a new sketch on to the Arduino from the Pi using the IDE? ?It's worth while checking this to ensure it's not h/w connection related.
What do you see on the DCC++ traffic monitor (Panel Pro -> DCC++ -> DCC++ Traffic Monitor)? ?You should see JMRI periodically issuing 'Status Cmd' which should elicit some response from the Arduino.
Regards
Paul
|
Locked
Re: IR Block Occupancy Sensors - Entrance and Exit
Hi Don,
You are quite right that I do not know train direction. There are two main lines with loops and the signalling is predominantly single direction. There are some areas like station approaches where I have crossovers where the sensors lock out large non-directional blocks to prevent collisions but once the train is into a platform and has cleared the block the expectation is that it then sets off down the line in the usual direction!
Dave
|
Locked
Re: Bachmann Street Car
I¡¯d be very surprised if the Soundvalue decoder for the streetcar isn¡¯t essentially an electric Econami. ?Yes, it did exist, for a year or so. ? Have you tried the definitions for that? It did streetcars very well. ?I have one in a Bachmann trolley.
Mick
________________________________
Mick Moignard
m: +44 7774 652504
Skype: mickmoignard
, so please excuse the typos.
|
I will have to check out the Monitoring thing. Doing what I mentioned doing I was able to get all the routes I wanted to create (so far) working. With that done, my next step will be to use Touch Toggles on the panel that will control the yard.
Larry Sloan
toggle quoted message
Show quoted text
On Jun 5, 2019, at 8:30 PM, Ken Cameron <kcameron@...> wrote:
Larry,
Focus on getting the turnouts working right from the turnout table first.
Each turnout is a pair of events, thrown/closed. The feedback is normally
MONITORING. Once that is correct, then the Routes would be a route has one
or more turnouts, each turnout is selected to be thrown or closed. Keep in
mind for a given route you may have one to N turnouts in that path, you set
what they need for direction. Other turnouts are not included in the route.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
I sure did discover that!
toggle quoted message
Show quoted text
On Jun 5, 2019, at 7:14 PM, dick bronson via Groups.Io < dick@...> wrote:
Larry, Turnouts should never use 'toggle'. They should always use two
events, one for normal and the other for reverse. The only time
you would use 'Toggle' (alt action) is if you are controlling
something with a single local push button. (or a button with
feedback controlling an indicator) The problem with 'toggle' is
that you can not follow the turnout state. (as you have
discovered)
Dick :)
|
Larry,
Focus on getting the turnouts working right from the turnout table first.
Each turnout is a pair of events, thrown/closed. The feedback is normally
MONITORING. Once that is correct, then the Routes would be a route has one
or more turnouts, each turnout is selected to be thrown or closed. Keep in
mind for a given route you may have one to N turnouts in that path, you set
what they need for direction. Other turnouts are not included in the route.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Larry,
Turnouts should never use 'toggle'. They should always use two
events, one for normal and the other for reverse. The only time
you would use 'Toggle' (alt action) is if you are controlling
something with a single local push button. (or a button with
feedback controlling an indicator) The problem with 'toggle' is
that you can not follow the turnout state. (as you have
discovered)
Dick :)
On 6/5/2019 6:56 PM, Larry Sloan via
Groups.Io wrote:
toggle quoted message
Show quoted text
OK¡ so that may have resolved the startup issue. ?But when I build
a route and click on the route all the turnouts just change to
their opposite state. ?I was thinking this has something to do
with the Event 1 and Event 2 being set to Toggle.
Larry Sloan
On Jun 5, 2019, at 11:47 AM, Larry Sloan via
Groups.Io < larrylsloan@...>
wrote:
My
node is 02.01.57.00.00.DD
I just updated it. ?I will see
what happens.
Larry
|
No. JMRI routes set JMRI Turnouts to a specific direction. There¡¯s no need to create a workaround to do that, that¡¯s what they should already be doing. If you¡¯re not getting consistent operation between the JMRI Turnout and the physical layout turnout, you should fix that first instead of creating a workaround. (If you¡¯re using JMRI Sensors to control physical layout turnouts, you should fix that even before) Bob On Jun 5, 2019, at 4:24 PM, Larry Sloan via Groups.Io <larrylsloan@...> wrote:
So I¡¯ve figured out that if I want to build a route that I want to *always* go a certain way, that I almost need to configure a turnout as two separate turnouts. One for each route that I want the turnout to be a part of. Would you guys say that is accurate? -- Bob Jacobsen rgj1927@...
|
Locked
Re: Reporting a decoder file error in TCS FL2/4 function decoder
I suggest you open an issue on Github you need to create an account to do so.
It would also be helpful to provide an updated definition if possible.
--
Peter Ulvestad
JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -
|
Locked
Reporting a decoder file error in TCS FL2/4 function decoder
A few years ago I reported an error in the light function settings in the TCS function decoders, today I found the same error is still in place so am reporting it once again. I don't remember if at the time I checked the other settings, but the ones I needed at the time and are still incorrect are for ditch lights. The result is one ditch light is the ditch light of the opposite phase, the other result is a constant dim light instead of the 2nd ditch light. I haven't evaluated what other function settings might be incorrect
copied from the original post:
In the TCS FL4and FL2 function decoders, one of the values to make a function perform as a ditch light is incorrect. The CV value choices should be 10 or 11 for forward operation, 25 and 26 for reverse, and 41 and 42 for non-directional operation. The present values are a value of one too low, making one output non-operational when one uses a value of 9, 24, or 40 that are stored in the DecoderPro files.
Lyle Dowell
|
So I¡¯ve figured out that if I want to build a route that I want to *always* go a certain way, that I almost need to configure a turnout as two separate turnouts. ?One for each route that I want the turnout to be a part of. ?Would you guys say that is accurate?
toggle quoted message
Show quoted text
On Jun 5, 2019, at 3:56 PM, Larry Sloan via Groups.Io < larrylsloan@...> wrote:
OK¡ so that may have resolved the startup issue. ?But when I build a route and click on the route all the turnouts just change to their opposite state. ?I was thinking this has something to do with the Event 1 and Event 2 being set to Toggle.
Larry Sloan On Jun 5, 2019, at 11:47 AM, Larry Sloan via Groups.Io < larrylsloan@...> wrote:
My node is 02.01.57.00.00.DD
I just updated it. ?I will see what happens.
Larry
|
OK¡ so that may have resolved the startup issue. ?But when I build a route and click on the route all the turnouts just change to their opposite state. ?I was thinking this has something to do with the Event 1 and Event 2 being set to Toggle.
toggle quoted message
Show quoted text
On Jun 5, 2019, at 11:47 AM, Larry Sloan via Groups.Io < larrylsloan@...> wrote:
My node is 02.01.57.00.00.DD
I just updated it. ?I will see what happens.
Larry
|
Locked
Re: Tips for splitting my Loconet in two
Steve,
I have done some searching and cannot find the test files that I was using to verify what follows.? So, here are a couple of answers, starting with the one I am most confident about.
Since the throttles are being separated from the signal hardware, usually, all the throttles are placed on the throttle bus and all the signaling hardware (SE8Cs, RR-Cirkits, etc.) on the signal bus.? If all the signal hardware will play together, then that is the preferred way to go.? In that scenario, in JMRI, define the two Loconet interfaces in Edit-Preferences.? The signal bus connection is identified with the "L" system prefix and the throttle bus interface with your favorite prefix.? Under Preferences->Defaults, select the throttle bus interface for hosting Throttles, Power Control, Command Station, Service Programmer, Ops Mode Programmer, and Consists (i.e. simply check all those buttons, moving the filled in dots from the Loconet row to the throttle bus row).
If you cannot completely segregate the throttle hardware from the signal hardware, then things get a little more complicated.? Two buses (connections) must still be defined, as above.? However, CATS accepts only a single letter prefix (some of this stuff is old).? I recommend that you set up the JMRI profile, first, so that you can pick a prefix that will work.? I think JMRI reserves "I", so pick another one.? In designer, Devices->JMRI Devices.? Create two new rows via the Add button or overwrite the "JMRI Class" column on the two existing rows with the desired second prefix from your JMRI profile.? For example, suppose you want to use ES and ET as your sensor and turnout system names for the second Loconet connection.? You would add a row with prefix "ES", Type Sensor, and check the Select box.? The linkage between the JMRI system name and CATS is what goes in the "JMRI Class" column.? Copy the contents of the "JMRI Class" column for the LS row (jmri.jmrix.loconet.LnSensorManager) to the same column for the ES row. Do the same for the LT row to the ET row.? In the rest of the designer layout file, use the appropriate system prefix for each decoder address.
It would be best to be on a fairly recent version of JMRI (and CATS) for this to work.
Rodney
|
FCOT2002
Ken Cameron
Bob Jacobsen
Peter Ulvestad
Lyle Dowell