Noob here but I thought I'd chime in because I have the same hardware (powercab, nce usb, excluding sensors) and goals. So I figured I could learn something going through this thread. Withrottle was working before although it appeared something was misconfigured because I was unable to select "show cabs." I have the 1.65B version of the powercab and (I think) the v7 nce usb. Initially all I had to do was change from v6 in the connection preferences and then I should show cabs and withrottle still worked. Jumpers and rate were default at off/9600.

So then I continued with the instructions here and set all jumpers on and set the 19200 baud rate. I edited the usb cab address to 10 and while the service console correctly reports?NCE EPROM revision = 7.3.7, withrottle doesn't work. And now I've stepped back all my settings and withrottle still doesn't work. I see my phone connected in the withrottle server window and appear to acquire the loco but commands have no effect. I see them in the jmri system console but see nothing in the nce command monitor or the nce dcc packet analyzer (in case I should.) Additionally, no leds fire on the nce usb with withrottle commands. The jmri throttle doesn't work either but jmri turnout controls do work with an led a corresponding led flash on the nce usb and the command in the nce command monitor.? The powercab throttle continues to function.

So to the OP, I can see why you're having trouble. Following instructions for correct config appears to break things!

Any ideas how to fix them again?

jumpers on/19200/cab id 10
=============================
2018-11-07 13:00:27,162 apps.Apps???????????????????????????? INFO? - PanelPro version 4.13.3+R9e5390b starts under Java 1.8.0_65 on Linux arm v4.14.70-v7+ at Wed Nov 07 13:00:27 EST 2018 [main]
2018-11-07 13:00:28,018 apps.Apps???????????????????????????? INFO? - Starting with profile NCE_USB.3f722756 [main]
2018-11-07 13:00:28,424 node.NodeIdentity???????????????????? INFO? - Using jmri-gxxjrda6rhNiaaTcEQSYxs-3f722756 as the JMRI Node identity [AWT-EventQueue-0]
2018-11-07 13:00:28,989 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "NCE" [main]
2018-11-07 13:00:29,915 usbdriver.UsbDriverAdapter??????????? INFO? - NCE USB ttyUSB1 port opened at 19200 baud [main]
2018-11-07 13:00:30,051 nce.NceConnectionStatus?????????????? INFO? - NCE EPROM revision = 7.3.7 [AWT-EventQueue-0]
2018-11-07 13:00:31,598 withrottle.FacelessServer???????????? DEBUG - WiThrottle listening on TCP port: 12090 [WiThrottleServer]

jumpers off/9600/cab id 3
================================
2018-11-07 13:22:17,935 apps.Apps???????????????????????????? INFO? - PanelPro version 4.13.3+R9e5390b starts under Java 1.8.0_65 on Linux arm v4.14.70-v7+ at Wed Nov 07 13:22:17 EST 2018 [main]
2018-11-07 13:22:18,781 apps.Apps???????????????????????????? INFO? - Starting with profile NCE_USB.3f722756 [main]
2018-11-07 13:22:19,203 node.NodeIdentity???????????????????? INFO? - Using jmri-gxxjrda6rhNiaaTcEQSYxs-3f722756 as the JMRI Node identity [AWT-EventQueue-0]
2018-11-07 13:22:19,778 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "NCE" [main]
2018-11-07 13:22:20,331 usbdriver.UsbDriverAdapter??????????? INFO? - NCE USB ttyUSB0 port opened at 9600 baud [main]
2018-11-07 13:22:20,467 nce.NceConnectionStatus?????????????? INFO? - NCE EPROM revision = 7.3.0 [AWT-EventQueue-0]

Hi Iain,

Not sure what you mean by 12" to the foot, or what you haven't heard of on UK layouts.

In your panel xml file look out for? ?
<signalmastlogics class="jmri.managers.configurexml.DefaultSignalMastLogicManagerXml">

Different people will probably want to store different info.

The Roster (under DecoderPro) lets you define and save new columns. That way, people can customize what they want to fill out and more importantly, what they _don’t_ want to fill out.

Would something like that work for this?

Bob

On Nov 7, 2018, at 9:50 AM, Paul Davidson <pdavidson@...> wrote:

Although I initially asked for a new field, I agree with Grant. My main objective was to avoid the need to maintain two separate files for my inventory. As single JMRI file that included the fields required for OpsPro with additional fields for the rest of the info I want to keep. A single file where Opspro can get what it wants and ignore the rest. With that file, I can export it to Excel when desired without the need for me to maintain a separate Excel file.

--
Bob Jacobsen
rgj1927@...

Thanks, I understand the 12" to the foot arrangements, but that isn't a possibility for my model. Apart from the fact that I don't know how to start I simply cannot take my layout to pieces in order to fit in more (to me) unnecessary technology - especially as it doesn't "give" me anything (apart from a delay after sending a turnout command).? It's not something I have heard of on UK layouts.

I shall have to hope that an alternative can be suggested.

I think what we have is fine. What I would like to see is an inventory program as part of JMRI, One where we fill out all of the info that we are wanting to keep track of and OPS pulls the info out that it wants or needs. I have 5600 cars so thats a lot of data and JMRI doesn't want to know or care about the info.
Matt G
Grant NE

开云体育

Can you add turnout position feedback to your system? This would require more wiring and some way to input this information to JMRI (I don't know enough about NCE hardware to advise on that, I'm using LCC for this sort of thing). Then send your signal command after receiving this feed back.

It may seem a bit of a bother, but it would avoid this problem, and it is how the prototype does it. :)

Tim Rumph
Lancaster, SC

Been there, done that with multi-address accessory decoders. Commands overflow in decoders.

Your analysis is basically correct.

But I don't know how to do delays with JMRI.
--
Dave in Australia

See below:

On 8 Nov 2018, at 1:01 AM, Ken Cameron <kcameron@...> wrote:

But here Dave and I differ, he is saying go back to 9600 and keep the items
addressed as was.

That wasn't what I was saying. I was saying to move the AIUs to 8 and 9, which Richard has done, but forget about moving the NCE USB for now, because there are more things that can go wrong with that, as has happened.

I say go with 19,200 and move things to the higher
addresses. I say that because one of your messages point to adding more AIU
boards later. So I'm going with the make the cleanup now while you have
fewer things. It is your choice.

Again, my suggestion is to clean up the AIU addressing and leave the NCE USB until later. You seem to believe the two are tied together. I have seen no evidence that they are.

I'll do some more testing tomorrow. I have no AIU but I do have a Mini Panel I can experiment with.

Also I'd remove the Startup action of loading the panel until you get the
baud rate matching and happy between the computer and the interface.
Otherwise you get extra errors about the interface not matching the panel
file you are loading.

I did suggest that as well. If the panel is loading at startup, that will most likely stop Richard from using Configure USB.

I'd say the only thing you missed was the step of putting the jumpers back
on when switching the baud rate. You could go back to that step of the plan
and work from there.

Ken, you missed the vital point that Richard doesn't have the jumpers any more. He vaguely remembers taking something off when he bought the USB but has no idea where they are.

Let's get my plan perfectly clear.
1) Unplug the two AIUs.
2) Don't put any jumpers on the NCE USB.
3) Take the JMRI settings back to:
-- System manufacturer: NCE
-- System connection: NCE USB
-- Serial port: COM4
-- USB version: V7.x.x
-- System: PowerCab
-- Additional Connection Settings checkbox ON
--- Baud rate: 9600.

4) Save and quit JMRI.
5) Turn off and restart Power Cab
6) Start JMRI and look for the V7.3.0 response in the log.
7) If all is well, check Preferences->Defaults to make sure all are set to NCE.
8) See if Show Cabs works now (may need a couple of refreshes to see Pro Cab at 2 and USB at 3.)
9) Plug in one AIU, refresh Show Cabs a couple of times and look for that AIU to appear.
10) Plug in the other AIU, refresh Show Cabs a couple of times and look for that AIU to also appear.
11) If all is well so far, then try changing AIU Switches as I suggested, one at a time, shutting down both JMRI and the Power Cab and restarting after a change is made.

- Note that I made no mention of removing panel from startup. Looking for a non-existent AIU on a Power Cab doesn't cause any errors.

AIU DIP switches:
- AIU 8 is Switch 4 Off, all others On.
- AIU 9 is Switches 1 and 4 Off, all others On.

Dave

Hi
I have bought one ESU Mobile Control II and installed Engine Driver in it.

I have set function 2 to be latching and I get a long whistle or horn sound when I use the function button on the screen.

I have also set the upper left button to function 2, but I can't get a long signal when I use the side button to activate the whistle/horn. It only gives me a short signal. I can't find anything in the settings to change this.

Is it a bug, is it supposed to work this way or have I missed something?

Best regards
Roland Levin

The link has a space in it, which might not come through certain email setups. See this page:



for links or try:




Bob

On Nov 7, 2018, at 6:38 AM, Gary Ray <gerber1926@...> wrote:

Seems to be a dead link.

Gary Ray

From: [email protected] [mailto:[email protected]] On Behalf Of Paul Davidson
Sent: Tuesday, November 6, 2018 9:27 PM
To: [email protected]
Subject: Re: [jmriusers] JMRI starter tutorial

Try this link. It is a power point presentation on using OperationsPro
www.bhamrails.info/Model_Railroading/New Layout/Operations/JMRI Ops.
Paul D

Virus-free. www.avast.com

--
Bob Jacobsen
rgj1927@...

I was also in the same boat and found a couple of handouts like Geralds’ very valuable. If you have access to YouTube, search ‘JMRI Operations’. There are numerous videos that will lead you through it. I’d also do a lot of playing with the demo files that come with the Operations software. The learning curve can be steep ( and occasionally the frustration level) but you can make it do almost anything you need.

开云体育

开云体育

开云体育

Richard,

Yes those 8 pins, 2 rows of 4, are the jumpers. As you said, those are where
you removed them when you first got the unit. Putting them back will give
you the 19,200 baud rate.

But here Dave and I differ, he is saying go back to 9600 and keep the items
addressed as was. I say go with 19,200 and move things to the higher
addresses. I say that because one of your messages point to adding more AIU
boards later. So I'm going with the make the cleanup now while you have
fewer things. It is your choice.

Also I'd remove the Startup action of loading the panel until you get the
baud rate matching and happy between the computer and the interface.
Otherwise you get extra errors about the interface not matching the panel
file you are loading.

I'd say the only thing you missed was the step of putting the jumpers back
on when switching the baud rate. You could go back to that step of the plan
and work from there.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org

Don't let it get you down, you are making progress, it's always a learning process. I too have been overwhelmed. I took a six year hiatus due to 'health' reasons, and have found that 'Raspberry Pi and Arduino" is just a big mystery to me. Bought an arduino kit and now understand that you can make just about anything. It would help if users said 'my arduino crossing gates", but I can't even consider this part of the hobby at this time.. Take small steps, walk away for a while, have a beverage or three and try again slowly in the morning. We have all been where you are now, keep your chin up and your mouth closed in case there are birds.

See below:

On 7 Nov 2018, at 9:16 PM, Richard_vanRaay via Groups.Io <richard_vanraay@...> wrote:

Wouter gave me a great link Tina photo of the USB interface but for the life of me I can't find the Jumpers on it! He gave a link to Tony's Trains.
When I study mine under a magnifying glass I am still unable to see anything that looks like it can be switched.
There are little black boxes with numbers like 271.
Is it the 8 pins that stick up that I believe I took a plastic case off when I bought it? It says SETUP right next to it. It is next to the LED near the curly cord.

Yes, it is the 8 pins in two rows between SETUP and 1 2 3 4. But don't worry. Simply leave them all bare.

Then JMRI preferences are:
-- System manufacturer: NCE
-- System connection: NCE USB
-- Serial port: COM4
-- USB version: V7.x.x
-- System: PowerCab
-- Additional Connection Settings checkbox ON
--- Baud rate: 9600.

Save and quit JMRI.
Turn off and restart Power Cab
Start JMRI.

The JMRI console log should then report V7.3.0.

I AIU,have theset the AIU's to 8 and 9

Good

WiThrottle is working.

Good

NCE show cabs keeps coming up error.

Don't know why. It works for me with JMRI V4.13.4 and the settings above.

All preference Defaults are NCE

Check them again after making changes.

Tell us if any LEDs are stuck ON on the NCE USB. They should not.

Post a Console Log and Ken can look over it while I try to get some sleep...

Dave

NCE PowerCab with USB, JMRI 4.12, Java 1.8.1, UK equipment mixed Cobalt and Guagemaster Turnout motors, Train Tech signals,

I have a Layout Panel which does what is expected "on the screen" and the correct NCE commands are sent out (i.e. the turnouts and signals change state on the screen and the JMRI NCE Command Monitor reflects the commands I would expect to appear.? However it all happens in a rush.? At times turnout operations get missed out ON THE LAYOUT - i.e the commands are there but somehow they overrun each other or "get lost" in the traffic (I think power draw on the accessory bus is also a factor). Also signals change before turnouts have completed their movements (a no-no in 12" to the foot terms). I had a similar experience when I automated my system using NCE Mini-panels.? In that case (despite arguments from many that it should not be necessary) I programmed delays into the panel logic to ensure time between key changes, and that all turnouts could complete before the command to change a signal was issued.

I have searched JMRI documentation and this forum and can find nothing to help me - probably because I don't know how to put the question to the search engines.

Can anybody help please?

Iain,
Newcastle upon Tyne, UK