Locked
Signalling issue with my panel
Hi,
I have built a panel in panelpro using layout editor, so far I am very pleased with the results. ?However I have just added signals to the panel and they do not operate quite as expected. ?
I am using the BR.2003 system and have added a mixture of signals, several dual aspect, one three aspect with feather and several ground signals.
I have set them all up in the signal heads and then signal mast as per the instructions. ?I can change the aspects from either table ok.
I have then added the signal masts to the panel in the locations I want them to be and to some extent I am very happy with the result as I can control the aspect by clicking on the panel.
My confusion comes as when I load the panel all the signals look like a red X. ?I had created a load of routes to set up routes but I also included a reset route which I use at loadup to reset all points closed and all signals red.
The panel updates nicely showing the position of all the points/turnouts but the signals remain as a red X.
How do I get the panel to refresh the signal condition other than me having to go round and click each one several times until showing red.
Hope this makes sense, I cannot find anything in theorem to the help pages.
regards
Doug
|
Locked
Re: Dispatcher - SML - auto-allocation problem
Steve,
Yes that makes sense, my loco stopped after the green signal S04 because it wasn¡¯t allocating any further.
so in that case, I¡¯m I pretty much screwed on getting this to work?
technically the signal SHOULD be green for both closed and thrown for LT1. A manual train has right of way for both if they are clear.
its when LT1 thrown is not clear, so dispatcher doesn¡¯t assign the route, so the signal stays green for closed and it goes past until that failsafe kicks in.
I¡¯m failing to see a workaround at this point apart from playing with direction sensors in SML.
I just hope then when NOT using dispatcher, my signals stay clear and don¡¯t all turn red bexuse there¡¯s no allocations.
--
Thanks
Mitch
|
Ken,
I assume that you are using Layout Editor.
The track circle color and size are based on the turnout circle: "Options >> Turnout Options >> Set Turnout Circle Color¡±.
Dave Sand
toggle quoted message
Show quoted text
On Nov 29, 2018, at 9:29 AM, KEN <boomer17@...> wrote:
How do I change the color of the track circle that shows in edit mode? It is now black.
Thanks,
Ken
|
Locked
Re: possible bug, LocoNet slot monitor
My preference would be that any slot that has a Loco address in? it should be displayed.? That seems to me like very simple filtering also.? Have that as the default and if you want check boxes to refine the filtering that is okay but not necessary in my opinion.
Dale Gloer
|
How do I change the color of the track circle that shows in edit mode? It is now black.
Thanks,
Ken
|
Locked
Re: Reading and programming new BLI PRR T1 - PROBLEM
I suspect you may need a higher current supply, 1A may be a bit light.
?
If you can find a supply with 2A or 2.5A I would give that a try to see if it helps.
?
?
?
From:
[email protected] <[email protected]> On Behalf Of
Michael Hahn
Sent: 29 November 2018 01:52
To: [email protected]
Subject: Re: [jmriusers] Reading and programming new BLI PRR T1 - PROBLEM
?
Hi Peter:
The decoder will NOT identify of I "Read type from decoder".
I have not yet tried different programming modes.? I use Direct, having been warned that this is the most reliable.? I can try other modes.
In manual decoder selection, I specifically selected the Paragon 3 "Steam" definition; I did NOT select the "Rolling Thunder" definition.
My Power Supply has output of 18 V, 1 AMP.
I am also having trouble reliably reading all CVs of other BLI Paragon 3 decoders.? And had problems reading the new Piko BR 82, which nominally has an ESU Dekoder.
So far the only way I have been able to program the addresses for these Locos is to select NMRA Standard Definition and only program the address.? That works!? But it leaves me high and dry if I ever have to reprogram the whole decoder!!
Cheers,
Michael
|
I do think that we have ¡®lost the plot¡¯ in this discourse. The original posting was not about ¡®actuators¡¯ or how we control the turnouts but simply that where multiple turnouts are used then each turnout should have its own name and the ability to enter the ¡®Associated Turnouts¡¯ name in the Tool Bar of the Layout Editor when initially creating the design as well as the ability to do this using the Turnout Editor.
I read more into the use of the Blue connector than I should have which, in turn, opened the door to signalling these formations and that led onto the control of multiple turnouts.
Lots of useful info nevertheless!
Dave
toggle quoted message
Show quoted text
On 29 Nov 2018, at 09:33, George Warner via Groups.Io < geowar1@...> wrote: Crossovers can have one to four turnout actuators (and I¡¯ve seen all combinations on real layouts) but only two actual useful states. There¡¯s little advantage to having any additoinal turnout actuators at different addresses. I¡¯ve only ever seen them all share the same address.
If your heart is set on using different address (for what ever reason you¡¯ve contrived) you could ¡°build your own¡± crossover using two left hand or two right hand (for single crossovers) or both and a level crossing (diamond) (for dual crossovers).
|
Locked
Re: possible bug, LocoNet slot monitor
First off: I have no stake in this at all. But reading along, it seems to boil down to a UI question. And I think that sort of question has been successfully answered in other products I have used by having the original checkbox and a second one labeled 'Advanced settings' that releases the four checkboxes instead of the one. That steers inexperienced users quite reliably away from areas where they could do more harm than good while giving 'power users' all they need.
Wouter
Hi
I agree that the four check boxes approach aint the greatest for general use.?
The generalised approach would be the Excel one of right clicking the column header and selecting the filter options, a lot of work to develop.
The default was to show anything not free. So Common, idle, In Use. It could be reprogrammed to that.
While the discussion goes on, try selecting show all slots and then sort descending on loco number column (click on the header column name). It will get you to the same place.
You can click on any of the headers to sort on that column.
My biggest problem on this screen is that the default direction column width is too small and that it doesn't remember my choices. With some direction we can fix this up. Colours, any one want colours?
Steve G.
|
Crossovers can have one to four turnout actuators (and I¡¯ve seen all combinations on real layouts) but only two actual useful states. There¡¯s little advantage to having any additoinal turnout actuators at different addresses. I¡¯ve only ever seen them all share the same address.
If your heart is set on using different address (for what ever reason you¡¯ve contrived) you could ¡°build your own¡± crossover using two left hand or two right hand (for single crossovers) or both and a level crossing (diamond) (for dual crossovers).
|
The MOLE I switch machine I designed has a double ended throw side arm, so that, using tube in wire, connected at each end, it can operate throws in opposite directions simultaneously. The MOLE itself is hidden in this clip, but you can see it throwing both points of one end of a double crossover in the street track progress you tube video ? ?starting at ~ 15 seconds in. The Proto:87 SIG has developed a lot of inexpensive technology for Proto:87, that is just as useful for regular HO. Andy ?On 11/28/2018 2:18 PM, Don Weigt wrote: I defy you to make a real crossover with only one turnout.
Logically it may have only two states, and one JMRI "turnout" definition may suffice to control it. But, having the JMRI configuration not match the physical one only makes it that much harder for us newbies to fathom how all this works on our physical layouts... One to one mapping is much easier to understand!
On a sad note, I learned today that Sudro Brown has passed. He has been mentioned here as a JMRI expert in central Massachusetts. He was a local JMRI hero. Hearing Sudro demonstrate and expound the advantages of JMRI is what made me consider trying it. He'd say, "If you're not using JMRI, why aren't you?!"
I will miss having a JMRI expert in my NMRA division covering Connecticut and part of Massachusetts. It makes me even more appreciative of the time and effort knowledgeable members of this group spend helping the rest of us. Thank you all!
Don Weigt
--- This email has been checked for viruses by AVG.
|
Locked
Re: Reading and programming new BLI PRR T1 - PROBLEM
Hi Peter:
The decoder will NOT identify of I "Read type from decoder".
I have not yet tried different programming modes.? I use Direct, having been warned that this is the most reliable.? I can try other modes.
In manual decoder selection, I specifically selected the Paragon 3 "Steam" definition; I did NOT select the "Rolling Thunder" definition.
My Power Supply has output of 18 V, 1 AMP.
I am also having trouble reliably reading all CVs of other BLI Paragon 3 decoders.? And had problems reading the new Piko BR 82, which nominally has an ESU Dekoder.
So far the only way I have been able to program the addresses for these Locos is to select NMRA Standard Definition and only program the address.? That works!? But it leaves me high and dry if I ever have to reprogram the whole decoder!!
Cheers,
Michael
|
Locked
Re: Dispatcher - SML - auto-allocation problem
Mitchell
I did take a cursory glance at the fail safe, it only works after you have gone by a red light, so doesn't apply here.
Steve G.?
|
Locked
Re: possible bug, LocoNet slot monitor
Hi
I agree that the four check boxes approach aint the greatest for general use.?
The generalised approach would be the Excel one of right clicking the column header and selecting the filter options, a lot of work to develop.
The default was to show anything not free. So Common, idle, In Use. It could be reprogrammed to that.
While the discussion goes on, try selecting show all slots and then sort descending on loco number column (click on the header column name). It will get you to the same place.
You can click on any of the headers to sort on that column.
My biggest problem on this screen is that the default direction column width is too small and that it doesn't remember my choices. With some direction we can fix this up. Colours, any one want colours?
Steve G.
|
Don,
I have several on my layout. They consist of a single turnout motor driving a bar pivoted at the center point between the two switch points. (under the roadbed) Think a piece of a yardstick, but it is actually just a wooden stick about that size. Each end of the bar has a piano wire mounted vertically that passes up through the roadbed to each throw bar. This results in the points moving in opposite directions as needed for a crossover. The flex in the piano wire accounts for any small errors in alignment between the two ends of the actuator bar. Because of the length of the bar the motion at the pivot is very small and I expect them to last well past the 15-20 years that they have been installed. One actually has dual bars that control a double crossover. (two machines, and 3 positions, left, straight, and right) That one has the pivots offset from the centers of the bars so that they don't both need to be at the same spot.
Dick :)
toggle quoted message
Show quoted text
On 11/28/2018 5:18 PM, Don Weigt wrote: I defy you to make a real crossover with only one turnout.
|
I defy you to make a real crossover with only one turnout.
Logically it may have only two states, and one JMRI "turnout" definition may suffice to control it. But, having the JMRI configuration not match the physical one only makes it that much harder for us newbies to fathom how all this works on our physical layouts... One to one mapping is much easier to understand!
On a sad note, I learned today that Sudro Brown has passed. He has been mentioned here as a JMRI expert in central Massachusetts. He was a local JMRI hero. Hearing Sudro demonstrate and expound the advantages of JMRI is what made me consider trying it. He'd say, "If you're not using JMRI, why aren't you?!"
I will miss having a JMRI expert in my NMRA division covering Connecticut and part of Massachusetts. It makes me even more appreciative of the time and effort knowledgeable members of this group spend helping the rest of us. Thank you all!
Don Weigt
|
>>>?However, since Crossovers require two Turnouts
Crossovers don¡¯t require two turnouts¡ they really only have two usable states: ¡°Normal¡± and ¡°Diverging¡±. These two states can apply to multiple turnout actuators but aren¡¯t ¡°required¡±.
|
Locked
Re: possible bug, LocoNet slot monitor
Bob J does a good job of focusing the problem on a key question (like he usually does!): What do we want the JMRI "LocoNet Slot Monitor" tool to do?
Whatever we come up with, I think we need a simple-to-use mechanism with a carefully-chosen default setting.
For the existing GUI, I would argue that the "default" mode of operation (i.e. "show unused slots" checkbox unchecked) should show any slot which can be actively controlled by a throttle (JMRI, Wi, Digitrax, or otherwise). This interpretation means, I believe, that "IN_USE" state _and_ "COMMON" state slots should always be shown, and "checking" the "show unused slots" checkbox would enable display of "FREE" state and "IDLE" state slots.
I do not support the idea of replacing the simple "show unused slots" checkbox with four checkboxes, one for each slot "state". The typical LocoNet/JMRI user doesn't have a clue about "slot state" values. Implementing four checkboxes, one for each state would cause massive confusion in the user-base, and would require significant re-training and support.
However, I and other power-users have uses for the four-checkbox approach. We could implement an option where the user could fiddle something like a checkbox in a new menu item on the Slot Monitor tool to swap out the simple "show unused slots" checkbox for the four "checkbox per slot status value" checkboxes.
Regards,
Billybob
|
Locked
Re: Multisensor Icon Rotation in CPE
Bob, thats a great point about Multisensors generally being used with levers, and needing to be defined as getting clicked left/right or up/down. In my case, the multisensors will be disabled, as the icons are only information feedback in their use.
As a workaround, I just rotated the original graphic to the needed orientation outside of JMRI. Working great and moving along once again.
Thanks
Steven
|
Locked
Re: possible bug, LocoNet slot monitor
I agree, lots of other things in that commit. I would say the change from
looking for LOCO_IN_USE to != LOCO_FREE would come closest to the older
results. My other thought was if anything had a throttle speed != 0, that
should always return true also.
I see the filter being nice an clean compared to old way.
I don't have a working repository right now or those two things are what I'd
consider doing.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Locked
Re: possible bug, LocoNet slot monitor
I suspect from reading the github pages that the original intention was to offer more checkboxes to choose which things to display. So, my ideal solution would be to have checkboxes for all of the states available at the top of the listing, and the user selects the ones they want, and that selection would be persistent between JMRI sessions.
If that's too much work (and I appreciate I'm asking someone else to do work), then of the states listed by Bob, I'd pick all of them except "LOCO_FREE =0"
- Nigel
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] [mailto: [email protected]] On Behalf Of Bob Jacobsen Sent: 28 November 2018 16:11 To: [email protected]Subject: Re: [jmriusers] possible bug, LocoNet slot monitor That particular PR includes a lot of good stuff besides this change to the filter logic. The filter part seems to boil down to a line that says (effectively) ¡°if no checkboxes are selected, display slots that have status ¡°LOCO_IN_USE¡±. The older code was so messy (and I can say that, as I wrote it) that it¡¯s not clear to me what it was doing before. Which of these states should it (by default) show now? * LOCO_IN_USE which is defined as STAT1_SL_BUSY | STAT1_SL_ACTIVE (this is happening now) * LOCO_IDLE = STAT1_SL_BUSY * LOCO_COMMON = STAT1_SL_ACTIVE * LOCO_FREE = 0 Bob On Nov 28, 2018, at 7:55 AM, John Griffin <johng.sst@...> wrote:
I think this should be reverted before the release of 4.15 If I could convince myself to participate in the development of this product I would do it but I've been retired for just 1 year and need to get away from Java for a while (java engineer for many years).
On Wed, Nov 28, 2018 at 12:08 AM Bob Jacobsen <rgj1927@...> wrote:
If somebody wants to look into restoring the previous behavior, the commit that changed this was
commit 7cc228bfaf451520ea16cb8e18b950050d1f9a4d
Date: Tue Dec 19 19:59:16 2017 -0500
Partly add filtering to Slot Monitor table
Need to use filtering instead of manipulating the model to implement checkboxes showing/hiding certain types of slots.
:040000 040000 e4378d76dab518e516a5ef33130d95bdfc1db7d0 d8cfda18046228b646c8ead203ceabd08b7bf201 M java You can see the full set of changes here:
The PR that included it is here:
It¡¯s called "Fix errors reading slots in Slot Monitor¡±
It doesn¡¯t look to me like the Zephyr behavior change was intended, but rather an unintended part of fixing some intermittent failures under load.
It first appeared in JMRI 4.11.1 on December 24th, 2017.
Bob
--
Bob Jacobsen
rgj1927@...
--
John Griffin
_______________________________
If today was your last day, you would...
-- Bob Jacobsen rgj1927@...
|
Dale Gloer
George Warner
Ken Cameron