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: How Engine driver resend command if not feedback from web server?
Randall Wood
If the ESP-1 message is being sent to the web server, and not the WiThrottle server, then your problems would be explained purely by that misconfiguration on your end.
Do note that for DCC throttle commands, there is no real two-way communication* between the throttle and the controlled locomotive; that¡¯s not built into the NMRA DCC protocol, meaning JMRI can¡¯t ensure there is two-way communication either. The web server *is not* used by Engine Driver to control locomotives, but is used to get roster entry pictures if present. JMRI apps (DecoderPro, PanelPro) contains both a web server and WiThrottle server. * RailCom and Digitrax Transponding provide some exceptions to this On Mar 6, 2018, at 04:33, despxkdcc@... [jmriusers] <jmriusers@...> wrote: [Non-text portions of this message have been removed] |
|
Locked
Re: Decoder Pro is exceptionally sluggish
Hi Ken,
toggle quoted message
Show quoted text
I have no pictures or anything on the roster as I am just starting with the programme and I still can't read the decoder so there's a problem somewhere that I'm missing. Since I've up dated to 4.11.3 the start up time is 5-6 seconds, which is excellent. It's the reading from decoders that is now the problem - see the reply I sent to Dave a moment ago. Regards, GeoffB On Monday, 5 March 2018, 13:05:17 GMT, 'Ken Cameron' kcameron@... [jmriusers] <jmriusers@...> wrote:
? Geoff B , Here is another way that DecoderPro (or the roster window) can be made very slow to start. Are you including pictures in the roster entry? How big are those pictures? When JMRI is building the roster list page, it has to convert all the pictures in the roster to the sizes it need for the display. I found a club that had odd problems that turned out to be 600 locos in the roster and about 500 of them had pictures. The problem was the pictures were about 5M images (nice camera). It was taking many minutes for that page to get built. Problem is that any other windows of JMRI will be inactive while that is being build. While we are looking into ideas to handle this better, I suggest that the pictures be 100k size or less to avoid slow opening of the roster list. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org #yiv7561838812 #yiv7561838812 -- #yiv7561838812ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv7561838812 #yiv7561838812ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv7561838812 #yiv7561838812ygrp-mkp #yiv7561838812hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv7561838812 #yiv7561838812ygrp-mkp #yiv7561838812ads {margin-bottom:10px;}#yiv7561838812 #yiv7561838812ygrp-mkp .yiv7561838812ad {padding:0 0;}#yiv7561838812 #yiv7561838812ygrp-mkp .yiv7561838812ad p {margin:0;}#yiv7561838812 #yiv7561838812ygrp-mkp .yiv7561838812ad a {color:#0000ff;text-decoration:none;}#yiv7561838812 #yiv7561838812ygrp-sponsor #yiv7561838812ygrp-lc {font-family:Arial;}#yiv7561838812 #yiv7561838812ygrp-sponsor #yiv7561838812ygrp-lc #yiv7561838812hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv7561838812 #yiv7561838812ygrp-sponsor #yiv7561838812ygrp-lc .yiv7561838812ad {margin-bottom:10px;padding:0 0;}#yiv7561838812 #yiv7561838812actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv7561838812 #yiv7561838812activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv7561838812 #yiv7561838812activity span {font-weight:700;}#yiv7561838812 #yiv7561838812activity span:first-child {text-transform:uppercase;}#yiv7561838812 #yiv7561838812activity span a {color:#5085b6;text-decoration:none;}#yiv7561838812 #yiv7561838812activity span span {color:#ff7900;}#yiv7561838812 #yiv7561838812activity span .yiv7561838812underline {text-decoration:underline;}#yiv7561838812 .yiv7561838812attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv7561838812 .yiv7561838812attach div a {text-decoration:none;}#yiv7561838812 .yiv7561838812attach img {border:none;padding-right:5px;}#yiv7561838812 .yiv7561838812attach label {display:block;margin-bottom:5px;}#yiv7561838812 .yiv7561838812attach label a {text-decoration:none;}#yiv7561838812 blockquote {margin:0 0 0 4px;}#yiv7561838812 .yiv7561838812bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv7561838812 .yiv7561838812bold a {text-decoration:none;}#yiv7561838812 dd.yiv7561838812last p a {font-family:Verdana;font-weight:700;}#yiv7561838812 dd.yiv7561838812last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv7561838812 dd.yiv7561838812last p span.yiv7561838812yshortcuts {margin-right:0;}#yiv7561838812 div.yiv7561838812attach-table div div a {text-decoration:none;}#yiv7561838812 div.yiv7561838812attach-table {width:400px;}#yiv7561838812 div.yiv7561838812file-title a, #yiv7561838812 div.yiv7561838812file-title a:active, #yiv7561838812 div.yiv7561838812file-title a:hover, #yiv7561838812 div.yiv7561838812file-title a:visited {text-decoration:none;}#yiv7561838812 div.yiv7561838812photo-title a, #yiv7561838812 div.yiv7561838812photo-title a:active, #yiv7561838812 div.yiv7561838812photo-title a:hover, #yiv7561838812 div.yiv7561838812photo-title a:visited {text-decoration:none;}#yiv7561838812 div#yiv7561838812ygrp-mlmsg #yiv7561838812ygrp-msg p a span.yiv7561838812yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv7561838812 .yiv7561838812green {color:#628c2a;}#yiv7561838812 .yiv7561838812MsoNormal {margin:0 0 0 0;}#yiv7561838812 o {font-size:0;}#yiv7561838812 #yiv7561838812photos div {float:left;width:72px;}#yiv7561838812 #yiv7561838812photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv7561838812 #yiv7561838812photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv7561838812 #yiv7561838812reco-category {font-size:77%;}#yiv7561838812 #yiv7561838812reco-desc {font-size:77%;}#yiv7561838812 .yiv7561838812replbq {margin:4px;}#yiv7561838812 #yiv7561838812ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv7561838812 #yiv7561838812ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv7561838812 #yiv7561838812ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv7561838812 #yiv7561838812ygrp-mlmsg select, #yiv7561838812 input, #yiv7561838812 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv7561838812 #yiv7561838812ygrp-mlmsg pre, #yiv7561838812 code {font:115% monospace;}#yiv7561838812 #yiv7561838812ygrp-mlmsg * {line-height:1.22em;}#yiv7561838812 #yiv7561838812ygrp-mlmsg #yiv7561838812logo {padding-bottom:10px;}#yiv7561838812 #yiv7561838812ygrp-msg p a {font-family:Verdana;}#yiv7561838812 #yiv7561838812ygrp-msg p#yiv7561838812attach-count span {color:#1E66AE;font-weight:700;}#yiv7561838812 #yiv7561838812ygrp-reco #yiv7561838812reco-head {color:#ff7900;font-weight:700;}#yiv7561838812 #yiv7561838812ygrp-reco {margin-bottom:20px;padding:0px;}#yiv7561838812 #yiv7561838812ygrp-sponsor #yiv7561838812ov li a {font-size:130%;text-decoration:none;}#yiv7561838812 #yiv7561838812ygrp-sponsor #yiv7561838812ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv7561838812 #yiv7561838812ygrp-sponsor #yiv7561838812ov ul {margin:0;padding:0 0 0 8px;}#yiv7561838812 #yiv7561838812ygrp-text {font-family:Georgia;}#yiv7561838812 #yiv7561838812ygrp-text p {margin:0 0 1em 0;}#yiv7561838812 #yiv7561838812ygrp-text tt {font-size:120%;}#yiv7561838812 #yiv7561838812ygrp-vital ul li:last-child {border-right:none !important;}#yiv7561838812 [Non-text portions of this message have been removed] |
|
Locked
Re: Decoder Pro is exceptionally sluggish
Hello Dave,
toggle quoted message
Show quoted text
The start up time for the programme is now down to around 5-6 seconds - excellent. The decoders did state "massoth" on read from decoder and when the correct decoder was selected I did notice that it read "15227". As a new user, I'm starting to learn where and what all the errors are!! Yes, the preferences did read as internal for the service and ops programmers. I just tried altering the service and ops mode programmers in preferences/defaults to xpressnet but no difference except that when clicked on "read from decoder" the error message came up one time as? "communication error PC to command station - error 311" and when I tried it again came up with "requested operation not implemented in command station - error 303". I tried then by selecting the decoder - TCS-T1 - from the drop down and then clicked read and the address lines went red and the error message was the "311" followed immediately by the "303" message, flicked a couple of times between the two, then settled on 303 - couldn't make it's mind up? I have unplugged a replugged the cable into both the PC and the command station and tried another usb port - all of which didn't alter things. I know the cable is OK as it is the one I use on my scanner, which I have used successfully a few times since I've been having the problems with JMRI. I've rung ZTC and they say that they will have to investigate at their end. One thing I did notice every time I installed a fresh JMRI (and on the original installation too) was that the installation went all the way to "installed - JMRI uninstall" and then hung and the next buttons, etc were grayed out. I left it for over 15 mins but nothing changed so I then stopped the programme in task manager. Perhaps something is not installing correctly? Regards, GeoffB On Monday, 5 March 2018, 10:52:09 GMT, Dave Heap dgheap@... [jmriusers] <jmriusers@...> wrote:
? Check Preferences->Defaults. You will find that one or more items are set to Internal. Explanation: "Massoth" is ManufacturerID 123. CVs all reading as 123, long address as 15227 are sure signs of something being set to Internal or Simulator instead of a real connection. These return 123 for everything so you realise they are faking. -- Dave in Australia The New England Convention 2018 On 5 Mar 2018, at 9:33 PM, Geoff Byman gbrails@... [jmriusers] <jmriusers@...> wrote:[Non-text portions of this message have been removed] #yiv5177030445 #yiv5177030445 -- #yiv5177030445ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv5177030445 #yiv5177030445ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv5177030445 #yiv5177030445ygrp-mkp #yiv5177030445hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv5177030445 #yiv5177030445ygrp-mkp #yiv5177030445ads {margin-bottom:10px;}#yiv5177030445 #yiv5177030445ygrp-mkp .yiv5177030445ad {padding:0 0;}#yiv5177030445 #yiv5177030445ygrp-mkp .yiv5177030445ad p {margin:0;}#yiv5177030445 #yiv5177030445ygrp-mkp .yiv5177030445ad a {color:#0000ff;text-decoration:none;}#yiv5177030445 #yiv5177030445ygrp-sponsor #yiv5177030445ygrp-lc {font-family:Arial;}#yiv5177030445 #yiv5177030445ygrp-sponsor #yiv5177030445ygrp-lc #yiv5177030445hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv5177030445 #yiv5177030445ygrp-sponsor #yiv5177030445ygrp-lc .yiv5177030445ad {margin-bottom:10px;padding:0 0;}#yiv5177030445 #yiv5177030445actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv5177030445 #yiv5177030445activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv5177030445 #yiv5177030445activity span {font-weight:700;}#yiv5177030445 #yiv5177030445activity span:first-child {text-transform:uppercase;}#yiv5177030445 #yiv5177030445activity span a {color:#5085b6;text-decoration:none;}#yiv5177030445 #yiv5177030445activity span span {color:#ff7900;}#yiv5177030445 #yiv5177030445activity span .yiv5177030445underline {text-decoration:underline;}#yiv5177030445 .yiv5177030445attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv5177030445 .yiv5177030445attach div a {text-decoration:none;}#yiv5177030445 .yiv5177030445attach img {border:none;padding-right:5px;}#yiv5177030445 .yiv5177030445attach label {display:block;margin-bottom:5px;}#yiv5177030445 .yiv5177030445attach label a {text-decoration:none;}#yiv5177030445 blockquote {margin:0 0 0 4px;}#yiv5177030445 .yiv5177030445bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv5177030445 .yiv5177030445bold a {text-decoration:none;}#yiv5177030445 dd.yiv5177030445last p a {font-family:Verdana;font-weight:700;}#yiv5177030445 dd.yiv5177030445last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv5177030445 dd.yiv5177030445last p span.yiv5177030445yshortcuts {margin-right:0;}#yiv5177030445 div.yiv5177030445attach-table div div a {text-decoration:none;}#yiv5177030445 div.yiv5177030445attach-table {width:400px;}#yiv5177030445 div.yiv5177030445file-title a, #yiv5177030445 div.yiv5177030445file-title a:active, #yiv5177030445 div.yiv5177030445file-title a:hover, #yiv5177030445 div.yiv5177030445file-title a:visited {text-decoration:none;}#yiv5177030445 div.yiv5177030445photo-title a, #yiv5177030445 div.yiv5177030445photo-title a:active, #yiv5177030445 div.yiv5177030445photo-title a:hover, #yiv5177030445 div.yiv5177030445photo-title a:visited {text-decoration:none;}#yiv5177030445 div#yiv5177030445ygrp-mlmsg #yiv5177030445ygrp-msg p a span.yiv5177030445yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv5177030445 .yiv5177030445green {color:#628c2a;}#yiv5177030445 .yiv5177030445MsoNormal {margin:0 0 0 0;}#yiv5177030445 o {font-size:0;}#yiv5177030445 #yiv5177030445photos div {float:left;width:72px;}#yiv5177030445 #yiv5177030445photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv5177030445 #yiv5177030445photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv5177030445 #yiv5177030445reco-category {font-size:77%;}#yiv5177030445 #yiv5177030445reco-desc {font-size:77%;}#yiv5177030445 .yiv5177030445replbq {margin:4px;}#yiv5177030445 #yiv5177030445ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv5177030445 #yiv5177030445ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv5177030445 #yiv5177030445ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv5177030445 #yiv5177030445ygrp-mlmsg select, #yiv5177030445 input, #yiv5177030445 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv5177030445 #yiv5177030445ygrp-mlmsg pre, #yiv5177030445 code {font:115% monospace;}#yiv5177030445 #yiv5177030445ygrp-mlmsg * {line-height:1.22em;}#yiv5177030445 #yiv5177030445ygrp-mlmsg #yiv5177030445logo {padding-bottom:10px;}#yiv5177030445 #yiv5177030445ygrp-msg p a {font-family:Verdana;}#yiv5177030445 #yiv5177030445ygrp-msg p#yiv5177030445attach-count span {color:#1E66AE;font-weight:700;}#yiv5177030445 #yiv5177030445ygrp-reco #yiv5177030445reco-head {color:#ff7900;font-weight:700;}#yiv5177030445 #yiv5177030445ygrp-reco {margin-bottom:20px;padding:0px;}#yiv5177030445 #yiv5177030445ygrp-sponsor #yiv5177030445ov li a {font-size:130%;text-decoration:none;}#yiv5177030445 #yiv5177030445ygrp-sponsor #yiv5177030445ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv5177030445 #yiv5177030445ygrp-sponsor #yiv5177030445ov ul {margin:0;padding:0 0 0 8px;}#yiv5177030445 #yiv5177030445ygrp-text {font-family:Georgia;}#yiv5177030445 #yiv5177030445ygrp-text p {margin:0 0 1em 0;}#yiv5177030445 #yiv5177030445ygrp-text tt {font-size:120%;}#yiv5177030445 #yiv5177030445ygrp-vital ul li:last-child {border-right:none !important;}#yiv5177030445 |
|
Locked
Re: How Engine driver resend command if not feedback from web server?
Hi SteveT,
>>>I assume you mean the WiThrottle server, as the JMRI Web Server isn't >>>involved in this communication. No Engine Driver communicates with a web server consisting of an ESP-1 and a pic18F26J50. >>>You retrieved this list of messages from the JMRI System Console (or the >>>session.log file). Is that correct? I>>>t would be helpful to see the entirety of the messages, including the >>>timestamps and such. Are there any intervening messages? No, I rely on the log I read in Engine Driver and debug on usb2com + Realterm port. ------------------------------------------------------------------------------------------------------- ?????????? Where Egnine Driver save the log file in Android ?????????? ------------------------------------------------------------------------------------------------------- >>>The "*10" is the heartbeat from the WiThrottle server to the client. Is that >>>always involved when you encounter this issue? A 3-second timed routine sends this message from the web server to the Engine Driver. >>>What command station are you using? DIY command station. >>>I don't recall if any of the command station adapters wait for an >>>acknowledgement of a function change such as this. This is the problem, if for example I send the command F1 ON, Engine Driver sends the command to the web server and waits for the answer from this but if the web server does not give the answer, Engine Driver discards the error without correcting it by resending last command. This behavior seems to me absurd and a source of problems in the control of a locomotive. From what I understand, between the web server and the Engine driver there is no real two-way dialogue with error correction. am i right or wrong? If I'm wrong, explain to me how can I enable error correction? >>>Losing a packet on the track bus is a normal occurrence, but this example >>>seems to indicate the WiThrottle server failed to respond to a function >>>change, which I've never seen with my Loconet setup. If you have never seen it does not mean that it can not happen ;-) That's why I do not understand why there is no error correction nor even a command that can allow the web server to request the last command sent by Engine Driver or alert it that it is busy. I have read and reread but I did not find any information about it and at I did not find a shred of documentation about the app. I hope someone can help me Best Regards, Despx |
|
Locked
Alternate languages for Engine Driver - Opinions and Volunteers
We are looking at the possibility of adding (non-English) translations to the Engine Driver app and would be interested to know: - Is this of interest to anyone?
- Would anyone be prepared to volunteer to help with the translations? Obviously to volunteer you would need to be fluent in one or more other (non-English) languages, and at least moderately fluent in English. Which languages we do will be entirely based on the volunteers we get. Peter Akers (Brisbane Australia) |
|
Locked
How can I identify which TSU-1000 Tsunami is installed in my loco?
When I try to identify the decoder with DecoderPro, all I get is the following: "Multiple possible Decoders detected - Manually select for the highlighted Decoders or Family", with a highlighted list of over 180 SoundTraxx decoders!
So how do I confirm which TSU-1000 decoder it is? Is it listed in a specific CV? If so, which one and will it just be a CV code number and not the actual SoundTraxx's part number? Any help would be appreciated. Rod Souza |
|
Locked
Section errors - sensor direction
Hi all,
I just cannot work out what I am doing wrong with sections. I have working layout editor map with sensors, blocks, turnouts all functioning correctly. I have sections each only containing one block and set entry points correctly (I think) I have set SSL turnout and block signals. Sections are validated, Created transits. But when I use dispatcher and add a train I get the error ¡°Found errors when checking setting direction sensors in signal logic for this transit.¡± I go and adjust sections and I get a whole different number of error messages. Or is the problem with the signals? I hope someone can steer me in the right direction Thankyou Paul [Non-text portions of this message have been removed] |
|
Locked
Re: Turnouts not working from Engine Driver app
kennyhunt990
I can confirm that as of right now we cannot throw turnouts from the JMRI turnouts table. Only from the digitrax throttles.
toggle quoted message
Show quoted text
Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Robin Becker' rbgroups@... [jmriusers]" <jmriusers@...> Date: 3/5/18 6:57 PM (GMT-06:00) To: jmriusers@... Subject: RE: [jmriusers] Turnouts not working from Engine Driver app
? Sounds good. Here¡¯s a suggestion for things to try in order when you get there: Confirm that you can throw a turnout from JMRI. You can do this from the Turnout Table or using the Turnout tool. If you cannot throw a turnout from JMRI then there is no need to mess around with Engine Driver. We have to get JMRI working first. If you can throw a turnout from JMRI, try it from Engine Driver with the Monitor Loconet window open. This will confirm whether or not JMRI is issuing the turnout command in response to Engine Driver. From there we can narrow it down some more. Good luck with the testing! Robin From: jmriusers@... [mailto:jmriusers@...] Sent: Monday, March 05, 2018 4:04 PM To: jmriusers@... Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It's a club layout so I'll have to try that n3xt time I can get over there. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Robin Becker' rbgroups@... <mailto:rbgroups@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...> > Date: 3/5/18 5:13 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Ok, that¡¯s good. With the Monitor Loconet window open, do you see anything happen in that window when you click a turnout in Engine Driver? Robin From: jmriusers@... <mailto:jmriusers@...> [mailto:jmriusers@...] Sent: Monday, March 05, 2018 1:23 PM To: jmriusers@... <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app The turnouts are in the table and show on the turnouts page of the Engine Driver App. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Robin Becker' rbgroups@... <mailto:rbgroups@...> <mailto:rbgroups@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 3:03 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Sorry if this has been suggested already, but in JMRI=>Preferences=>Withrottle under ¡°Allowed Controls¡± is the Turnouts box checked? If not check that box, save the prefs and restart JMRI. The turnouts that you wish to control via Engine Driver must already be in your Turnout Table. So if you try to control LT13 from Engine Driver and there is no entry in your Turnout Table for LT13 that it will not work. HTH. Robin Robin Becker San Diego, CA From: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> [mailto:jmriusers@...] Sent: Monday, March 05, 2018 12:12 PM To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It automatically did that. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Bruce J. Clews' bclews@... <mailto:bclews@...> <mailto:bclews@...> <mailto:bclews@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 12:59 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Just saw this post so may be a little bit behind but did you add the prefix LT before turnout number? Bruce Clews -----Original Message----- From: "kennyhunt990 kennyhunt990@... <mailto:kennyhunt990@...> <mailto:kennyhunt990@...> <mailto:kennyhunt990@...> [jmriusers]" [jmriusers@...] Date: 03/05/2018 12:30 PM To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It is a Loconet system. The turnouts work when thrown from a Digitrax throttle. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Ken Cameron' kcameron@... <mailto:kcameron@...> <mailto:kcameron@...> <mailto:kcameron@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 11:02 AM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app One other test is the turnout from a real throttle on the native system (bypass JMRI completely). If that doesn't work, JMRI won't be able to either. I don't recall which vendor your system is: NCE, LocoNet, etc........... If the turnouts are not working from the JMRI tables, there is a connection or configuration issue. So if the throttle are working, from JMRI or via the phones, you have a connection. Then it becomes configuration issues. One spot to check is the 'Preferences->Defaults' tab. Make sure selections are point to the system and not Internal. Next is open and watch the Help->System Console, it may be displaying error when you try to operate the turnouts. This will give us more clues. -Ken Cameron, Member JMRI Dev Team www.jmri.org <> <> <> www.fingerlakeslivesteamers.org <> <> <> www.cnymod.com <> <> <> www.syracusemodelrr.org <> <> <> [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] |
|
Locked
Re: How Engine driver resend command if not feedback from web server?
Hi despx,
I assume you mean the WiThrottle server, as the JMRI Web Server isn't involved in this communication. You retrieved this list of messages from the JMRI System Console (or the session.log file). Is that correct? It would be helpful to see the entirety of the messages, including the timestamps and such. Are there any intervening messages? The "*10" is the heartbeat from the WiThrottle server to the client. Is that always involved when you encounter this issue? What command station are you using? I don't recall if any of the command station adapters wait for an acknowledgement of a function change such as this. Losing a packet on the track bus is a normal occurrence, but this example seems to indicate the WiThrottle server failed to respond to a function change, which I've never seen with my Loconet setup. Regards, --SteveT |
|
Locked
Re: Turnouts not working from Engine Driver app
Sounds good. Here¡¯s a suggestion for things to try in order when you get there:
Confirm that you can throw a turnout from JMRI. You can do this from the Turnout Table or using the Turnout tool. If you cannot throw a turnout from JMRI then there is no need to mess around with Engine Driver. We have to get JMRI working first. If you can throw a turnout from JMRI, try it from Engine Driver with the Monitor Loconet window open. This will confirm whether or not JMRI is issuing the turnout command in response to Engine Driver. From there we can narrow it down some more. Good luck with the testing! Robin From: jmriusers@... [mailto:jmriusers@...] Sent: Monday, March 05, 2018 4:04 PM To: jmriusers@... Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It's a club layout so I'll have to try that n3xt time I can get over there. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Robin Becker' rbgroups@... <mailto:rbgroups@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...> > Date: 3/5/18 5:13 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Ok, that¡¯s good. With the Monitor Loconet window open, do you see anything happen in that window when you click a turnout in Engine Driver? Robin From: jmriusers@... <mailto:jmriusers@...> [mailto:jmriusers@...] Sent: Monday, March 05, 2018 1:23 PM To: jmriusers@... <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app The turnouts are in the table and show on the turnouts page of the Engine Driver App. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Robin Becker' rbgroups@... <mailto:rbgroups@...> <mailto:rbgroups@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 3:03 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Sorry if this has been suggested already, but in JMRI=>Preferences=>Withrottle under ¡°Allowed Controls¡± is the Turnouts box checked? If not check that box, save the prefs and restart JMRI. The turnouts that you wish to control via Engine Driver must already be in your Turnout Table. So if you try to control LT13 from Engine Driver and there is no entry in your Turnout Table for LT13 that it will not work. HTH. Robin Robin Becker San Diego, CA From: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> [mailto:jmriusers@...] Sent: Monday, March 05, 2018 12:12 PM To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It automatically did that. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Bruce J. Clews' bclews@... <mailto:bclews@...> <mailto:bclews@...> <mailto:bclews@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 12:59 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Just saw this post so may be a little bit behind but did you add the prefix LT before turnout number? Bruce Clews -----Original Message----- From: "kennyhunt990 kennyhunt990@... <mailto:kennyhunt990@...> <mailto:kennyhunt990@...> <mailto:kennyhunt990@...> [jmriusers]" [jmriusers@...] Date: 03/05/2018 12:30 PM To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It is a Loconet system. The turnouts work when thrown from a Digitrax throttle. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Ken Cameron' kcameron@... <mailto:kcameron@...> <mailto:kcameron@...> <mailto:kcameron@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 11:02 AM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app One other test is the turnout from a real throttle on the native system (bypass JMRI completely). If that doesn't work, JMRI won't be able to either. I don't recall which vendor your system is: NCE, LocoNet, etc.......... If the turnouts are not working from the JMRI tables, there is a connection or configuration issue. So if the throttle are working, from JMRI or via the phones, you have a connection. Then it becomes configuration issues. One spot to check is the 'Preferences->Defaults' tab. Make sure selections are point to the system and not Internal. Next is open and watch the Help->System Console, it may be displaying error when you try to operate the turnouts. This will give us more clues. -Ken Cameron, Member JMRI Dev Team www.jmri.org <> <> <> www.fingerlakeslivesteamers.org <> <> <> www.cnymod.com <> <> <> www.syracusemodelrr.org <> <> <> [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] |
|
Locked
Re: Turnouts not working from Engine Driver app
kennyhunt990
It's a club layout so I'll have to try that n3xt time I can get over there.
toggle quoted message
Show quoted text
Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Robin Becker' rbgroups@... [jmriusers]" <jmriusers@...> Date: 3/5/18 5:13 PM (GMT-06:00) To: jmriusers@... Subject: RE: [jmriusers] Turnouts not working from Engine Driver app
? Ok, that¡¯s good. With the Monitor Loconet window open, do you see anything happen in that window when you click a turnout in Engine Driver? Robin From: jmriusers@... [mailto:jmriusers@...] Sent: Monday, March 05, 2018 1:23 PM To: jmriusers@... Subject: RE: [jmriusers] Turnouts not working from Engine Driver app The turnouts are in the table and show on the turnouts page of the Engine Driver App. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Robin Becker' rbgroups@... <mailto:rbgroups@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...> > Date: 3/5/18 3:03 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Sorry if this has been suggested already, but in JMRI=>Preferences=>Withrottle under ¡°Allowed Controls¡± is the Turnouts box checked? If not check that box, save the prefs and restart JMRI. The turnouts that you wish to control via Engine Driver must already be in your Turnout Table. So if you try to control LT13 from Engine Driver and there is no entry in your Turnout Table for LT13 that it will not work. HTH. Robin Robin Becker San Diego, CA From: jmriusers@... <mailto:jmriusers@...> [mailto:jmriusers@...] Sent: Monday, March 05, 2018 12:12 PM To: jmriusers@... <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It automatically did that. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Bruce J. Clews' bclews@... <mailto:bclews@...> <mailto:bclews@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 12:59 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Just saw this post so may be a little bit behind but did you add the prefix LT before turnout number? Bruce Clews -----Original Message----- From: "kennyhunt990 kennyhunt990@... <mailto:kennyhunt990@...> <mailto:kennyhunt990@...> [jmriusers]" [jmriusers@...] Date: 03/05/2018 12:30 PM To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It is a Loconet system. The turnouts work when thrown from a Digitrax throttle. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Ken Cameron' kcameron@... <mailto:kcameron@...> <mailto:kcameron@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 11:02 AM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app One other test is the turnout from a real throttle on the native system (bypass JMRI completely). If that doesn't work, JMRI won't be able to either. I don't recall which vendor your system is: NCE, LocoNet, etc......... If the turnouts are not working from the JMRI tables, there is a connection or configuration issue. So if the throttle are working, from JMRI or via the phones, you have a connection. Then it becomes configuration issues. One spot to check is the 'Preferences->Defaults' tab. Make sure selections are point to the system and not Internal. Next is open and watch the Help->System Console, it may be displaying error when you try to operate the turnouts. This will give us more clues. -Ken Cameron, Member JMRI Dev Team www.jmri.org <> <> www.fingerlakeslivesteamers.org <> <> www.cnymod.com <> <> www.syracusemodelrr.org <> <> [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] |
|
Locked
Re: JMRI and NEW APPLE Computer
Randall Wood
A: the LocoBuffer-USB works on macOS; no need to buy new equipment. You may need to install drivers. Check with RR-Cirkits.
B: 1. Copy the *entire* profile folder to a thumb drive, or, if you use it, DropBox. a. If you used a thumb drive , copy the Profile folder to anywhere you want on the Mac. 2. Start JMRI on the Mac and go to the Preferences window. 3. Select ¡°Config Profiles¡± in that window and click ¡°Add Existing¡¡± 4. Find your profile where you copied it or in DropBox and click Choose. 5. Activate the profile and restart JMRI. 6. JMRI will complain about not finding the LocoBuffer-USB on COM3 (or COM-some-other-number). 7. Open the Preferences, go to Connections. 8. Change the LocoBuffer-USB connection from COM3 to something like cu.usbserial-FTZ12345. 9. Save Preferences and restart JMRI. 10. It should ¡°just work¡± now. Note that if you used DropBox, you can do the same on your Windows computer, and the two JMRI computers can share the same profile, and will keep the correct connection for the LocoBuffer-USB. Randall On Mar 5, 2018, at 18:29, upitrr@... <mailto:upitrr@...> [jmriusers] <jmriusers@... <mailto:jmriusers@...>> wrote: A)...Can I use my LOCOBUFFER-USB to connect my Digitrax system layout to my new APPLE computer or do i have to purchase something different? [Non-text portions of this message have been removed] |
|
Locked
Re: Operations.. sorting trains window
I'll restore the ability to sort on the "Build" check box column. Should see this in the next test release.
Dan |
|
Locked
Re: WiThrottle viewing turnouts
Robin,
Yes, the app was closed and restarted. It will be Wednesday before I can get to the club. Everything is closed down due to severe weather that is supposed to go through tomorrow morning. David Klemm Sent from my iPhone 8 Plus _____________________________ From: 'Robin Becker' rbgroups@... [jmriusers] <jmriusers@...> Sent: Monday, March 5, 2018 17:27 Subject: RE: [jmriusers] WiThrottle viewing turnouts To: <jmriusers@...> David, Sorry to hear the problem showed up at the open house :( Did you try closing and restarting the WiThrottle app on your phone by any chance? Just a thought. Anyway if the problem is reproducible you might want to grab the JMRI system console output so we can see if there are any errors reported there. Robin -----Original Message----- From: jmriusers@... [mailto:jmriusers@...] Sent: Monday, March 05, 2018 1:09 PM To: jmriusers@... Subject: Re: [jmriusers] WiThrottle viewing turnouts Robin, At our open house Saturday no one had an android phone so I couldn't see if it was across both devices. David Klemm Sent from my iPhone 8 Plus _____________________________ From: 'Robin Becker' rbgroups@... [jmriusers] <jmriusers@...> Sent: Monday, March 5, 2018 15:06 Subject: RE: [jmriusers] WiThrottle viewing turnouts To: <jmriusers@...> David, Hi. Is this problem just when using the iPhone WiThrottle app or does it happen in Engine Driver also? Robin Robin Becker San Diego, CA -----Original Message----- From: jmriusers@... [mailto:jmriusers@...] Sent: Saturday, March 03, 2018 7:42 AM To: jmriusers@... Subject: [jmriusers] WiThrottle viewing turnouts We have done something where we don't see all the turnouts. It shows TO User and about 10 of the hundred turnouts. I have looked in preferences etc and i am stumped. David Klemm Sent from my iPhone 8 Plus [Non-text portions of this message have been removed] ------------------------------------ ------------------------------------ ------------------------------------ Yahoo Groups Links [Non-text portions of this message have been removed] ------------------------------------ ------------------------------------ ------------------------------------ Yahoo Groups Links |
|
Locked
JMRI and NEW APPLE Computer
A)...Can I use my LOCOBUFFER-USB to connect my Digitrax system layout to my new APPLE computer or do i have to purchase something different?
B)...How do I move files from the backups directory under Operations (PanelPro) on the Microsoft PC tot he backups folder under Operations (PanelPro) on the new APPLE computer? Example....set up trains on PC...copy files from backups folder under Operations on the PC to a thumb drive and then use the thumb drive (USB Port) to load these files to the backups folder under Operations (update Operations) on the new Apple computer. HOW DO I PUT THESE FILES IN THE BACKUPS FOLDER ON THE APPLE COMPUTER? THANK YOU....at this point I am really confused......Frank in Houston |
|
Locked
Re: WiThrottle viewing turnouts
David,
toggle quoted message
Show quoted text
Sorry to hear the problem showed up at the open house :( Did you try closing and restarting the WiThrottle app on your phone by any chance? Just a thought. Anyway if the problem is reproducible you might want to grab the JMRI system console output so we can see if there are any errors reported there. Robin -----Original Message-----
From: jmriusers@... [mailto:jmriusers@...] Sent: Monday, March 05, 2018 1:09 PM To: jmriusers@... Subject: Re: [jmriusers] WiThrottle viewing turnouts Robin, At our open house Saturday no one had an android phone so I couldn't see if it was across both devices. David Klemm Sent from my iPhone 8 Plus _____________________________ From: 'Robin Becker' rbgroups@... [jmriusers] <jmriusers@...> Sent: Monday, March 5, 2018 15:06 Subject: RE: [jmriusers] WiThrottle viewing turnouts To: <jmriusers@...> David, Hi. Is this problem just when using the iPhone WiThrottle app or does it happen in Engine Driver also? Robin Robin Becker San Diego, CA -----Original Message----- From: jmriusers@... [mailto:jmriusers@...] Sent: Saturday, March 03, 2018 7:42 AM To: jmriusers@... Subject: [jmriusers] WiThrottle viewing turnouts We have done something where we don't see all the turnouts. It shows TO User and about 10 of the hundred turnouts. I have looked in preferences etc and i am stumped. David Klemm Sent from my iPhone 8 Plus ------------------------------------ ------------------------------------ ------------------------------------ Yahoo Groups Links ------------------------------------ ------------------------------------ ------------------------------------ Yahoo Groups Links |
|
Locked
Re: Turnouts not working from Engine Driver app
Ok, that¡¯s good. With the Monitor Loconet window open, do you see anything happen in that window when you click a turnout in Engine Driver?
Robin From: jmriusers@... [mailto:jmriusers@...] Sent: Monday, March 05, 2018 1:23 PM To: jmriusers@... Subject: RE: [jmriusers] Turnouts not working from Engine Driver app The turnouts are in the table and show on the turnouts page of the Engine Driver App. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Robin Becker' rbgroups@... <mailto:rbgroups@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...> > Date: 3/5/18 3:03 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Sorry if this has been suggested already, but in JMRI=>Preferences=>Withrottle under ¡°Allowed Controls¡± is the Turnouts box checked? If not check that box, save the prefs and restart JMRI. The turnouts that you wish to control via Engine Driver must already be in your Turnout Table. So if you try to control LT13 from Engine Driver and there is no entry in your Turnout Table for LT13 that it will not work. HTH. Robin Robin Becker San Diego, CA From: jmriusers@... <mailto:jmriusers@...> [mailto:jmriusers@...] Sent: Monday, March 05, 2018 12:12 PM To: jmriusers@... <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It automatically did that. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Bruce J. Clews' bclews@... <mailto:bclews@...> <mailto:bclews@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 12:59 PM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app Just saw this post so may be a little bit behind but did you add the prefix LT before turnout number? Bruce Clews -----Original Message----- From: "kennyhunt990 kennyhunt990@... <mailto:kennyhunt990@...> <mailto:kennyhunt990@...> [jmriusers]" [jmriusers@...] Date: 03/05/2018 12:30 PM To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app It is a Loconet system. The turnouts work when thrown from a Digitrax throttle. Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "'Ken Cameron' kcameron@... <mailto:kcameron@...> <mailto:kcameron@...> [jmriusers]" <jmriusers@... <mailto:jmriusers@...%20%3cmailto:jmriusers@...> <mailto:jmriusers@...> > Date: 3/5/18 11:02 AM (GMT-06:00) To: jmriusers@... <mailto:jmriusers@...> <mailto:jmriusers@...> Subject: RE: [jmriusers] Turnouts not working from Engine Driver app One other test is the turnout from a real throttle on the native system (bypass JMRI completely). If that doesn't work, JMRI won't be able to either. I don't recall which vendor your system is: NCE, LocoNet, etc........ If the turnouts are not working from the JMRI tables, there is a connection or configuration issue. So if the throttle are working, from JMRI or via the phones, you have a connection. Then it becomes configuration issues. One spot to check is the 'Preferences->Defaults' tab. Make sure selections are point to the system and not Internal. Next is open and watch the Help->System Console, it may be displaying error when you try to operate the turnouts. This will give us more clues. -Ken Cameron, Member JMRI Dev Team www.jmri.org <> <> www.fingerlakeslivesteamers.org <> <> www.cnymod.com <> <> www.syracusemodelrr.org <> <> [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] |
|
Locked
Re: Turnouts not working from Engine Driver app
kennyhunt990
I dont think so but I'll have to check.
toggle quoted message
Show quoted text
Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone -------- Original message --------From: "[email protected] [jmriusers]" <jmriusers@...> Date: 3/5/18 4:43 PM (GMT-06:00) To: jmriusers@... Subject: [jmriusers] Re: Turnouts not working from Engine Driver app
? Hi! Did you change the prefs for the command station in the main set up window? If it is set to PR3 or something other that your command station, it will not work. Don't ask how I know about this. Jay [Non-text portions of this message have been removed] |
|
Locked
Re: Turnouts not working from Engine Driver app
Hi! Did you change the prefs for the command station in the main set up window?
If it is set to PR3 or something other that your command station, it will not work. Don't ask how I know about this. Jay |
|
Locked
How Engine driver resend command if not feedback from web server?
Hi all,
sometimes web server does not read an Engine driver command, for example about Light: tx & rx ok --> MTAS33 <;> F10 was (TF10 <;> S33) <<< push Light button --> MTAS33 <;> F00 was (TF10 <;> S33) <-- MTAS33 <;> F00 <<< Light OFF --> MTAS33 <;> F10 was (TF10 <;> S33) <<< push again Light button --> MTAS33 <;> F00 was (TF10 <;> S33) <-- MTAS33 <;> F10 <<< Light ON tx & rx error --> MTAS33 <;> F10 was (TF10 <;> S33) <<< push Light button --> MTAS33 <;> F00 was (TF10 <;> S33) <-- * 10 <<<< error web server did not read the command Light OFF remain ON --> MTAS33 <;> F10 was (TF10 <;> S33) <<< push again Light button --> MTAS33 <;> F00 was (TF10 <;> S33) <-- MTAS33 <;> F00 <<< Light remai ON How can I notify Engine Driver to re-send the last command? Regards Despx |
Peter Akers
to navigate to use esc to dismiss