Locked
DecoderPro print problems
Still not getting any help here or on the "other" JMRI site. How can I enlarge the font when printing out copies of my loco CV pages? Mine all print so small you need a magnifying glass to read it?? ANYBODY/// Changing font size in preferences doesn't work on these pages. I am not a programmer/coder, just a happy user of DecoderPro. It seems to me as I read answers to other problems I need simplified help as most answers I read here are way above my understanding of the JMRI stuff.\
At one time way back in an early 3. something vrsion of DecoderPro I could get really nice printed pages of the summary with all the CV's and or functions,etc, printed out for each of my locos. They save just fine and when called up they look great, but I normally print them out and keep them in a binder for ready reference. I have tried pasting into WORD but by the time you blow them up to a size to read they pixelate so bad they are all fuzzy. Is there a simple line of code somewhere that controls the font size for these pages/reports? As I noted above, Display/Fonts under Preferences has no effect when printing these pages. Yes they show big on the computer screen but just ant tracks when printing.
Thanks again to anyone here who knows the secret for fixing this, I know it doesn't seem as important as all the issues I read about the other postions of JMRI/DecoderPro but for me, a simple user it is a real hassle.
You folks here seem to be the goto people for this so I'm hoping someone has a moment to get me on the right track.
Sincerely,
Rick Bell
katmedia@live .com
hopefully Yahoo won't strip out my email address......
|
Locked
Re: Odd problems with latest test version 4.9.1 Windows 10
Any takers please? I'm having a others issues but thought I'd start with
these. Ta.
|
Locked
Re: Sensor State Table not Updating
Egbert, ? Yes - it was the preferences box which was not marked "X" , ?unfortunately the earlier documentation I used didn't refer to this requirement. ?Now there's quite a bit to sort out ! ?Very many thanks for your help. ?Best Regards, ? Alan
toggle quoted message
Show quoted text
On Saturday, July 29, 2017, 7:59:11 AM GMT+1, dcc2@... [jmriusers] <jmriusers@...> wrote:
?
Alan, Can you check in JMRI Preferences what you have set as the XpressNet Connection Prefix? If Add Sensor just puts an S in front of the sensor address, that field could be empty and in that case JMRI is not listening to the correct connection. The Sensor Table only shows the state of items present in the table.
You can place an image of the screen on the Yahoo Files area, instead of trying to attach it to a group meassage that will strip it out. Put your name in the file name so we can match the file with this thread.
I can't interpret the Xbus traffic you quote from the Console, but don't expect it to be the cause of your issue.
Egbert
Alan wrote:
I have since updated to 4.8 but this does not resolve the problem. I think the sensors all work ok as I can see their responses in the XpressNet Traffic window, however these responses do not appear in the Sensor Table or layout diagram. This applies to all types of sensors.
The documentation suggests that the system name prefix for Xpressnet sensors is "XS" whereas the "Add process" produced "S", e.g. S575, other than that I cant see what could be wrong.
[Non-text portions of this message have been removed]
#yiv4160105225 #yiv4160105225 -- #yiv4160105225ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv4160105225 #yiv4160105225ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv4160105225 #yiv4160105225ygrp-mkp #yiv4160105225hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv4160105225 #yiv4160105225ygrp-mkp #yiv4160105225ads {margin-bottom:10px;}#yiv4160105225 #yiv4160105225ygrp-mkp .yiv4160105225ad {padding:0 0;}#yiv4160105225 #yiv4160105225ygrp-mkp .yiv4160105225ad p {margin:0;}#yiv4160105225 #yiv4160105225ygrp-mkp .yiv4160105225ad a {color:#0000ff;text-decoration:none;}#yiv4160105225 #yiv4160105225ygrp-sponsor #yiv4160105225ygrp-lc {font-family:Arial;}#yiv4160105225 #yiv4160105225ygrp-sponsor #yiv4160105225ygrp-lc #yiv4160105225hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv4160105225 #yiv4160105225ygrp-sponsor #yiv4160105225ygrp-lc .yiv4160105225ad {margin-bottom:10px;padding:0 0;}#yiv4160105225 #yiv4160105225actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv4160105225 #yiv4160105225activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv4160105225 #yiv4160105225activity span {font-weight:700;}#yiv4160105225 #yiv4160105225activity span:first-child {text-transform:uppercase;}#yiv4160105225 #yiv4160105225activity span a {color:#5085b6;text-decoration:none;}#yiv4160105225 #yiv4160105225activity span span {color:#ff7900;}#yiv4160105225 #yiv4160105225activity span .yiv4160105225underline {text-decoration:underline;}#yiv4160105225 .yiv4160105225attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv4160105225 .yiv4160105225attach div a {text-decoration:none;}#yiv4160105225 .yiv4160105225attach img {border:none;padding-right:5px;}#yiv4160105225 .yiv4160105225attach label {display:block;margin-bottom:5px;}#yiv4160105225 .yiv4160105225attach label a {text-decoration:none;}#yiv4160105225 blockquote {margin:0 0 0 4px;}#yiv4160105225 .yiv4160105225bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv4160105225 .yiv4160105225bold a {text-decoration:none;}#yiv4160105225 dd.yiv4160105225last p a {font-family:Verdana;font-weight:700;}#yiv4160105225 dd.yiv4160105225last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv4160105225 dd.yiv4160105225last p span.yiv4160105225yshortcuts {margin-right:0;}#yiv4160105225 div.yiv4160105225attach-table div div a {text-decoration:none;}#yiv4160105225 div.yiv4160105225attach-table {width:400px;}#yiv4160105225 div.yiv4160105225file-title a, #yiv4160105225 div.yiv4160105225file-title a:active, #yiv4160105225 div.yiv4160105225file-title a:hover, #yiv4160105225 div.yiv4160105225file-title a:visited {text-decoration:none;}#yiv4160105225 div.yiv4160105225photo-title a, #yiv4160105225 div.yiv4160105225photo-title a:active, #yiv4160105225 div.yiv4160105225photo-title a:hover, #yiv4160105225 div.yiv4160105225photo-title a:visited {text-decoration:none;}#yiv4160105225 div#yiv4160105225ygrp-mlmsg #yiv4160105225ygrp-msg p a span.yiv4160105225yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv4160105225 .yiv4160105225green {color:#628c2a;}#yiv4160105225 .yiv4160105225MsoNormal {margin:0 0 0 0;}#yiv4160105225 o {font-size:0;}#yiv4160105225 #yiv4160105225photos div {float:left;width:72px;}#yiv4160105225 #yiv4160105225photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv4160105225 #yiv4160105225photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv4160105225 #yiv4160105225reco-category {font-size:77%;}#yiv4160105225 #yiv4160105225reco-desc {font-size:77%;}#yiv4160105225 .yiv4160105225replbq {margin:4px;}#yiv4160105225 #yiv4160105225ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv4160105225 #yiv4160105225ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv4160105225 #yiv4160105225ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv4160105225 #yiv4160105225ygrp-mlmsg select, #yiv4160105225 input, #yiv4160105225 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv4160105225 #yiv4160105225ygrp-mlmsg pre, #yiv4160105225 code {font:115% monospace;}#yiv4160105225 #yiv4160105225ygrp-mlmsg * {line-height:1.22em;}#yiv4160105225 #yiv4160105225ygrp-mlmsg #yiv4160105225logo {padding-bottom:10px;}#yiv4160105225 #yiv4160105225ygrp-msg p a {font-family:Verdana;}#yiv4160105225 #yiv4160105225ygrp-msg p#yiv4160105225attach-count span {color:#1E66AE;font-weight:700;}#yiv4160105225 #yiv4160105225ygrp-reco #yiv4160105225reco-head {color:#ff7900;font-weight:700;}#yiv4160105225 #yiv4160105225ygrp-reco {margin-bottom:20px;padding:0px;}#yiv4160105225 #yiv4160105225ygrp-sponsor #yiv4160105225ov li a {font-size:130%;text-decoration:none;}#yiv4160105225 #yiv4160105225ygrp-sponsor #yiv4160105225ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv4160105225 #yiv4160105225ygrp-sponsor #yiv4160105225ov ul {margin:0;padding:0 0 0 8px;}#yiv4160105225 #yiv4160105225ygrp-text {font-family:Georgia;}#yiv4160105225 #yiv4160105225ygrp-text p {margin:0 0 1em 0;}#yiv4160105225 #yiv4160105225ygrp-text tt {font-size:120%;}#yiv4160105225 #yiv4160105225ygrp-vital ul li:last-child {border-right:none !important;}#yiv4160105225
|
Locked
Re: Hornby Merchant Navy TTS decoder
Hi, Nigel On 30/07/2017 07:46, Nigel Cliffe nigel.cliffe@... [jmriusers] wrote: Medium term, if the manual is on the Hornby website with the identification CVs described, then it¡¯s very simple to get it added to the TTS file which covers all TTS locos. I'm new at JMRI, so I'd rather not change it myself. (That will change as I get more used to things). The manual's at - Nigel (original writer of the TTS file for JMRI ) Best wishes -- Jane Sullivan Beckenham
|
Locked
Re: Hornby Merchant Navy TTS decoder
99% certain it will be much the same as any other TTS loco. So, short term, just pick one that's close.
Medium term, if the manual is on the Hornby website with the identification CVs described, then it¡¯s very simple to get it added to the TTS file which covers all TTS locos.
- Nigel (original writer of the TTS file for JMRI )
toggle quoted message
Show quoted text
-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: 29 July 2017 18:53
To: jmriusers@...
Subject: [jmriusers] Hornby Merchant Navy TTS decoder
Has anyone got a file for the TTS decoder in the new Hornby Merchant Navy?
[Non-text portions of this message have been removed]
------------------------------------
Posted by: janesullivan@...
------------------------------------
------------------------------------
Yahoo Groups Links
|
Locked
Re: Trouble with Virtual Signals
Bob Z,
It has been a while, but I think you can name and save the custom signal set once you have it defined once.
Bob Bucklew
toggle quoted message
Show quoted text
----- Original Message -----
From: "JMRI users yahoo" <jmriusers@...>
To: "JMRI users yahoo" <jmriusers@...>
Sent: Friday, July 28, 2017 5:18:58 PM
Subject: Re: [jmriusers] Trouble with Virtual Signals
I'm sorry if my latest question wasn't clear. I appreciate the advice regarding layout panels and the like, but my question is about Signal Heads and having icons and Simple Signal Logic stay with the signal head.
I think I found a solution to part of my problem. In the Tools menu there is a item for Simple Signal Logic. It seems that this is where you would create the logic that sticks with the signal head regardless where you place it or how many times it gets used. This is exactly what I was looking for!
The second part of my question is regarding icons. Is there is a way to have the icons stick with the signal head so that each time I select it onto a panel I don't need to change all eight of the icons? That would be a huge time saver!
Thanks!
|
Locked
Hornby Merchant Navy TTS decoder
Has anyone got a file for the TTS decoder in the new Hornby Merchant Navy?
|
Locked
Re: Advertising WiThrottle v2.0 on: pending
UPDATE: I have done some experimentation and have discovered the following:
WiThrottle works only when my iMac is connected to the internet (using Ethernet, of course, because the WiFi facility is occupied with creating a WiFi network for the WiThrottle to use).
Why am I seeing this behaviour? What is the suitable workaround?
Here is my situation: my iMac is located in my Studio at the back of my house, whereas my layout is in my living room, more than 20 feet away and my Ethernet does not reach that far. How do I use WiThrottle when I move my iMac to my living room so it is beside my layout?
Christopher
Winnipeg, Canada
|
Locked
Re: System Console Warning Message
Paul; I only have 2 usb ports to choose from
cu.Bluetooth-Incoming=port &
cu.usbmodem1411
As well if I change to Xpressnet Simulator; I get following System Console message
2017-07-29 09:23:10,856 util.Log4JUtil INFO - * JMRI log ** [main]
2017-07-29 09:23:11,833 util.Log4JUtil INFO - This log is appended to file: /Users/williamseabrooke/Library/Preferences/JMRI/log/messages.log [main]
2017-07-29 09:23:11,834 util.Log4JUtil INFO - This log is stored in file: /Users/williamseabrooke/Library/Preferences/JMRI/log/session.log [main]
2017-07-29 09:23:11,840 apps.AppsBase INFO - DecoderPro version 4.8+Rbe0ff15 starts under Java 1.8.0_131 on Mac OS X x86_64 v10.13 at Sat Jul 29 09:23:11 EDT 2017 [main]
2017-07-29 09:23:12,052 gui3.Apps3 INFO - Starting with profile wmseamac.3f48e951 [main]
2017-07-29 09:23:12,269 node.NodeIdentity INFO - Using jmri-28F0761979C8-3f48e951 as the JMRI Node identity [main]
2017-07-29 09:23:13,885 util.FileUtilSupport INFO - File path program: is /Applications/JMRI/ [main]
2017-07-29 09:23:13,886 util.FileUtilSupport INFO - File path preference: is /Users/williamseabrooke/Library/Preferences/JMRI/wmseamac/profile/jmri-28F0761979C8-3f48e951/ [main]
2017-07-29 09:23:13,886 util.FileUtilSupport INFO - File path profile: is /Users/williamseabrooke/Library/Preferences/JMRI/wmseamac/ [main]
2017-07-29 09:23:13,886 util.FileUtilSupport INFO - File path settings: is /Users/williamseabrooke/Library/Preferences/JMRI/ [main]
2017-07-29 09:23:13,887 util.FileUtilSupport INFO - File path home: is /Users/williamseabrooke/ [main]
2017-07-29 09:23:13,887 util.FileUtilSupport INFO - File path scripts: is /Applications/JMRI/jython/ [main]
Thank you
|
Locked
Re: Sensor State Table not Updating
Alan, Can you check in JMRI Preferences what you have set as the XpressNet Connection Prefix? If Add Sensor just puts an S in front of the sensor address, that field could be empty and in that case JMRI is not listening to the correct connection. The Sensor Table only shows the state of items present in the table.
You can place an image of the screen on the Yahoo Files area, instead of trying to attach it to a group meassage that will strip it out. Put your name in the file name so we can match the file with this thread.
I can't interpret the Xbus traffic you quote from the Console, but don't expect it to be the cause of your issue.
Egbert
Alan wrote:
I have since updated to 4.8 but this does not resolve the problem. I think the sensors all work ok as I can see their responses in the XpressNet Traffic window, however these responses do not appear in the Sensor Table or layout diagram. This applies to all types of sensors.
The documentation suggests that the system name prefix for Xpressnet sensors is "XS" whereas the "Add process" produced "S", e.g. S575, other than that I cant see what could be wrong.
|
Locked
Re: System Console Warning Message
On Jul 28, 2017, at 11:04 AM, wmseapc@... [jmriusers] <jmriusers@...> wrote:
The 8th line in my System Console Message is a warning
"2017-07-28 11:01:15,484 lenz.XNetInitializationManager WARN - Command Station disconnected, or powered down assuming LZ100/LZV100 V3.x [main]" You either have: A command station or interface that isn't getting power A disconnected cable The wrong port selected. My guess is it is the third possibility because the LIUSB does not usually end up with a name like cu.usbmodem1411, which is what the log shows you have configured currently. You probably are looking for a port name that starts "tty-usbserial" followed by an alphanumeric serial number Paul
|
Locked
Re: TCS Indexed CV Problem on JMRI 4.9 amd 4.9.1
Dennis What is the date in the decoder? A date before 30 October 2015 will have problems reading - after that date the decoder read OK. Gerry On 29/07/2017 5:06 AM, dbcherry@... [jmriusers] wrote:
This could be on earlier version of JMRI also, but having issues
reading Indexed CV's on a Wow-121 Steam Ver 3.
On a DCC++ Command station I can 100% read all regular CV's and the
CVT3 Cv's but noe the CVT2 CV's, that all give me a 308 error.
On a Lenz Set100 R3.6, all regular CV's read 100%, but the CV'2's give
me a 310 error and the CVT3's give me a 310 error.
What is the difference between the CVT2 and CVT3 anyway.
Dennis
-- Gerry Hopkins MMR #177 FNMRA Great Northern Downunder NMRA Australasian Region Contest & AP Chairman Web Administrator
|
Locked
Re: Console Log with INFO message regarding JOAL
INFO messages are for informing you in passing about something. Sometimes they¡¯re too much information. This one is telling you which audio libraries JMRI found from looking around your computer. It doesn¡¯t need them yet if you¡¯re not using sound, but the code was written to find them when it could. Bob On Jul 28, 2017, at 2:09 PM, Marshall readingrr2103@... [jmriusers] <jmriusers@...> wrote:
I have been noticing the following entry in the console log.
timestamp audio.JoalAudio Factory INFO Initialised JOAL using OpenAL: vendor ¨C OpenAL Community Version ¨C 1.1 ALSOFT 1.15.1 [Listed Table Generation]
It comes after the panel is loaded and when the first train is run.
Can someone tell what this is. As far as I know we have no audio built in the panels
Using JMRI Version 4.8 on Windows 10 with Java 1.8.0_131 -- Bob Jacobsen rgj1927@...
|
Locked
Odd problems with latest test version 4.9.1 Windows 10
I loaded the latest test to see whether the XML parse was fixed, but got an error still - I've been in and replaced odd <comment/> fields with <comment><.comment> which worked - but then I got a parse error for <metric>. Remocing these also passed. But this is the strange thing, I had played with path metrics by right clicking on a block and then using Edit, then Create/Edit to access the block fields, where there is a tab for Routing, where a metric value was entered to try different things. However, as this caused a problem, I looked in the Block table and could see no tab for entering this data that way. Are metrics still implemented or has something been missed, or am I missing something?!
Also, NX routing seems a bit broken - before if a route could not be set, you (if option selected) were prompted to stack the route (a bit flaky at times though), Now, the turnouts get changed even before offering to stack or whatever, meaning that routes are set regardless of any situation, including block occupancy, which is very bad and a particularly silly bug! In addition...
I had noted previously that the NX routing data displayed from Layout Editor, Tools, Entry Exit option disappears on restarts. This seems to indicated all your previous hard work getting NX sensors to do the right thing simply vanishes into thin air... but they still seem to work (sic!) even though nothing is displayed. This is not helpful at all, and I cannot fathom why this is the way it is. Auto-creating NX entries generates a lot of false entries that are logically impossible so many have to be deleted. The Double Crossover seems to allow path logic that means a train goes through an acute angle to get aound the point to come back the way to the place its just come from when deployed on a double track main line! I can find nothing that allows path corrections, and even fixing NX senors as best I can, neither routes, signal mast pairs or anything else seems to mitigate against NX believing theres a way through these that is surely physically wrong, and therefore logically silly, for the type of track it is.
Looking at the XML I am conused by the path data I see (or rther don't), but cannot find any explanation as to how to resolve these issues either in help or by searching. A simple explanation somewhere of todir and fromdir numeric values would be useful maybe? I'm happy to edit the XML if needed..... just no idea as to how to start with this issue.
I feel I cannot be the only person seeing this.... so I must be in error. Help please!
Thanks!
John
|
I don't know if anyone has run across this. After I upgraded to latest Windows 10 version DecoderPro locked up. I'm using the program for programming only and the computer is connected to a SPROG III. When start the program the roster comes up and I can select a locomotive to program and go through all the tabs. When I select a tab I can change the setting but when I click write to sheet nothing happens and the only way I can get out of the program is through the Task Manager. The latest version of JMRI and Java is installed.
Before you ask me to do some programming checks I'll have to tell that I'm not a programmer and you would have to guide me step by step. I have checked computer, a HP laptop, and found several old versions of JAVA which I can't uninstall because of missing JRE files associated with those old programs. My guess is that the old JAVA updates may cause the problem. Any help would be appreciated,
Al Babinsky
Sent from my Verizon HTC Smartphone
|
Locked
Re: Multiple Openlcb Conections
Ken,
The problem occurs when attempting to create a sensor or turnout in the node configuration window - not the table view for sensors or turnouts.
The two connections are for geographic separation of the two CAN segments.
Regards
Nom
|
Locked
Re: Locobuffer locking up from data overload?
Steve,
If it is going to be a problem defining the Loconet commands for each aspect using existing JMRI signal heads, you can define them in CATS designer and CATS will create JMRI signal heads when you load your CATS panel. You will need to know what Loconet "addresses" are required for each signal head aspect. Page 7 of the SE8C instruction book has the mapping for board ID 1 and page 8 summarizes the mappings for board IDs 1 thru 12. The way of looking at an SE8C is not as 8 signal heads, but as 32 "lights", spread across 8 "zones". Any "light" can be selected with a Loconet address and a throw or close selection, all done through a JMRI LT turnout. So, if you wired your signals as described in the Digitrax SE8C manual, then the "green" is turned on in the designer Signal Head Definitions window, green sub-pane, by selecting Decoder = LT, Address = the address for the board ID and zone number, check Close. Red is turned on by the same Decoder and Address fields, but checking Throw. Yellow is the same Decoder information, but the address is the green address + 1, and checking Throw. Flashing red is the yellow address, but checking Close. Do not check Off Command (the SE8C automatically turns off a color when a new one is selected) and do not check Software Flashing (the Se8C will handle the flashing).
Rodney
__________________________________________________________________________________________
Steve,
I don't think that it will be easy with existing JMRI signal head "type" definitions.
The SE8c uses an odd encoding of two turnout addresses and both states of each turnout. It uses a "last turnout command" determines the output state. JMRI's SE8c signal head type understands this behavior. Other JMRI signal types may or may not be able to handle this type of operation.
One that seems promising is the LDT LS-DEC signal head type. With this signal head type, you may define a unique specific turnout and its state for each of the possible color/flashing/dark possibility. If one defines "bogus" turnouts, such as "internal" turnouts, for those aspects which are not reachable on a given SE8c, then one might "get lucky". One would also need to define a custom "JMRI signaling system" that matches the available aspects.
(For the "bogus" turnouts, I would recommend a unique "internal" turnout+state for each "unwanted" aspect, so that a wayward change on one signal head does not confuse other signal heads.)
None of the other JMRI "signal head type"s seem to come close to the requirements of the SE8c board.
If this JMRI "signal head type" cannot fit the bill, then it will be necessary to code up a new signal head type to support the SE8c in "fourth aspect is flashing red" mode. A new JMRI "signal head type" would be the "ideal" way, especially if the code would strictly limit use to "JMRI signal systems" which did not include any "dark" or "flashing green" or "flashing yellow" aspects.
Regards,
Billybob
|
Locked
Re: JRMI 4.6 failure to recognize an Atlas dual mode decoder
Hi Michael, If every read returns 123, you will find you are not using the hardware. Instead, you're accessing the simulator. You need to check your defaults! (Please don't ask me how I know) Wouter On 28 July 2017 at 21:51, michael97303@... [jmriusers] < jmriusers@...> wrote:
Hi,
I gave up on 4.6. I uninstalled it and reinstalled the old 3.x I had on a
thumb drive. It still gave me issues, but it did recognize the Atlas Dual
Mode decoder in the test engine, but when I went to read and then write,
the system said there was no locomotive. So, I gave up again. I have now
upgraded to the new 4.8 and it does not work either! Regardless of which
locomotive I place onto our programming track which is connected to our
computer via SP|PROG II, I get the same response when I tell the program to
read the type from the Decoder is: Found mfg 123 (Massoth Elektranik, GmbH)
version 123, no such decoder defined.
The two locomotives I have placed onto the programming track are, first,
the initial test engine which I used all along that has an Atlas Dual Mode
Decoder. The second one is a Bachmann. Both locomotives give me the
response above.
I am not an advanced user. We have Windows 10 for an operating system.
Help please, step by step for a clueless user. Thank you.
Michael
|
Locked
Re: Trouble with Virtual Signals
I'm sorry if my latest question wasn't clear. I appreciate the advice regarding layout panels and the like, but my question is about Signal Heads and having icons and Simple Signal Logic stay with the signal head.
I think I found a solution to part of my problem. In the Tools menu there is a item for Simple Signal Logic. It seems that this is where you would create the logic that sticks with the signal head regardless where you place it or how many times it gets used. This is exactly what I was looking for!
The second part of my question is regarding icons. Is there is a way to have the icons stick with the signal head so that each time I select it onto a panel I don't need to change all eight of the icons? That would be a huge time saver!
Thanks!
|
Locked
Console Log with INFO message regarding JOAL
I have been noticing the following entry in the console log.
timestamp audio.JoalAudio Factory INFO Initialised JOAL using OpenAL: vendor ¨C OpenAL Community Version ¨C 1.1 ALSOFT 1.15.1 [Listed Table Generation]
It comes after the panel is loaded and when the first train is run.
Can someone tell what this is. As far as I know we have no audio built in the panels
Using JMRI Version 4.8 on Windows 10 with Java 1.8.0_131
Thank you,
Marshall Wales
Scottsdale Model Railroad Historical Society
[Non-text portions of this message have been removed]
|
RickyB
Christopher Robinson
wmseapc
Egbert Broerse
Bob Jacobsen