Locked
A Simplified JMRI WiFi Throttle you can Customize
Some modelers might be interested in this article which describes the construction of a simple WiFi throttle that connects directly to the JMRI WiFi server. It will support loco address selection, six (or more) function switches, speed and direction control, and power-on. While providing basic throttle functions, it can be customized and expanded by the inventive modeler to perform multiple functions at the touch of a button. You can also limit its functionality as you wish.
SMA30 A Simplified WiFi Throttle You Can Customize
Have fun!? :-)
Best regards,
Geoff Bunza
|
Locked
Re: Dual monitor oddity
OK, a similar issue that has been a minor annoyance.? New user here, all I am doing is using Ops for a bookshelf switching layout.??
I am using a MS Surface tablet, W10, i5, 16 GB RAM.? I often use the Surface dock to connect a 21" HDMI monitor.? Other times I just use the tablet itself if I'm away from my desk.
If I set the font to be readable on the tablet screen, it's huge on the monitor.? If I set it to be closer to normal on the monitor, it's too tiny to read on the tablet screen.? In fact, on the tablet screen what should be a large font, like 14, is rendered very very small.
That is for the apps themselves.? The Help app is different.? The help text is tiny, and I have to full-screen the window on the monitor to make it barely readable.? The help directory tree though is overly large, with every category overlaying the adjacent ones.? On the tablet screen Help cannot be read.??
There's gotta be a checkbox somewhere that is making this happen.
FWIW, I've never seen this happen before, and I regularly use MS Office apps and other programs without this happening.
Any assistance appreciated!
Chuck?
I tried both those workarounds.? Neither work here.
This odd window behaviour seems only to apply to JMRI
--
=================== Chuck Chandler ===================
|
Locked
Re: Panel Pro Roster picture access
Web server is running? ...? Roster images are visible in JMRI Roster(list)? and visible from both JMRI 4.6 and JMRI 4.14 on the JMRI web server roster page so I have localized it as not a JMRI problem?I am beginning to think that it has to do with memory.? I can see the images from 4.14 on a cell phone but not on a 7" tablet.? So I guess I will have to investigate it as something wrong with the tablet and not JMRI.? Once again, thank you for your response and help.??
|
Locked
Re: Block Occupied colour not working
Paul,
I looked at the block table and a lot of the blocks do not have an assigned sensor.
Dave Sand
toggle quoted message
Show quoted text
On Jan 17, 2019, at 12:53 PM, Paul Townsend <paultownsend49@...> wrote:
I have done the two checks you suggested.
I am unsure of the relevance of what you said under " note"
I have installed 4.15.2, result is my problem is unchanged.
Uploading "Pseudo Dartmouth_Mk42" in a mo. to problems being worked on
|
Locked
Re: MQTT Connection in JMRI
I don't think the "simplicity of the turnout concept"would be particularly helpful for this actual model example. How would the members here tackle this? Andy On 1/17/2019 9:24 AM, steve young via Groups.Io wrote: Hi Andy,
I think it's because of the simplicity of the turnout concept, combined with logix, routes and sensors, that enables JMRI to cope with all of the various scenarios you describe.
One important thing imho for the group to consider is whether the systems names should be considered equal if they use different cases.
Eg, would "Train" equal "train" ?? would "SENSOR47" equal "Sensor47", should they be considered completely different?
I think the default JMRI currently handles this in different ways for sensor and turnout naming so it would make sense to define this for MQTT early on,
Steve.View/Reply Online (#156078) </g/jmriusers/message/156078> | Reply To Group <mailto:[email protected]?subject=Re:%20Re%3A%20%5Bjmriusers%5D%20MQTT%20Connection%20in%20JMRI> | Reply To Sender <mailto:icklesteve@...?subject=Private:%20Re:%20Re%3A%20%5Bjmriusers%5D%20MQTT%20Connection%20in%20JMRI> | Mute This Topic </mt/24537680/958693> | New Topic </g/jmriusers/post>
Your Subscription </g/jmriusers/editsub/958693> | Contact Group Owner <mailto:[email protected]> | Unsubscribe </g/jmriusers/leave/defanged> [andy_r@...]
_._,_._,_ --- This email has been checked for viruses by AVG.
|
Locked
Re: (Another) new install not starting
Anti-virus programs can stop the app from running as it does not identify this first time install app.
Would need the logs from C:\user\** user name**\JMRI\log.? The session or messages? log would help.
Marc
|
Hello,
This email message is a notification to let you know that a file has been uploaded to the Files area of the [email protected]
group.
File: Pseudo Dartmouth_Mk42.xml
Uploaded By:
Paul Townsend
Description:
For solving problem re Occupied track colours not changing in Blocks 6,7 etc.
Working OK in Blocks 0-3
You can access this file at the URL:
/g/jmriusers/files/Pseudo%20Dartmouth_Mk42.xml
Cheers,
The Groups.io Team
|
Locked
Re: Block Occupied colour not working
I have done the two checks you suggested.
I am unsure of the relevance of what you said under " note"
I have installed 4.15.2, result is my problem is unchanged.
Uploading "Pseudo Dartmouth_Mk42" in a mo. to problems being worked on
|
Locked
Re: Programming locos with Fleischmann Twin-Center sw ver. 2.000 and DecoderPro 4.14
On Tue, Jan 15, 2019 at 10:16 PM, <cocco.bill.97@...> wrote:
Do you know if there are any plans to complete the support for the Intellibox 1/Twin-Center?
Not to my knowledge, and not on my end. If you have Java programming skills, you can make a try; the remaining work is not necessarily huge, but could be tricky (need to retro-engineer the protocol). ? -- Alain LM
|
Locked
Re: (Another) new install not starting
Thanks Mike - we'll try that.
David
|
Locked
Re: Block Occupied colour not working
Paul,
I created a new Layout Editor panel yesterday using 4.15.2 and the block color change based on block occupancy sensor works as expected.
Make sure that Track Color and Occupied Track Color are not the same color.
LE Options >> Track Options >> Default Track Colors defines the default values for new layout blocks. Make sure these values are correct.
Note: With the recent change to Track Drawing Options, ¡°track" colors are now actually ¡°block" colors.
If nothing else looks wrong, upload your panel xml file to ProblemsBeingWorkedOn.
Dave Sand
toggle quoted message
Show quoted text
On Jan 17, 2019, at 11:49 AM, Paul Townsend <paultownsend49@...> wrote:
Using 4.15.1.ish I can no longer add the feature where track colour changes on Occupation. The sensor input is working as a sensor light on LE changes correctly.
Blocks previously set up under ( I think ) ver 4.14 still work correctly and I can edit the Occupied colour OK.
Help!
|
Locked
Re: Crossovers not working on Panel Web Interface
Awesome, thank you!!!!
Kevin, was thinking of your idea as well but I want to keep things as simple as possible.??
I will swap files tonight and report back .
Tim
|
Locked
Block Occupied colour not working
Using 4.15.1.ish I can no longer add the feature where track colour changes on Occupation.? The sensor input is working as a sensor light on LE changes correctly.
Blocks previously set up under ( I think ) ver 4.14? still work correctly and I can edit the Occupied colour OK.
Help!?
|
Locked
Re: (Another) new install not starting
?I have a Dell , try right clicking on the PP icon and then select "open" . Double clicking won't work for me either ,.....Mike
I have just installed JMRI 4.14 on a friend's computer and the program will
not start.
What I know:
This is a first time installation.
Computer is a Dell laptop - running Windows 10.
Computer reports Java 1.8 as installed, and JMRI program installed with no
complaints.
When I double-click on the "Panel Pro" icon, absolutely nothing happens.
When I get back to his computer next week I shall do the 'java version test'
as described in recent posts, and run the JMRI "Install test.bat".
Until I do, does anyone have any bright ideas?
Thanks;
David
|
Locked
Re: Trouble setting a Throttle in JMRI
Just off out Steve will post on return. Tim
|
Locked
Re: Dual monitor oddity
I tried both those workarounds.? Neither work here.
This odd window behaviour seems only to apply to JMRI
|
Locked
Re: MQTT Connection in JMRI
Hi Andy,
I think it's because of the simplicity of the turnout concept, combined with logix, routes and sensors, that enables JMRI to cope with all of the various scenarios you describe.
One important thing imho for the group to consider is whether the systems names should be considered equal if they use different cases.
Eg, would "Train" equal "train" ?? would "SENSOR47" equal "Sensor47", should they be considered completely different?
I think the default JMRI currently handles this in different ways for sensor and turnout naming so it would make sense to define this for MQTT early on,
Steve.
|
Locked
Re: Trouble setting a Throttle in JMRI
Hi Tim,
Could you post your console log showing the CAB acquiring and releasing the throttle, then the JMRI attempt to acquire the throttle?
If there's nothing in the console log for the CAB attempt, JMRI isn't connected to the CAN network.
Thanks,
Steve.
|
Locked
Trouble setting a Throttle in JMRI
Hi, I've got a problem with my JMRI/MERG DCC set-up
I'm running JMRI version 4.12 and Java 1.8.0_201 with the MERG DCC system, CANCMD, CANCAB and NB1B Booster.
When I try to select a loco I get a RLOC timed out message and no loco control. Most of the throttle panel stays greyed out.
I've looked at the default preferences to make sure they're not set in internal and they're fine.
If I use the CANCAB handset instead of JMRII can select and control locos.
Hope someone can help.
Many thanks, Tim
|
Locked
Re: MQTT Connection in JMRI
I'm still bothered that all this is based on the simplistic idea that railroads consist of merely simple turnouts and plain track. I know of multi-way turnouts, stub multi-way turnouts, multi-gauge mixed route turnouts, fixed crossings, switched crossings, crossovers, double crossovers, single slips, (inside and outside), double slips, (inside and outside), gantlett tracks, grade crossings and multi-track versions of all the previous, plus turntables and traversers . All of which are devices that cannot be expressed as merely "thrown" on a single route.? In every case they variously change the route direction and/or clearance options of other routes they are not connected to, besides the one being addressed. I would vote for replacing the "simple turnout" device with a more generalized state machine like entity that is a "route(s) modifier" and which clearly reports its effect on all the routes that it controls, whenever it's input(s) are changed. Andy On 1/17/2019 4:53 AM, Dave wrote: Folks,
There have been plenty of good ideas tossed around in this discussion and I think we're almost at completion, with I think just a couple of minor loose ends to settle.? I think this is where we are at, please correct me if my understanding is incorrect.
channel - yes or no? or optional? - noted below as optional because I don't know if it is in or out.
*Topic:*
The topic is the device identifier and must be unique.
Naming is totally user choice. If a channel name is defined on the connection page, that will be used as the top level.
Hardware name: topic components entered when creating a new device
System name: derived as Connection Prefix + Device type character + topic
Topic:? [ channel/ ] + hardware name
The syntax should be validated at the time of data entry to ensure that the topic has no leading or trailing slashes and one and only one slash between topic levels.
*Payload: *
Use the state as it appears in the associated JMRI table.
Json format yes or no?? or optional, perhaps a setting on the connection page?? If yes, something like {"state":"Thrown"}
My personal opinion, though happy with either option, is to use Json format. Whilst I think there is little benefit of using Json just to show the state, using Json now may be a better starting position for future enhancements that may include additional data.
*Device types to be included:*
Turnouts
Lights
Sensors
Signal heads
Reporters
Regards, David.
--- This email has been checked for viruses by AVG.
|
Geoffb
Chuck, WS1L