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: Layout Editor: issue connecting two turnouts
#layouteditor
George -
i can consistently get the following situation to exhibit the issue: panels->new panel->layout editor options->grid options->show grid in edit mode [turn this off] options->grid options->snap when adding options->grid options->snap when moving turnout RH: shift-click to put this somewhere on panel turnout LH: shift-click to put this to the right of the first TO aligned horizontally but not touching right click/hold on the red square of the points end of the LH TO and drag (extending the line of the TO) to try to connect to the red square on the normal end of the RH TO. ?[ I can¡¯t get these to connect] alternatively, if I extend the normal end of the RH TO to attempt to meet the points and of the LH TO, that won¡¯t connect either. If I move the entire LH TO, it will connect most of the time (I thought I had a time or two when it didn¡¯t connect, but I couldn¡¯t reproduce consistently). ?Also, as I play around with extending and moving the ends of the TOs, there are times when I can no longer grab the points and of the TO which I extended. ?Obviously a somewhat obscure bug somewhere. ?
Hope this helps in debugging. ?As I said, there is an easy workaround of just adding a track segment between the TOs manually so definitely not a high priority.
And thanks for making Layout Editor such an incredibly useful and sophisticated tool!
Jerry ___________________________________
jerryg2003@... |
|
Locked
Re: Cable driver help needed
Thanks, it wasn¡¯t so much the bargain but the speed in which Amazon could get me the cable. Lack of patience, turns out, probably gonna cost me more time. Bruce in Mt. airy MD
toggle quoted message
Show quoted text
On Jan 1, 2020, at 10:21 AM, Dave Heap <dgheap@...> wrote: |
|
Locked
Re: Cable driver help needed
Bruce,
On 1 Jan 2020, at 11:15 AM, burrettmd <burrett@...> wrote:That's exactly why I recommend spending ~$30 on buying an ESU or RRCirKits supplied genuine FTDI cable rather than buying a "bargain". Dave in Australia |
|
Locked
Re: NCE signalling
John,
On 2 Jan 2020, at 12:56 AM, John <jonie41@...> wrote:That's certainly possible with Program on Main. Dave in Australia |
¿ªÔÆÌåÓýNo it cannot. The LNWI basically implements a minimal version of the WiThrottle protocol, allowing smartphones to run trains, nothing else.? ? You need a full function computer interface.? Some recent Digitrax systems include those, or there is the long established LocoBuffer USB device, or Digitrax¡¯ own PR3/PR4 products. ? ? ? From: [email protected] [mailto:[email protected]]
On Behalf Of umarally@...
Sent: 01 January 2020 11:52 To: [email protected] Subject: [jmriusers] Using JMRI via LNWI Wifi throttle interface ? HI, |
|
Locked
Re: WiThrottle - control panels
#paneleditor
#withrottle
Hi Brian,?
What type of panel is it? Layout Editor, Panel Editor or Control Panel Editor? If you'll post your panel file somewhere, we can take a look. Also, there have been changes to the client-side panel code, so make sure to refresh the page to get the new code to your browser. I'd also suggest you open a browser on your local machine and advise if the same problem occurs. --SteveT |
|
Locked
Cable driver help needed
?Cable driver help needed! ? so I went out and bought myself a USB to RS 232 serial cable advertised as with FTDI chipset. When I received ?the cable, The specifications sheet does not list FTDIE but says the chipset is an FT 232 and ZT213. It also came with a driver disc, which my laptop does not have a CD at all so is Not usable. So following the instructions I went to the webpage to download a driver and when I get there it tells me that new drivers are now available to support the FT4222H and 4D2XX drivers it also has in the instruction area A line that says FTDI drivers are available for windows CE 4.2 to 5.2 6.0 to 7.0 and 2013 I am running windows 10. I also have no clue what FT4222H or D2XX might be. The cable I purchased is a Ditech DT 5031 from Amazon Suggestions? ?Thanks Bruce in Mt. Airy, MD
|
|
Locked
WiThrottle - control panels
#paneleditor
#withrottle
I'm just about to start construction of a new layout and over the christmas period have been constructing a ne panel in panel pro.
All seems fine and works ok in panel pro. but when I started WiThrottle on my i-pad and connected to jmri to check how the panel looked the double slips and 3 way point icons were missing. All the other icons are OK. When I checked the panel in wi throttle under my jmri the screen shot of the panel looks ok and shows the panel as complete. I thought at first it was due to upgrading to 4.18 but having done a clean install? back to 4.16 the problem still remains. Anyone have any ideas why the the double slips and three way points would not be showing in wi throttle? Many thanks Brian The panel was constructed from scratch and most of the icons have also been created from scratch. I have currently set the prefferences to load the panel and start withrottle. The DCC interfaces are set for NCE and NCE simulator ready for connection to the Powercab once the new layout out is built. |
|
I connected a siding that was isolated from the main line by insulating connectors. I then attached a power connection to that siding and to an Atlas power router. Thus I could select programming track on the NCE Power Cab, route the NCE Power cab solely to that siding and perform the changes to CV. Once that was finished, I could run the locomotive onto the main line. That simple. Did not need boosters or any other devices. |
|
Locked
Re: NCE signalling
Wasn't there a post in 2018 or later where a fellow connected all his Light-Its
toggle quoted message
Show quoted text
in parallel gave them all the same address, programmed the functions all at once, then disconnected them all, then connected them one at a time to give each a unique address? John ---------- Original Message ---------- |
|
Wouter,
There is no pending melt down as I posted the original thread for Dave to read. After that there's nothing else to be said. If you look at Larry's last comment "Any thoughts of help to troubleshoot and resolve would be appreciated." I understand that my posting isn't anything official and can be deleted if need be. I'm ok with it. I think I'll end my posting on this topic here as I've gained a lot of knowledge in this exchange.? Inobu |
|
Inobu, Dave, Going to stick my neck out here, with a mention that descending into bickering is not helpful to anyone. Both of you obviously have a lot of knowledge. Dave has a lot more mileage on this forum where he is universally respected. But that does not invalidate anyone else's aqcuired knowledge and experience. I wonder if the best solution, not just to the impending meltdown but even more in terms of helping other users, is taking this off-line? If not, then I would respectfully ask Inobu to homour Dave and answer his queries - because it seems a constructive way forward. It doesn't matter to readers here who's right. What matters is a useful outcome and averting acrimony. Who's right will emerge at the end of the problem finding mission, not at the beginning. And to almost anyone, it doesn't matter anyway. Pretty please. Wouter On Wed, 1 Jan 2020 at 12:02, Inobu One via Groups.Io <one2beros=[email protected]> wrote: Dave, |
|
Dave,
toggle quoted message
Show quoted text
I don't think you really understand the issue at hand. How can to even clam to test the issue when you don't have a Raspberry Pi 4. That makes no sense what so ever. That is like someone complaining that they are having problems with a Ford and you tell them I just test drove a Toyota and I don't see the problem. If any of your test cases encompassed a 15 minute waiting period then you surely don't understand the problem or issue at hand. The issue is within? seconds. More so you are trying to argue a point with no knowledge in what "Buster" does with the ttyUSB0 time out.?? This is the original trouble post...... On Thu, Dec 26, 2019 at 05:45 AM, Larry wrote: I ordered a Raspberry Pi 4 and am using Steve Todd's wonderful image to run JMRI.? I can access the desktop at 192.168.6.1 perfectly and everything appears fine except that I can never get my NCE PowerCab to connect.? I disabled the autoidentify and set the preferences up manually choosing NCE USB.? I always get error: Unable to connect on ttyxxxxIts like going to the doctor and saying I have a headache and he says no you don't none of my other patients are complaining.? lol Inobu |
¿ªÔÆÌåÓýInobu, What you are doing is quite primitive is regards to establishing the link between JMRI and the Power Cab. Because of this understanding I was able to reason out what it take to I'm afraid I cannot agree with your reasoning because there are several fundamental errors in your understanding of what communications go on between JMRI/NCE USB/Power Cab during startup of these items. For example, there is absolutely no basis for your assumption that there are any limited-time communication windows between (1) power-up of the microprocessor 12V, (2) power-up of the USB-UART CP2102 5V and (3) startup of JMRI. I just disproved your theory by (1) plugging my NCE USB into the cab bus only, powering up the Power Cab (hence providing 12V to the microprocessor), waiting 15 minutes before (2) connecting the USB, hence providing 5V to the USB UART and initiating the SiLabs driver loading into RAM and providing a COM port within seconds,?waiting a further 15 minutes? before (3) launching JMRI, which triggered transmission of an AA to the microprocessor via the USB link and a "07 03 07" response from the microprocessor and readiness to accept a command (I tried Read CV 8), which it passed on to the Power Cab and I received a valid response from the decoder. Note that the Power Cab would have been pinging all valid cab bus addresses (including the address for the NCE USB, 10 in my case) since power-up but the NCE Cab Bus protocol manual notes that a connected cab bus device is under no obligation to respond until it has something to send (the Read CV8 command in this test case).? Neither does the NCE USB need a ping from the Power Cab to set up communications with JMRI. This can be easily disproved by unplugging the Power Cab from the PCP and starting JMRI. You will see the "07 03 07" response in the system log and you can happily use the Send NCE command to send an "AA" (or even a "B1 xx" change cab bus address) command and see the response in the NCE Command Monitor. It's not until you send something that needs to be passed to the Power Cab (such as Read CV8) that the microprocessor and eventually JMRI will notice the absence of the Power Cab.? It may not be a problem to you but one of your users posted up this issue first. When I could duplicate the issue I deemed it a problem and began
I don't think or work like that... Dave in Australia |
|
Dave,
Its not called a dance. In data communication it is typically called a protocol hand shake. This process starts with a Service information Octet that starts the communication? process between two machines. After each receives a set number of these message the machines will go to the next level of establishing communication. The is typical in SS& protocol. What you are doing is quite primitive is regards to establishing the link between JMRI and the Power Cab. Because of this understanding I was able to reason out what it take to address this problem. It may not be a problem to you but one of your users posted up this issue first. When I could duplicate the issue I deemed it a problem and began to troubleshoot it. After a few hours of testing I came up with a solution that resolved the issue and I was able to establish the connection between JMRI running on a RPi 4? and the Power Cab. I have stated that I had one 1.65 and two 1.65b one being NIB and was able to create the problem and clear the problem using the prescribed method. With all of this said if you still cannot accept my testing I cannot help you. The PCP are dated 2005 and 2017. The 2005 came set came from a 1.28c that I upgraded the chip to 1.65. the 1.65b were new 2017. If you need proper reports from other uses then wait for them pretend this never happened. I will.....lol. Inobu |
|
Locked
Re: NCE signalling
¿ªÔÆÌåÓýTim, i am looking at using NCE LIGHT-it decoders for my signals is there a video on how to wire them up and program them I will be using NCE BD20¡¯s for block detection. This may answer some of your questions: Light-It with JMRI The Light-It can easily be set to Signal Decoder mode. JMRI provides full support to the decoders, both via Program on Main (the only programming mode these decoders support) and as DCC Signal Heads. To get the Light-It into Signal Decoder mode on almost any DCC system: - Attach the Light-It to your DCC track bus (the rails) - Create a Roster Entry using the "Light-It - Signal mode" definition. (Auto identify is not possible). - Go to the Basic pane, check the warning about Preferences, enter the desired Signal Address, Save and Close. - Reopen the roster entry in POM mode and go to the Basic pane. - Make sure nothing on your layout is busy sending Turnout or Signal commands (these will upset address programming). - Press the gold programming button on the Light-It board. - While the LEDs are still flashing, Write Full Sheet on the Basic Pane. - The LEDs should stop flashing as soon as you Write. Try again if needed. - The decoder should now be in Signal mode and accept Aspect or POM commands. To use/test the Light-It in Signal mode: - Open the Signal Head table. - Add a DCC Signal Decoder with the same hardware address as you set in the roster entry. You must tick the Offset Address checkbox for these decoders, irrespective of your DCC system. - Test by setting various Appearances, but be aware that the default mapping in JMRI is not the same as the default mapping in the Light-It. You need to either change the Appearance numbering for the Head in JMRI, or reprogram the decoder. Here is a sample numbering system that matches the decoder's defaults. Appearance Numbering: Dark: 31 Red: 0 Yellow: 1 Green: 2 Lunar: 15 (all on) Flasing Red: 3 Flashing Yellow: 4 Flashing Green: 5 Flashing Lunar: 30 (all flashing) If you create JMRI Masts using existing Signal Head(s) in "Signal Head Controlled Mast", there is no problem. If you create JMRI Masts using "DCC Signal Mast Decoder", there is a problem because the checkbox for the needed Offset Address is not present (there is a current GitHub issue for this). ? Dave in Australia |
|
Inobu,
You have missed one vital troubleshooting step. You haven't reported whether you need to do the same connection dance with a non-RPi4 computer. We've used the NCE-USB to Power Cab combination on many Windows, Mac and Linux computers and never experienced the same problem. It's remotely possible there's something odd going on with the RPi4. Dave in Australia |
|
Inobu,
On 1 Jan 2020, at 5:08 PM, Inobu One via Groups.Io <one2beros@...> wrote:I don't want you to delete your findings. But I don't accept your conclusions that you need to perform a connection dance with the Cab Bus cable due to some NCE or JMRI timing issue. Your logic on that doesn't stand up to what I know about the particular NCE hardware and JMRI software. I'm one of the acknowledged NCE hardware experts and also a JMRI developer was one of the experts working directly with NCE on diagnosing and fixing the timing problem I mentioned. I'm putting this on public record that having to perform a connection dance with the USB cable is not a known or likely issue with this hardware, your logic for the dance doesn't stand up to what we know about the devices. The problem may not be due to the termination problem, but it's the most likely for your symptoms. You also haven't given me any evidence that you have checked your PCP or your NCE USB, nor your Power Cabs. It would be very helpful to us if you could email me closeup photographs of both sides of the PCP and NCE USB boards so I can make some checks. (I'm reluctant to ask you to partially dismantle a Power Cab for photography.) If there's a real issue with the NCE product or JMRI we need to get to the bottom of this and we need proper reports from any other affected users, not just an acceptance that this connection dance needs to be performed. Dave in Australia |
to navigate to use esc to dismiss