开云体育

I get confused when Dave uses the term INFERNALS...

??? I always thought that was a joke.? Because a least one version it generated a mass of email.

-- 
Jon Miller
For me time stopped in 1941
Digitrax  Chief/Zephyr systems, 
SPROG, JMRI User
NMRA Life member #2623
Member SFRH&MS

In an ideal world mobile decoders would have a globally unique and immutable serial number in the same way that network interface controllers have a MAC address, and the DCC address would be akin to the IP address which can be assigned and reassigned as required to meet local operational requirements. When it's necessary to identify a decoder you would read the unique serial number and so on, but when operating a decoder the DCC address is used. However this isn't likely to happen in the near future.

Reading the correspondence above suggests that any solution based on reading the DCC address on its own or in conjunction with other CVs is likely to be problematic and the best that could be achieved from reading decoder CV values is to produce a list of matching roster candidates. ?If you're lucky the list will have only one entry. ? There are users like me, who have relatively small rosters, and are unlikely to have duplicate matches, however I rarely use the 'identify' button as it's usually faster just to select the roster entry by eye. ?It's the users with larger and more complex rosters with the problems in this area who, I suspect are more likely to use the 'identify' button and have most to gain from any enhancements in this area.

One though I had ?was to consider the use of RFID tags. ?These are relatively easy to secrete in a locomotive or whatever, and JMRI already has support for RFID readers. Although not a scripting expert, ?I think that it should be possible to write a script that listens to the RFID reader next to a programming track, and uses the RFID value to find the roster entry associated with that RFID and then display the roster entry.

Paul

Thanks for the details, Martin. Good to hear it's working for you.
In my experience, running the GUI desktop takes a large chunk of RPi memory, and I found it too slow for my taste until the RPi2 and RPi3, which bumped memory to 1Gb. The PiZeroW is still at 512Mb.
I'm curious why you're not using (newer) smart tablets for displaying your local panels? The /panel web client only gets updates for items defined on the specific panel shown.
--SteveT

开云体育

开云体育

What happens if you drag an upside down image into JMRI?

John

Group:

Interesting thought... language localization... Just how much of where it was invented take hold on how the name and or terminology take language root else where. The three starting places of railroading being the UK, USA and Germany whose language for a major invention or innovation did that language (given difference in spelling) become the common term? This is fun, we came up with "frog"... jumping one rail over another..? Did that stay frog when the RR came to Italy or translated to rana?

I'd be curious how the "home" language takes root in other languages... think airplane speak... That bit of language "domination" is more practicality than anything else... Where we're not flitting all over the globe we don't have the same pressures but still..?

Further... I'll admit to trying to shift my localized terminology in posts if I think it might help improve the understand-ability of a post. So why not in the supporting documentation?

Jim Albanowski

You're welcome, Scott.

I fear the anwer is No. The VSDecoder library is at . For now a couple of American Diesel files and German Steam files are available in the library.

Are you looking for UK Diesel or Steam sounds?

It may be worth to search on YouTube for "jmri virtual sound decoder".
I once was asked on YouTube to share a VSD file, and I did so. May be others will share, too.

Klaus


Am 04.01.2019 um 12:27 schrieb Scott Rixon:

I think you're onto something Marc.
Mumbles of Infernal Information. Each one with a tab on top.

Steve G.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Thanks..
Has anyone posted any UK VSD files? For any locos? Is their a library??

Thanks.. I'd not found that page! Need to find some more time to have a play.

Cheers,
Scott.

Thanks Ken but that reply just makes it worse. What I'm asking for is phrases that have a clear meaning, never mind their history. At the coal face we just need to know which option to take and what will happen when we do.
Like I said, "Read decoder", "Write changes to file", that sort of thing. I realise this would take a while to work through so in the meantime could we have a little conversion table perhaps?
Looking at the TCS tab for a decoder I'm working with I see the following phrases:
"Read changes on sheet", "Write changes on sheet", "Read full sheet", "Write full sheet"
"Read changes on all sheets", "Write changes on all sheets", "Read all sheets, "Write all sheets".
I thought I might be able to suggest different words but I soon bogged down because I just don't know what each phrase is intended to say. If "Read changes on sheet" actually means (?), "Read decoder changes", then what does "Read changes on all sheets" mean? From a user perspective a decoder does not exist in parts. We can read the decoder and with a bit of help we can read just the changes, but I don't get the distinction implied by the word "all". I've read that in DecoderPro "all" can take a long time. Also do "full" and "all" have the same or different meanings?
Sorry, but I just find this area quite opaque and therefore confusing.
Regards
Peter

Marc,

The question was how to launch SoundPro. You showed the way and it works. I would prefere to copy the SoundPro icon and paste the icon as a Desktop link (as you said in your second post).

In most cases however I access SoundPro with PanelPro >> Tools >> Tables

Audio. This helps me to see wheather the audio objects like buffer,

source or listener are ready for an application to play the sounds.

One player application is Virtual Sound Decoder (VSD), and I think (and may be wrong), people sometimes say SoundPro but are thinking of VSD.

VSD add locomotive sounds to a layout without the need of sound decoders. I'm using Audacity to prepare the sounds (WAV files) for VSD. A SPJ file contains a WAV file for locomotive sound. And Audacity obviously can import a SPJ file.

Just my thoughts on this.

Klaus


Am 03.01.2019 um 23:44 schrieb Marc:

" How do I access soundPro from JMRI"
WIn10:
1 - you open that WINDOW, lower left side
2 - Scroll down to JMRI
3 - Do a right click on SOUNDPRO? and do a Pin to start? or Pin to Taskbar (which is deeper).
Hope I understood your request.
What SPJ files are you talking about.? I downloaded Audacity thinking we were talking DIGITRAX SPJ files.? Clearly not the case.
Marc

Thanks Chris, clearly we can exceed 64 bytes with ESP8266?devices?- your example has 207. Perhaps when the 64 character limit was mentioned, it was with some other device in mind.

I have looked further into the possible inconsistencies between Heads and Masts I mentioned yesterday.?
Flashing is no issue. the xml files for appearances use "flashred" but when a head is included in a mast, the head shows this as "Flashing Red"
Regarding Lunar, it depends on which options you choose in creating the head. Virtual Heads do not have Lunar as an option. If you include that in a Signal Head Controlled Mast, the head appearance becomes null so could be considered as a bug or limitation in the current use of Virtual Heads with Signal Head Controlled Masts.?This digresses a bit from the objective of this discussion but worth mentioning as a reminder when coding for MQTT signal heads that Lunar and Flashing Lunar should be permitted. If we could add flashing frequency to it, I could say the Lunar ticks are on the Mast (apologies to Pink Floyd and everyone reading this, there's someone in my head but it's not me.)

Getting back to business, the objectives here are to define precisely what content and syntax will be created by JMRI for MQTT messages from the information held in JMRI and for sensors, to define the content and syntax of MQTT messages created by a remote sensor when it announces its state so that JMRI can interpret that message to identify which JMRI sensor it is and update its status in JMRI. Then Bob can do the coding.

The current format already in JMRI for turnouts only is /trains/track/turnout/{number} {state}? ?e.g.? ?/trains/track/turnout/27 THROWN? ?
The hardware address is MT{number)? e.g. MT27? where M is the prefix assigned to the MQTT connection and T for Turnouts. The prefix may not always be "M", MQTT connections do not have exclusive rights to the letter M so another connection may already have used "M".?

For the topic, I think there is general acceptance that we retain the existing topic syntax though allow the first two components can be user choice and number can be text of user choice.? I suggest Bob can decide whether or not it should include the two character prefix, currently it doesn't, perhaps it should. Technically, the first two topic levels (trains/track)?are actually the second and third levels, with the top level, the bit before the first slash, being null so that means we could use that extra level if we want without breaking compatibility with the existing structure. Sensors may need to be pinned down a bit more so that JMRI can be programmed to handle it.


For payloads, in the interests of keeping things simple and clear, I'm suggesting the payload be the state (or equivalent) as shown in JMRI,

See below:

On 2 Jan 2019, at 6:39 PM, Peter Ross <peterr@...> wrote:

Could I just say that as a relative newcomer I still find the term "sheet" confusing. You obviously know what you mean but at best the word seems superfluous and at worst confusing. If you mean "read decoder", why not say so?

Because "read sheet" certainly does not mean "read decoder". It means read only those items on the current sheet/(mumble)/tab/(thingy you can see on screen)...

And for "write changes", why not something like "write changes to file".

Because "write changes", certainly does not mean "write changes to file". It means "write changes to decoder".

Read and Write are probably never used in relation to files in JMRI:
- Open and Save are usually used in relation to files.
- Read and Write are probably always used in relation to Decoder CVs.

Read and Write are usually qualified by terms such as changes/full/all/sheet to
indicate the scope of changes.

If I recall correctly "sheet" is mentioned four times with what seem to be four different meanings.

I've never seen more than one meaning for "sheet" in JMRI. Can you explain further?

Dave in Australia

(mumbles) are often called "tabs", particularly in Microsoft and Apple documentation. This probably comes from often being rendered by those platforms like the paper tabs usually attached to the top of real paper sheets and/or folders in a filing cabinet.

The term "sheet" may come from the filing cabinet analogy, or from the term "worksheet" used in Microsoft Excel.

There may be official terminology guidelines but I haven't seen them.
--
Dave in Australia

Marc,

Not at all. The iPhone behaves just like a "real man's camera" (we have those too). The problem is with some image rendering software.

If you hold the iPhone in landscape mode with the main camera lens (we are not considering the selfie camera) in the top corner and the power button at the top, the iPhone considers that the "normal" orientation and sets the EXIF orientation flag to Horizontal Normal. Just like my "real man's camera" when I hold it the right way up.

If I rotate the iPhone 90 degrees clockwise it sets the EXIF orientation flag to Rotate 90 CW. Just like my "real man's camera" when I rotate it 90 degrees clockwise.

If I rotate the iPhone 180 degrees clockwise it sets the EXIF orientation flag to Rotate 180. Just like my "real man's camera" when I hold it upside down.

If I open any of these images with any image processing software I use on my Mac (or use Quick-Look to preview them), they all appear Right Way Up (the Mac software uses the EXIF orientation flag to render the images the way they should be viewed.)

If I drag any of the rotated images (iPhone or "real man's camera") to a Roster Media window in JMRI, they show as if I've been standing on my head or lying on one side.

There are no problems with the iPhone nor the "real man's camera". The problem is that whatever we use to render JPEG images in JMRI (on the Mac at least) ignores the EXIF orientation flag embedded in the image and doesn't render the image in its corrected orientation.

What are Windows and Linux users seeing?
--
Dave in Australia

To add to Ken’s comments below, JMRI is already translated for UK users.

The changes include using railway instead of railroad, wagon instead of car, and spelling color, analogue, catalogue, signalling, neighbour and grey properly, etc. But there might be more than can be done.

See


for more info on this if you’d like to make the translations better.

Bob

On Jan 3, 2019, at 8:27 PM, Ken Cameron <kcameron@...> wrote:


I think it is safe to say that JMRI is produced on the planet, the whole
planet. While the US may have the largest number of supporters, there is a
good number on the other parts of the planet. Some other most frequent
support people on this list are 'down under'. Other wrap around the globe.
The design ideas have always tried to 'think globally' when creating things.
In fact the titles you mention, like 'Write Changes on Sheet' are completely
translated for many different languages. As many of the labels you read are
in fact from a database the gives a translation for each language somebody
has taken the time to figure out the right words for that language.

--
Bob Jacobsen
rgj1927@...

Peter,

I think it is safe to say that JMRI is produced on the planet, the whole
planet. While the US may have the largest number of supporters, there is a
good number on the other parts of the planet. Some other most frequent
support people on this list are 'down under'. Other wrap around the globe.
The design ideas have always tried to 'think globally' when creating things.
In fact the titles you mention, like 'Write Changes on Sheet' are completely
translated for many different languages. As many of the labels you read are
in fact from a database the gives a translation for each language somebody
has taken the time to figure out the right words for that language.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org