Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Jmriusers
- Messages
Search
Locked
Re: Layout editor zoom issue- new insights
#layouteditor
You may be looking at old sources¡ my LayoutEditor.java only has 7920 lines. I refactored all the drawing code into LayoutEditorComponent.java and all the ToolBarPanel code into LayoutEditor[Horzontal, Vertical, Float]ToolBarPanel.java.
|
Locked
Re: Layout editor zoom issue- new insights
#layouteditor
The culprit here is the clipping region. It's maintained via the Editor superclass. I've spent days trying to get it to work correctly without any luck.
Even now if you zoom the window fullscreen and then grab the lower right corner and resize toward the upper left corner you'll notice the drawn tracks will start disappearing. This is because the clipping region is shrinking faster than the window is resizing. |
Locked
Re: "Connectivity error when searching turnouts" when load layout editor panel
#layouteditor
See?:?LayoutEditor:Fix Connectivity error when searching turnouts in Block
|
Locked
Re: "Connectivity error when searching turnouts" when load layout editor panel
#layouteditor
Found the bug! In LayoutSlip.getLayoutConnectivity() the DOUBLE_SLIP is limiting BD instead of BC:
This line (¡Ö1847): ? ? ? ? ? ? if ((type == DOUBLE_SLIP) && (lbB != lbD)) {
should be: ? ? ? ? ? ? if (lbB != lbD) {
And this line (¡Ö1863)
? ? ? ? ? ? if (lbB != lbC) {
Should be:? ? ? ? ? ? if ((type == DOUBLE_SLIP) && (lbB != lbC)) { I'll submit a PR asap¡ |
Locked
upgraded from 4.17.3.ish to 4.18
Upgraded from JMRI 4.17.3.ish to 4.18
I am using 3 Keyspan USB to serial converters on a Mac I am using keyspanUSAdrvr 4.0b4 because of upgrade to Mac 10.15.2 One connection is CMRI with 9 SMINIS One connection is Powerline with Insteon One connection is Lionel TMCC Did not have to reinstall any Keyspan Drivers or anything else. It just started up and worked. I had been running JMRI from a folder on my desktop. I dragged the JMRI folder with 4.17.3 to the applications folder. I then threw the panel pro icon on the dock into the trash. Then I dragged the panel pro icon in the JMRI folder in applications to the dock. Clicked on the panel pro icon on the dock and everything started up normally. I then downloaded JMRI 4.18. I placed it in the Applications folder. I threw the old 4.17.3 panel pro icon in the dock into the trash and dragged the new panel pro icon from 4.18 out of the applications director to the dock. Started the system by clicking on the new panel pro icon in the dock. All worked perfectly. Wi Throttle on iPhone worked Running a Mac Mini quad core i7 with 10 gb ram and a 512 gb SSD and 2 monitors Monitor 1 is 19 inch 1280 by 1024 Monitor 2 is 34 inch ultrawide 2560 by 1080 Using Panel Pro Java 1.8.0_191 (en_US) Mac OS 10.15.2 A long standing bug that made an Apple Mighty Mouse ( USB) jumpy and unusable seems to have been fixed with 10.15.2. Had to use a trackpad on JMRI since it only affected JAVA apps. So far the mouse is working okay. Will keep and eye on that one. Jim |
Locked
Re: Signalling feedback to Panels
Hi Brian
If neither party is willing to help then we can only develop software that allows people to fully utilize the product by observing cause and effect. Stuff like, "I sent this", "this happened" and "this was the response". This work is usually done by an interested owner of the hardware. If you have logs of all of the interactions then maybe something could happen.? Steve G. |
Locked
Re: Function mapping on ESU V4
#esu-decoders
¿ªÔÆÌåÓýStefan and Michael? Read the documentation [RTFM? ;-)], Unfortunately the ESU decoder manuals are not a great help with the function map. They just present a bewildering array of Function Map CVs (640 for V4, more than 1,000 for 5). A good resource is Phil Dunlop's excellent unofficial LokProgrammer manual, found in the Files area of the LokSound group. it is very easy to do, I have done it a number of times for my own small roster and for friends. Here's an expanded version of this: 1) You must use New Loco->Read Type from Decoder and use the model it picks. 2) You should use Direct Mode to read these decoders (despite misinformation to the contrary peddled by some OEMs). Some DCC systems will fail to read some CVs in Paged Mode or may return incorrect values. 3) You must read the Decoder Default CVs. Reading the full decoder is essential, particularly with ESU decoders where there are no "standard defaults". Each sound project has its own "factory defaults". All ESU sound decoders are manufactured effectively blank. When a Sound project is loaded to the decoder (using LokProgrammer software) part of the procedure is to write a new set of "factory defaults". Because of a known (but as yet unresolved) race condition with certain decoder settings variables in JMRI code: i) Use "Read Full Sheet" on the CVs pane instead of "Read All Sheets". It is less likely to cause errors when reading a decoder with lots of CVs. Once finished, some may be missed (displayed in red). Use "Read Changes on Sheet" as many times as needed until no red items remain. (Hint: Click on the Status column in the CVs pane until you see a down arrow. All the Red items will then be at the top.) ii) After you make changes on a programming sheet, don't use Write/Read changes on that programming sheet. Instead, switch to the CVs pane and use Write/Read changes on (the CVs) sheet. The result is the same but it will never trigger the race condition. You'll also see a number of messages in the JMRI System Log like this: "ERROR - Variable=xxxxxx; Busy goes false with state IDLE" Ignore these as they don't indicate a real error, we'll fix the problem in a later JMRI release. 4) Save the roster entry once you have successfully read all CVs Programming the Function Map - Read the information about the Function Map on the README pane of the Roster Entry. - Ignore the line numbers of the Function Map. They are just there for convenience and bear absolutely no relationship to F keys on your throttle. - You read the Function Map by reading across a line (ignoring the line numbers). So your decoder will most likely have a line that reads: "F0,Forward Headlight[1]". There will also most likely have a line that reads: "F0,Reverse Rearlight[1]". These lines may be on any line and not even in that order. The line order doesn't matter in the slightest, nor the lime numbers. - To change an F key assignment, you simply find the line that mentions what you want and change the Conditions (first box) in the line. So if you want to change the Rearlight to F5, you'd Change the Conditions box to read F5 (uncheck F0 and Reverse). If you accidentally left F0 checked (the box would read F0,F5 Rearlight) you'd have to have both F0 and F5 on for the Rearlight to work. - When you remap you will almost certainly end up with the F keys out of order as you read down the page. That doesn't matter in the slightest, nor do any blank lines. (You can reorder the lines by selecting the radio button in the first column of any line and using the Up or Down buttons to move that line. But that's only necessary if you want to be obsessive, it makes no difference to the decoder and you'll have a lot more CVs to write when you do a Write Changes.). Dave in Australia |
Locked
Re: withrottle not working with V4.18
#withrottleserver
#4-18
Fixed - thanks Dale Gloer for linking back to the previous thread.
|
Locked
Re: Car Order
#operationspro
Doug,? I've been using JMRI Ops and refining it to suit my operations for the last 5 years. It is a wonderful?car forwarding program. On my layout I pretty much do as you are suggesting could be solutions for your layout.? As part of my pre operations setup I BUILD my trains according to the schedule /? sequence that I'm going to run. From this I have the information I need to block the cars in the trains located at staging. They are blocked according to the DROP OFFS performed as the trains make their way around the layout. This minimizes car classification for the main yards as they already have enough to do.?? The paperwork also generated are the switch lists for each yard. These are issued to the yardmasters and it is their role at the commencement of the session to start classifying the cars already in the yard interchange and classification track required for each trains PICK UPS. This is generally done by the yard masters inline with the sequence of train arrival times for that particular yard under their control. Since refining my operations to this methodology it has freed the yards up somewhat from becoming bottlenecks and has smoothed the flow of traffic across the layout. Plus less stress for he yard crews. Hope this is of help.? Duncan? On Tue, Dec 31, 2019 at 3:52 AM Doug <dougsrr1@...> wrote: Taking another look at JMRI Ops after about 8yrs. of CC/WB.? I am interested in knowing how folks, particularly those running longer over the road trains, are working their classification yards.? I am considering either working the staged trains prior to an Op Session to match the manifests or adding a staging crew to do that live.? In addition, am thinking about a trimming crew in the major yards to do the same thing with cuts that will be picked up. |
Locked
Re: Rotation of layout
#layouteditor
Hi All, Updated from 4.16 to 4.19.1, rotated dual panels (top level and lower level of layout) and saved panels. Then loaded 4.18. All good. Again thanks for incorporating this feature. All the best for the New Year. Regards, Kel Wellington, New Zealand |
Locked
Re: withrottle not working with V4.18
#withrottleserver
#4-18
I have the same problem.
I see the post about the consist.xml. What needs to be done about the consist then to fix this? |
Locked
Re: Car Order
#operationspro
A person can make this so rigid that we are not having fun anymore. On my RR cars come from staging (the rest of the world) to to my yard I/C and terminate. from this point on the program does it's thing and the train is built now whether the cars are in order is up to the yard clowns. When the local comes back to the yard it will go to the departure tracks and terminate. The train going back to staging is built and again the order the cars go to the train is up to the clowns. When the cars go to staging they have left the railroad. They will be gone for up to 80 staging trains worth. This is beautiful perfect can't complain.
The program tells us what to do by the info we give it, working as intended. By sending cars into staging we tell the program that the train is gone bye bye. When we hit the button to bring the cars back online since they theoretically been traveling all over the place not on our part of the rail system, the program has to pick an order for the cars to be in so guess what? we get in order loco numbers, car numbers (smallest to largest), and caboose. I am perfectly fine with this practice. I have an old prototype program that works fine as long as there is a clerk telling the program where the car is I don't think it is possible to have a program follow our thoughts. So just have fun and if you need the train in order out of staging STOP and put it in order you will be amazed at the number of people that can't put a train in numerical order. This program works wonderful. Thanks to those that have made this possible. I have learned to live with the things I can't change we cannot be fired for not having cars in some predetermined order or any other of ten thousand ideas that doesn't matter one iota Just my thoughts and have fun Matt Greenwood Former Engineer and Conductor in real life BMFWIC on the Cascade Rwy Grant NE? |
Nigel, Thank you for the tip, I will have another go tomorrow. Interestingly I have a ROCO loco and the same problem with decoder pro, but I did 4 digit decode it with my Digitrax set up.
toggle quoted message
Show quoted text
All help is welcome, it seems like the older you get the slower in life. All the best, Mike Shore On Dec 30, 2019, at 5:18 PM, Nigel Cliffe <nigel.cliffe@...> wrote: |
Pick the nearest equivalent decoder, with the nearest firmware.
toggle quoted message
Show quoted text
Zimo release lots of decoders, and keep changing the firmware. This is good, its more features in the decoders. But it makes it hard work for volunteers to keep up with every change. Fortunately most Zimo changes are incremental small changes: a new firmware brings is a couple of very minor features. So, using a slightly older version will be fine. Zimo use the same firmware in all decoders, so picking a different decoder hardware rarely has consequences, provided the decoder picked has enough function outputs (lighting outputs) for your needs. Or, join those who edit the Zimo files to try to keep up with the changes. - Nigel -----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Shore Sent: 30 December 2019 20:53 To: [email protected] Subject: [jmriusers] Zimo decoder recognition by Decoderpo I¡¯m an European model train user and relatively a new user of a Sprog/ Decoder pro for roistering my locomotives. In the past few years TRIX change their programming of their HO model trains. The Digitrax program doesn¡¯t allow 4 digit addressing with the TRIX locomotives. I then purchased the Decoder pro/ Sprog, I was able to program some of my locomotives, but recently any Zimo decoder wasn¡¯t recognized, and I was unable to set up the address. Does anybody have a solution for this apparent problem. Thank you in advance of a reply, Mike Shore |
Locked
Web panel refresh after scripted panel changes
I've come across a couple of scenarios where the web panel becomes inconsistent with the native layout editor panel:
First issue:
import jmri; jmri.InstanceManager.getDefault(jmri.jmrit.display.PanelMenu).getLayoutEditorPanelList()[0].sensorImage[2].setHidden(True)
In my 'real' scenario I've created scripts that isolate the sensors and other items I need to hide/show. I'm wondering what are the commands to
Thanks Andy |
Locked
Re: Layout editor zoom issue- new insights
#layouteditor
One more detail, the initial setup and adjustScrollBars() use 2 different names for the scroll bars- the initial setup uses hsb and vsb, whereas the adjustScrollBars part uses horscroll and verscroll.
|
Locked
Re: calling dispatched from script
Bill
I tried this and it worked for me. I used the LH-Xover, 2 separate addresses, not inverted. All six routes thru the Xover worked. Steve G. |
I¡¯m an European model train user and relatively a new user of a Sprog/ Decoder pro for roistering my locomotives. In the past few years TRIX change their programming of their HO model trains. The Digitrax program doesn¡¯t allow 4 digit addressing with the TRIX locomotives. I then purchased the Decoder pro/ Sprog, I was able to program some of my locomotives, but recently any Zimo decoder wasn¡¯t recognized, and I was unable to set up the address.
Does anybody have a solution for this apparent problem. Thank you in advance of a reply, Mike Shore |
Locked
Re: Layout editor zoom issue- new insights
#layouteditor
Also, unless I misunderstand, on line 9066, it should be "rectangleToRectangle2D", not "rectangle2DToRectangle", since the variable being defined is a "rectangle2D".
|
to navigate to use esc to dismiss