Locked
Re: Trouble with JMRI to JMRI client/server
Yes, that's a good setup.
I don't think you'll overload anything (other than the track bus), but If you want to distribute the load more, you could have a locobuffer-usb on each RaspberryPi, and take a bit more off of the central machine.
--SteveT
|
Locked
Missing Decoder Listings
I just Purchased two new decoders, One a Zimo MX616N and a ESU Lokpilot FX Nano 8 Pin. Neither of these will self identify under JMRI.
The Zimo will identify many different decoders but not the MX616N, If I select one that I think is closest to it and read all CV's It will read almost all, but will leave three CV's?unread.?That questions my choice of decoder. Do I need to create a new definition file?
On the Lokpilot I see the F1 Light Flash, when it is being read,?but then I get a no locomotive present. Reading the documentation just confuses me more.
Can anyone give me some insight?how to programing these decoders.
I am using JMRI Test ver 15-1
Also I have a MRC 1833 Sound Decoder that I was trying to create a Decoder definition file. I am?using JEdit. I used a MRC 1927 File to begin with as it had most of the cv's that I needed. It will let me make changes to the file but will not let me save it.
|
Locked
Re: ESU Loksound 4.0 decoder - Error 303 when 'Read All Sheets'
Thanks Dave¡I¡¯ll give that a try tomorrow and report back to the group. ? Jim
|
Locked
Re: Decoder Pro problems
I personally like the terminology as it is. It is clear and concise. Changing it would just complicate matters for the thousands of users who already have learned to navigate the system.? And, imho, there are far more pressing things for the developers to spend their voluntary time on.? Thank you to all who have put so much time and effort into this awesome product. Tom Wilson
Colorado Springs, CO
On Fri, Jan 4, 2019, 3:42 PM Bob Jacobsen < rgj1927@... wrote:
> On Jan 4, 2019, at 2:09 PM, Peter Ross <peterr@...> wrote:
>
> Thank you Bob, that has been quite helpful. For example, based on using the Help explanations, why not put "Recover data from the decoder" instead of "Read changes on sheet¡±?
Because that¡¯s not what it does. Your phrase hasn¡¯t captured that it¡¯s only ¡°recover(ing)¡± _some_ of the data, and which data will be recovered.
> And something like, "Write only what has changed" instead of "Write changes on sheet¡±.
Because that¡¯s not what it does. It only writes what was changed _on_this_sheet_.? Changes that have been made on other sheets are not written by that button.? There is another button, which uses the word ¡°all¡± for those. You also made it longer by changing ¡°changes¡± to ¡°only what was changed¡±.? Maybe ¡°changes" is too short, so "changed values" might do, but ¡°what was changed¡± is verbose and ¡°only¡± is redundant:? _Everything_ only does what it does.
> Likewise, "Read all from the decoder" instead of "Read changes on all sheets¡±?
Because that¡¯s not what it does. It only reads what was _changed_.?
> And, "Write all to the decoder"?
> So (within the limitations of this text format), we could have (note preamble to each row of buttons):
> "For CVs on this pane only: Recover values from decoder/Write changes to decoder/Read all from decoder/Write all to decoder."
> "For the entire range of CVs: Recover values from decoder/Write changes to decoder/Read all from decoder/Write all to decoder.¡±
What¡¯s the difference between ¡°recover¡± and ¡°read¡±?? Perhaps I¡¯m not understanding some change in how the program works that you¡¯re proposing. (I¡¯m also not sure what ¡°entire range of CVs¡± means:? What range? The visible things on the page are variables, not CVs:? They may or may not correspond to a particular set of CVs that appear on other pages too)
In general, it¡¯s less confusing if a button says what it does.? Having two buttons with exactly the same language right over each other that do different things is not generally viewed as quick & easy to understand:
Necktie? ? ? ? ? ? ? ? ? [Put On]? ? [Take Off]
All Clothes? ? ? ? ? ? ?[Put On]? ? [Take Off]
Which button do I press when I get on the bus home? (.c.f one of my favorite Farside cartoons about UI design: )
Bob
--
Bob Jacobsen
rgj1927@...
|
Locked
Re: Decoder Pro problems
Hood = Bonnet
Fender = Wing (as well as a guitar)
Trunk = Boot
|
Locked
Re: Decoder Pro problems
On Jan 4, 2019, at 2:09 PM, Peter Ross <peterr@...> wrote:
Thank you Bob, that has been quite helpful. For example, based on using the Help explanations, why not put "Recover data from the decoder" instead of "Read changes on sheet¡±? Because that¡¯s not what it does. Your phrase hasn¡¯t captured that it¡¯s only ¡°recover(ing)¡± _some_ of the data, and which data will be recovered. And something like, "Write only what has changed" instead of "Write changes on sheet¡±. Because that¡¯s not what it does. It only writes what was changed _on_this_sheet_. Changes that have been made on other sheets are not written by that button. There is another button, which uses the word ¡°all¡± for those. You also made it longer by changing ¡°changes¡± to ¡°only what was changed¡±. Maybe ¡°changes" is too short, so "changed values" might do, but ¡°what was changed¡± is verbose and ¡°only¡± is redundant: _Everything_ only does what it does. Likewise, "Read all from the decoder" instead of "Read changes on all sheets¡±? Because that¡¯s not what it does. It only reads what was _changed_. And, "Write all to the decoder"?
So (within the limitations of this text format), we could have (note preamble to each row of buttons):
"For CVs on this pane only: Recover values from decoder/Write changes to decoder/Read all from decoder/Write all to decoder."
"For the entire range of CVs: Recover values from decoder/Write changes to decoder/Read all from decoder/Write all to decoder.¡± What¡¯s the difference between ¡°recover¡± and ¡°read¡±? Perhaps I¡¯m not understanding some change in how the program works that you¡¯re proposing. (I¡¯m also not sure what ¡°entire range of CVs¡± means: What range? The visible things on the page are variables, not CVs: They may or may not correspond to a particular set of CVs that appear on other pages too) In general, it¡¯s less confusing if a button says what it does. Having two buttons with exactly the same language right over each other that do different things is not generally viewed as quick & easy to understand: Necktie [Put On] [Take Off] All Clothes [Put On] [Take Off] Which button do I press when I get on the bus home? (.c.f one of my favorite Farside cartoons about UI design: ) Bob -- Bob Jacobsen rgj1927@...
|
Locked
Re: Decoder Pro problems
I had to think about it for a few seconds when i came across the terminology in JMRI. Then realised. Think of each decoder as a booklet or loose leaf folder of instructions. These are grouped into sheets in this folder. Each sheet of instructions (or CV's) can be read or written separately, as well as a whole folder. Simples
|
Locked
Re: Decoder Pro problems
Just internally translate 'Sheet" to "Tab" or "current page with data".
Like when the folks across the pond say 'Bonnet" you think "Hood". (Or is that "Trunk"? Car part anyway.)
And 'Fair Dinkum" means happy Aussie or some such.
Any new company or group has its own terminology. Learn the lingo and you get the precise meaning.
Thomas
DeSoto, TX
|
Locked
Re: JMRI Not Identifying Locomotives Properly
That would be the railcom that I turn off in all my Loksound decoders.
Only a small subset of decoders have that feature, and older decoders of the same brand may not work the same..And we never throw out a working decoder, right?
You are asking for a feature that cannot be retrofitted, and that the Decoder makers see no profit in providing.
At the Club ( with hundreds of roster entries) we make use of the Owner data field. If you get duplicate matches, look at the owner.
And if you have more than one copy of a Lok learn how to renumber the thing. (I have about 6 duplicates on that list).
Someone years ago suggested using CV 105 & 106 as extra match fields. Most NMRA decoders have those. (more than have RailCom) Did that fall out?
The user would have to put data in those CVs, but they are right there on the basic sheet. Maybe too easy?
Thomas
DeSoto, TX
|
Locked
Re: Trouble with JMRI to JMRI client/server
[If JMRI is running on an RPi and talking to the layout via LocoNetOverTcp, there¡¯s no need for a panel to be open on the main machine. It can be opened independently on the client RPi (or not). As far as that client is concerned, it thinks it¡¯s directly connected to the layout and can do whatever it wants independently.
If you¡¯re talking about LayoutEditor panels, you have to be a bit careful because they¡¯re also a way to instantiate layout _logic_. You want some machine, but only one machine, to be running the signals, for example.]
So what it appears I can do is have the 'dispatcher' JMRI instance run with its LayoutEditor panels for real time and linkage.? PanelEditor panels on Pi ZX's with touch screens with their own JMRI instance(s).? As long as the switch addresses (tables) are congruent across all the instances (back end a front end of the yards have the same addresses - no conflict with the mainline). No signaling in the yards.??
The single Loconet-USB at the dispatcher station should not get overrun?
One benefit of this is that the main 'layout' xml file gets smaller (currently ~25k lines) and making changes for UI or operations at a particular area can be done independently?
Thanks for all your assistance,
Martin Booker
|
Locked
Re: Decoder Pro problems
Thank you Bob, that has been quite helpful. For example, based on using the Help explanations, why not put "Recover data from the decoder" instead of "Read changes on sheet"? And something like, "Write only what has changed" instead of "Write changes on sheet". Likewise, "Read all from the decoder" instead of "Read changes on all sheets"? And, "Write all to the decoder"?
So (within the limitations of this text format), we could have (note preamble to each row of buttons):
"For CVs on this pane only: Recover values from decoder/Write changes to decoder/Read all from decoder/Write all to decoder."
"For the entire range of CVs: Recover values from decoder/Write changes to decoder/Read all from decoder/Write all to decoder."
Regards
Peter
|
Dave
The miss understanding is probably because we are upside down and
see things differently!
Gerry
On 5/01/2019 7:15 am, Dave Heap wrote:
It seems my antipodean sense of humour/satire/frustration gets lost other side of the pond.
Infernals is a play on words, describing the consequences and support nightmare created by the unfortunate code decision that caused connection preferences to be set to Internal if hardware was temporarily absent.
Here is the text snippet I usually posted in response to this problem:
"If you get "Found mfg 123 (Masoth Electronic, GMBH) version 123; no such decoder defined.", and/or all CVs return a value of 123 and long address 15,227 it is 100% certain that you cannot communicate with the decoder and that one of two possibilities have happened:
1) Preferences->Defaults has Service Programmer (and possibly other items) set to Infernal.
2) Preferences->Connections has System Connection set to Simulator.
Possibility (1) is the most likely. It would most likely have occurred due to a previous failure to open a connection. If there is no alternative to Infernal, you currently have a problem with the connection to your DCC system and you need to resolve the connection problem before proceeding. If an alternative is available select that, restart JMRI and try again.
Warning, the Infernal problem can happen again in the future if you have any connection problems. See comments at:
/g/jmriusers/message/153294
This has hopefully been fixed in JMRI V4.14"
--
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder
NMRA Australasian Region
Contest & AP Chairman
Web Administrator
|
Locked
Re: ESU Loksound 4.0 decoder - Error 303 when 'Read All Sheets'
Try "Read Full Sheet" on the CVs pane instead. 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" until no red items remain.
Hint: Click on the Status column until you see a down arrow. All the Red items will be at the top.
--
Dave in Australia
toggle quoted message
Show quoted text
On 5 Jan 2019, at 7:46 AM, James S. Brown <brown3980@...> wrote:
This is my first adventure with an ESU decoder so I¡¯m hoping someone can pitch in and maybe provide a solution. I added the locomotive to my Roster and then selected ¡®Read All Sheets¡¯ using Direct Byte. As I was told to expect from a few others, reading CV¡¯s from LokSound decoders can be a bit of a slow and painful process but nonetheless it seemed to be crunching through them. However, it then reached a point where an Error 303 cropped up and continued to do so.
|
1) From my Concise Oxford Dictionary 8th Edition, 1990:
infernal adj. 1?a of hell or the underworld b hellish, fiendish 2 detestable, tiresome
I can think of no better description of the situation we found ourselves in!
2) Who hasn't heard a diehard steam enthusiast refer derisively to the "Infernal Combustion Engine" (diesel) as it supplanted the "External Combustion Engine" (steam)?
toggle quoted message
Show quoted text
On 5 Jan 2019, at 7:15 AM, Dave Heap < dgheap@...> wrote: It seems my antipodean sense of humour/satire/frustration gets lost other side of the pond.
Infernals is a play on words, describing the consequences and support nightmare created by the unfortunate code decision that caused connection preferences to be set to Internal if hardware was temporarily absent.
Here is the text snippet I usually posted in response to this problem:
"If you get "Found mfg 123 (Masoth Electronic, GMBH) version 123; no such decoder defined.", and/or all CVs return a value of 123 and long address 15,227 it is 100% certain that you cannot communicate with the decoder and that one of two possibilities have happened:
1) Preferences->Defaults has Service Programmer (and possibly other items) set to Infernal.
2) Preferences->Connections has System Connection set to Simulator.
Possibility (1) is the most likely. It would most likely have occurred due to a previous failure to open a connection. If there is no alternative to Infernal, you currently have a problem with the connection to your DCC system and you need to resolve the connection problem before proceeding. If an alternative is available select that, restart JMRI and try again.
Warning, the Infernal problem can happen again in the future if you have any connection problems. See comments at:
/g/jmriusers/message/153294
This has hopefully been fixed in JMRI V4.14"
--
Dave in Australia
|
You should not have any problems as the Econami is fully supported by decoderpro and since 4.12 is a recent version so you should be good.?
Pete?
toggle quoted message
Show quoted text
On Jan 4, 2019, at 4:06 PM, Bob McClain via Groups.Io < mcclainbob55@...> wrote: I am using Decoder Pro 4.12, Windows 7 and a Sprog II with an isolated programming track.? I recently purchased an Athearn RTR SD-50 with an Econami sound decoder.? When I go to make a new roster entry will I have any problem with Decoder Pro recognizing that decoder in that engine?? This is my first Econami decoder equipped loco and I want to know if I am going to have to jump thru any special hoops.
Thanks,
Bob
|
I am using Decoder Pro 4.12, Windows 7 and a Sprog II with an isolated programming track.? I recently purchased an Athearn RTR SD-50 with an Econami sound decoder.? When I go to make a new roster entry will I have any problem with Decoder Pro recognizing that decoder in that engine?? This is my first Econami decoder equipped loco and I want to know if I am going to have to jump thru any special hoops.
Thanks,
Bob
|
Locked
ESU Loksound 4.0 decoder - Error 303 when 'Read All Sheets'
Good morning¡ ? I have just received a stunning new Sn3 Shay from the fine folks at PBL which is equipped with a LokSound Ver. 4.0 sound decoder. I have JMRI installed on a MS Surface Pro 3 running the latest version of Windows 10 Professional and am interfacing with a program track through a Lenz LI-USB and an LZV100, both running the most recent version 3.6 Lenz software. The LI-USB connection and interface is solid and functional as I have programmed numerous Tsunami 2200 decoders over the past months. ? This is my first adventure with an ESU decoder so I¡¯m hoping someone can pitch in and maybe provide a solution. I added the locomotive to my Roster and then selected ¡®Read All Sheets¡¯ using Direct Byte. As I was told to expect from a few others, reading CV¡¯s from LokSound decoders can be a bit of a slow and painful process but nonetheless it seemed to be crunching through them. However, it then reached a point where an Error 303 cropped up and continued to do so. ? Any ideas on where I might look for the root cause of this issue? I have uploaded a short video illustrating the issue on my OneDrive which is ? TIA for any wisdom and help! ? Jim
|
Locked
Re: MQTT Connection in JMRI
Andy,
There are no dumb questions!
When you look at the 3-way turnout's hardware itself, there are 2 sets of switch points and they need to move, Thrown or Closed. 2 Tortoises, 2 servos, 2 manual gadgets or 2 something elses. So, yes, in JMRI it is currently done with 2 turnouts. Fairly easy to use Routes in JMRI to control the thrown and close of the needed turnouts to get you to the 1st, 2nd or 3rd path by activating a sensor. So, if we put Routes in MQTT, then the relevant subscribers could be told to do something when topic DFW/clublayout/module001/yardladder/route gets a message like "3".
MQTT is not a wireless protocol, TCP/IP is all you need. It became very popular with IOT devices, and that gave it the wireless flavor. The fear about the adjacent layouts being controlled by the same MQTT subscription will need to be just as you would if they were DCC controlled accessories on the same command station. If two modules both use the same DCC address (example #145) for a turnout, both will move. For an MQTT implementation, DFW/clublayout/module001/turnout002 would not interfere with DFW/clublayout/module006/turnout002 or myownlayout/module001/turnout002, if they where to connect to the same MQTT broker. And then of course, JMRI would also need to have all the turnouts in the same table, and thus unique as well. (One of the smart things in LCC/OpenLCB is the 64-bit addressing that would help keep all LCC devices on the planet unique.)
Back to the wired versus wireless question, with a NodeMcu now costing , I do not know how a "wired" Ethernet implementation would beat that! Noise is a good topic, but not for this thread, this is MQTT in JMRI, and not a "wireless" thread.
Speed
|
Locked
Re: For Andrew (Andy) and his Walthers GP7
UPDATE: Thank you!
Thanks to all who assisted me in getting over the initial hump. It was a process full of infernal anguish! I am now using my PR4 and JMRI and have put several locos in my roster. I was definitely banging my head against the wall trying to program from the DCS51 without power boosted!
One question regarding my (canary in the coal mine) Walthers proto GP7. I changed the dcc address to the road number (3400) but the DCS51 is only seeing it as 34. Is there a 2 digit vs 4 digit setting in operations mode for the DCS51? I know there is when programming. Also, when entering data on the basic tab, there were two instances where JMRI assigned a short dcc address of 72 to this loco. That is a number i never entered. Any thoughts on where it came from or why dcs51 is only seeing 34 instead of 3400?
On Thu, Jan 3, 2019 at 10:38 PM Marc < forfoum@...> wrote: The PR3 and PR4 are internally rectified by a 4 diode bridge.? AC or DC will work fine. Inverted DC will not affect it.? The high Amp makes no difference here as the voltage out to the terminals is controlled and limited by resistors. Just don't short the terminals together.?
Like I mentioned , many use 18Volt 4 or 5 AMP power packs with there PR3 or PR4. People saying the sky will fall are wrong.
You did fine. IT will read the CV's that are in the definition file and nothing else.
For the CSV file. In your GP7 Roster screen, far left "FILE "? Then EXPORT, Then CSV file... Give it a name (GP 7 Walt)? and save it. Notice WHERE it ends up so you can grab it and Email it.
Marc
|
Locked
Re: Roster Images Upside Down
Simply saving with no EXIF data doesn't help at all unless the software has actually read, rotated and resaved the image (usually a lossy procedure for JPEG files).
--
Dave in Australia
toggle quoted message
Show quoted text
On 5 Jan 2019, at 4:47 AM, whmvd <vandoornw@...> wrote:
Maybe the image is saved with no EXIF-data at all, which would also solve it for you.
|
James S. Brown
SwissChris
Bob Jacobsen
Andrew Roberts