Keyboard Shortcuts
Likes
- Jmriusers
- Messages
Search
Inobu,
On 1 Jan 2020, at 5:00 PM, Inobu One via Groups.Io <one2beros@...> wrote:I believe you've misread something. The FTDI and USB Serial route is not and never has been an option for the Power Cab. Dave in Australia |
Locked
NCE signalling
Hey guys Thanks Tim |
Locked
CTC panels
#paneleditor
Hey guys I am looking at building a ctc panel on the computer for my layout what is a good site to get a step by step video on how to go it.? thanks Tim? |
Dave,
You don't have to accept it but I know I saw the same problem that the OP said he had. I went through this procedure and cleared it. I got the components new out of the box and it showed the same problem. If you want to say that I have hardware issue that ok.....but like I said I did not start this thread Larry did. His hardware has nothing to do with mine but he is having the same problem. I think if you look in the past you pretty much said the same thing and recommended for the guy to go with the FTDI and USB Serial route. I think that he was experiencing this same issue. I would venture to say other people will come across the same issue. In any case I know what to do the get these components going and that important to me and my clients. Hopefully Larry comes back and tries it as I did it to help him out as well as anyone else who has the same "hardware" problem that I have.? Inobu ? |
Inobu,
On 1 Jan 2020, at 4:05 PM, Dave Heap via Groups.Io <dgheap@...> wrote:I know you have tried several different Power Cabs. But you haven't reported whether your PCP has the extra-resistors fix documented at the following link: <> The site claims that only a limited range of Power Cabs are affected, but I've had reports of NCE USBs that show the symptoms of sub-spec chips. Setting up an unterminated RS485 bus (bad practice) and relying on special lockup-proof transceiver chip models wasn't a robust move. It was done for what seemed a good reason at the time (reluctance to put terminators in the Power Cab due to its secondary applicability as a slave cab on already-terminated Power Pro systems). When we tracked the problem down it was realised that putting terminators on the PCP (of which there should never be more than one) solved the problem completely. The retrofit was recommended and all newer production runs of the PCP were fitted with terminators. Dave in Australia |
¿ªÔÆÌåÓýInobu, It you allow the NCE USB interface to go RED all bets are off. The handshaking will never start. This has never been found necessary with any other system using the NCE USB. That rings alarm bells to me.
I sometimes leave my Power Cab and NCE USB powered up for hours before starting JMRI.
It says there's something wrong with your particular system. ?I'd suspect a below-spec ?RS485 chip that is causing cab bus flooding and buffer overflow in either device and hence locking up communications. This was what was happening when we worked through this original problem with NCE and came up with the PCP fix ?Your "workaround" is possibly just avoiding this. I'm afraid I can't accept that this is a generally-applicable workaround procedure. It almost certainly indicates a hardware problem somewhere in your setup, or even some unwanted hardware/software interaction with your?RPi4. Dave in Australia |
Locked
Re: Grouping a track arrangement...Can this be done?
#layouteditor
Which panel editor? The LayoutEditor panel will allow you to click (on blank part of screen) and drag (a selection rectangle). Then click inside of it and drag to move it.
|
Bill,
On 1 Jan 2020, at 9:19 AM, WHurry <Wttr@...> wrote:Does your current Power Pro have trouble with reading CVs on sound decoders? More recent Power Pro's than mine have a circuitry change that reportedly solves the problem. I have: - An older Power Pro that has trouble with some sound decoders. -- I briefly had a PowerPax booster but it was unsatisfactory. -- I now have a PTB-100 booster, I always leave it in-circuit and has been fine with almost everything I've thrown at it. - An NCE Power Cab. It has been fine with everything I've thrown at it. - A SPROG IIv3. It has been fine with almost everything I've thrown at it. - The Power Pro with PTB-100 has good compatibility and a speed edge. - The Power Cab has best compatibility, you can use the Power Cab as an extra throttle when not programming. It can also be taken portable as a standalone system, with or without laptop. - The SPROG has good compatibility but is slowest. It is compact for portable use but needs a laptop accompanying it. Dave in Australia |
That falls in line with what I am saying. It you allow the NCE USB interface to go RED all bets are off. The handshaking will never start. What you do is watch JMRI when launches Panel Pro. Connect the coil cable from the Power Cab to the NCE USB Interface. This starts up the micro processor as the USB portion starts up. Within that initialization sequence the USB Interface will connect the two sides and you will be good.? If this happens too far apart the ports are deemed bad by both sides and each side is labeled? bad. The one piece missed was the connection of the coil cable. This is the on switch (12 volt power) being applied to the USB Interface at the same time the JMRI side is? trying to establish communication. I tested this all kinds of ways and I got everything up no problem. I was experiencing the same issue that Larry was with the Raspberry Pi4. Using this procedure I was able to turn it up everything from scratch. |
¿ªÔÆÌåÓýInobu, On 31 Dec 2019, at 2:35 PM, Inobu One via Groups.Io <one2beros@...> wrote: On boot up JMRI is looking to contact the Power Cab Command station but it will not be able to communicate with it until NCE USB interface is established. The NCE USB interface will not go active until it gets a Cab ID. After the Power Cab gives the Cab ID to the USB interface its not looking to do anything else and that handshake transaction is complete. Mean while JMRI is reporting no communication with the Power Cab and just cycles through. The NCE USB consists of two optically-isolated parts, linked by a pair of optocouplers (TX and RX only, no hardware handshaking). 1) The USB part is a SiLabs CP2102 USB-UART chip. Your computer provides 5V power to this chip, it responds on the USB data lines and your computer loads the SiLabs Driver. When JMRI opens a connection, it tells the driver what baud rate to set in the CP2102. 2) The rest of the NCE USB board is powered by 12V from the cab bus. It has a microprocessor with an onboard UART connected to the two optocouplers, input pins with jumpers and other I/O pins to talk to an RS485 transceiver and several LED drivers. When 12V power is applied, the microprocessor starts up, reads the jumpers (once-only) to set its UART board rate (and a system-type setting). It doesn't attempt any communication bus initially, just sits and waits for instructions from the USB part. NCE USB Communications: Once JMRI has opened the port, it sends an "AA" binary command to the device. If the baud rates match, the microprocessor replies with three binary bytes, the 07 30 07 (or whatever) we see in the log. At this stage there is still no attempt by the micro to talk to the NCE Cab Bus. Once JMRI has received the response to the AA command it assumes it has full communication and the status goes green. Once JMRI sends any other command (with a couple of exceptions) to the NCE USB, the micro will need to pass the command on to the Power Cab via the Cab Bus. But the NCE USB is a slave device and cannot initiate communications. It cannot speak until asked to by the Power Cab. The Power Cab loops sending out "ping" commands to all possible address. When the NCE USB sees a ping command addressed to its CabID*, it responds with the command JMRI sent and waits for a response from the Power Cab. When the micro is in the process of waiting for an ping so it can send a command to the Power Cab, it will turn the Cab Bus LED on. This is the step where things most often go wrong and a stuck-on of Cab Bus (or USB Bus) ?LED will require a power cycle of the microprocessor. Once the micro gets a reply (e.g. CV contents) from the Power Cab, it will pass that back to JMRI via the optocoupler. * What is the CabID of a given NCE USB? - For some jumper settings (e.g. All Off), the CabID is always forced to 3. - For some jumper settings (e.g. All ON), the CabID is stored in the NCE USB and programmable by the "B1 xx" command (another command handled locally by the micro and not passed on). (JMRI's Configure USB menu item). Dave in Australia |
Locked
Resolution of Control Panel Screens
Keith
Group,
Something I noticed when constructing my Control Panel using CP editor.? I have the panel finished and it extends over 4 22" panels, in a 2 x 2 arrangement.? I recently purchased a large 55" screen to see if I could get the panel on just one screen.? However, because the screen resolution is what it is, the panel needs to be zoomed to a smaller size to fit on the screen.? When I do this, the icons do not function correctly.? In other words, the toggle switches and control levers do not function.? Has anyone else see this?? Any solution?? Also, when zooming the panel, the resolution of the icons really degenerates.? Any solution for this< or is it an function of a bitmap image rather than a postscript type? Any insight to these issues would be appreciated. Thanks in advance,? Keith Williams Hoschton, GA |
Locked
Re: Car Order
#operationspro
Our railroad, the Castle Rock and Pacific, is 2500 sq.ft. on two levels.? It is freelance, point to point - Galveston, TX to Castle Rock, CO.? There is a classification yard in each of the end point cities.? Beyond Galveston and Castle Rock there are two double ended staging yards that are the true endpoints.? The staging yards are not active during an op session, that is, there is no switching in staging - what ever car order goes in is that same as what comes out the next time that train runs.? We are currently running? a 5:1 fast clock so four hour sessions only represent 20 hours of a full day.?? Now for CAR ORDER on the Castle Rock and Pacific... We have 4 through freights that run staging to staging and return during a 24 hour day - so 8 through freights.? These trains pick-up and set out cars only at the two major class yards as they run across the railroad.? Before each session, I check and block any of these trains that are in staging.? If a train is coming out of Galveston staging, Galveston cars are in block #1 and Castle Rock cars in block #2 followed by the remainder of the train.? I use Operations Pro and love it.? I do not run in real time but rather build, update, print and terminate all manifests in sequence ;for all trains that are expected to run in that 20 hour fast clock session.? When a through freight comes out of staging for the first time during the session it is blocked because I blocked it before the session.? When it enters the second and last classification yard before entering staging on the opposite end of the railroad, the yardmaster a that yard has orders to reblock the train so that when it reappears on its next run out of staging it is already blocked.? Since I have generated all of the manifests in advance, I know how the train should be blocked when it reappears.? To keep things kind of "railroady" I print the blocking instructions on a pseudo "31 Order" and place it in the "restaurant rail" on the fascia above the yard and staple a copy on to the associated manifest. (a "restaurant rail" is one of those linear rails that are used to hold food order tickets in a restaurant)? I also stamp the Operations Pro generated manifests and switch lists with a green inked stamp that says "Blocking Required see 31 Orders".? In a pinch, the YM can delay the blocking until the train returns because no one else will see the train until it has passed through his/her yard the second time but we encourage them to get it done at the first opportunity.? This works for us and keeps things in order. Not really on topic but it goes with staging on our railroad - we swap open loads.? A train may go into staging with an empty flatcar but when the train is built again by Operations Pro it may have any number of different open loads for the next trip to a different industry.? When an operator gets a train out of staging they check the manifest for cars that have open loads and change them if necessary.? We keep a file cabinet full of different open loads.? All the operator has to do is remove any improper load and replace it with the load listed on the manifest.? In this way a flat with a steel plate load going into staging may come out with a load of? pipe or tractors or...whatever.? The downside of this is that you don't have all of the neat detail of chains and such to fasten down the loads but it does allow you to have sensible loads going to each industry.? Food for thought. |
Inobu,
On 31 Dec 2019, at 6:16 PM, Inobu One via Groups.Io <one2beros@...> wrote:Your symptoms indicate that you've probably got one of the sub-spec RS485 driver chips in one or more of your devices, probably the NCE USB and don't have the PCP modification necessary to make these work. The result is that the NCE USB connection will need unplugging and replugging after power-up to unstick a stuck RS485 driver chip. <> The NCE USB will report the version number even if it hasn't established communication with the Power Cab. All it needs is 12V power from the cab bus and correct jumper settings to match the baud rate JMRI is using. Communication on the NCE Cab Bus only starts when other commands are sent by JMRI and that's when the lockup can happen, shown by a stuck-on Cab Bus LED. Dave in Australia |
Locked
Re: Layout editor zoom issue- new insights
#layouteditor
So basically, if you zoom out farther, it permanently changes the size of the viewing area (at least until you re-load the panel), but it doesn't change the viewing area to be large enough to see the entire panel while?it's zoomed out that far. I don't know what would make it do that (yet).
|
You're not suppose to be able run a loco on the programming track....I've used dcc++ in the past...program on the program track then run on the main track On Dec 31, 2019 9:01 PM, "Chuck Bade via Groups.Io" <chuck.bade@...> wrote: I also have an Arduino (Mega) DCC++ base station.? I can run a loco on the main track and I can program a loco on the programming track, but I can't run the loco on the programming track.? Does that work on your system? |
Locked
Re: Layout editor zoom issue- new insights
#layouteditor
Alright, I've done more testing with the program and I have more information.
The problem appears to be difficult to replicate because it's very unusual. It only shows the part of the layout that can be shown with "no zoom" setting once you zoom out. However, it gets weirder if you zoom out farther- if you zoom out to a certain point, it will be able to show the entire thing at the lower zoom factor again. I don't know what that means regarding what causes the glitch yet, but I hope it helps you with troubleshooting. |