Re: Decoder Pro not seeing Power Cab #nce #powercab

开云体育

Andrew,

On 18 Dec 2019, at 10:01 AM, andrew.woolman <apwool@...> wrote:

I look forward to getting home and trying this, though I am not at this point optimistic. ?Meantime, I looked, and those two drivers I had earlier installed seem to be missing, but there is a?SiLabsUSBDriver.kext in the Library/Extensions folder; nothing SiLabby in the System tree. ?shrugs. ?I will delete the one and follow your instructions, se where they lead.

The installer should put a new one in "Library/Extensions". It doesn't always clear out the old ones.

No harm in removing everything SiLabs and doing a clean reinstall of the latest correct (for your OS version) drivers from <>..

Any opinion on those jumpers, given the specs I put in my initial Question on this topic?

Not an opinion, just the facts. There's no way your current configuration (all jumpers off and 19,200 baud) will ever work. There's a baud rate mismatch between the USB part (set by JMRI) and the onboard microprocessor (set by the jumpers).

There are only two valid setting combinations for a Power Cab:

1) All jumpers OFF and 9600 baud in JMRI.

2) All jumpers ON and 19200 baud in JMRI. (Jumper 1 is ignored so it's setting doesn't matter).

Setting (1) is the base level setting that will work with any combination of NCE USB (V6 or V7) and any Power Cab version.

Setting (2) will only work with NCE USB V7. and and Power Cab V1.65 or greater (V1.65B preferred). Enables some extra features but can be a bit more fiddly to set up.

Don't attempt setting (2) until you get setting (1) working reliably (and then only if you have the right firmware versions).

Dave in Australia

Re: Digitrax BXP88 - eight zone occupancy detectors

#166999

As was noted in another thread on this forum not too long ago, there is a file in the file section of the Digitrax list that you can use to determine board addresses.

It can be used for the SE8c, the BDL168, the BXP88, and the DS54/64.

Steve
"Breezlys"

Re: Digitrax BXP88 - eight zone occupancy detectors

#166998

Alan,

I think the terms (address and addressed ID) you are using is making the question a bit convoluted.?

This might be the answer you are looking for.

When you make the ID assignments it automatically assigns the section addresses in each BXP88. There is a formula to calculate the addresses but as Marc alluded to JMRI will automatically
list them in the tables when the command station boots up and all the devices report in.

As with all Digitrax devices it is recommended to document everything to better manage the addresses. Down the road you can make an ID assignment that could possibly conflict previous assigned ID's.
It may force you to re organize everything. ?

Inobu

Re: Issue copying profiles with long name

#166997

no this is simply a windows issue its not worth troubleshooting i gave you the theory how it plays out in the real world is a different story but i run into the same problem moving files. Another windows problem with renaming files has to do with windows running out of memory and before you ask I have 64 gigs in my pc and it doesnt matter windows is what it is.

Bobby Abrams

Show quoted text

On Tue, Dec 17, 2019 at 3:42 PM JerryG via Groups.Io <jerryg2003=[email protected]> wrote:

I can certainly change file location, but having a profile where I simply changed a “7” to an “8” shouldn’t have changed the length of the name.? Is there some other issue here?

Thanks, Jerry
___________________________________
jerryg2003@...

Re: Issue copying profiles with long name

#166996

I can certainly change file location, but having a profile where I simply changed a “7” to an “8” shouldn’t have changed the length of the name. ?Is there some other issue here?

Thanks, Jerry
___________________________________
jerryg2003@...

Re: Arduino CMRI turnout feedback not working properly

#166995

Found this a bit of an intriguing problem so I tried to replicate (which I did - but also found the solution).? Using s.brackstone's Arduino code as is, I just set up two turnouts using 2 bit outputs,? one with pulsed (as he did) and a second one with steady state output for comparison.? I also set up the two sensors as he did in JMRI.? At this stage, I haven't put any feedback on either turnout.
?
Looking at the CMRI Monitor, I see that the second turnout works as I would expect with a single transmit from JMRI with the appropriate bit set when the turnout is thrown.? ?Furthermore, the sensor shows Acitve when the turnout shows Thrown and Inactive when the turnout shows Closed, again as would be expected.

The first turnout (the one with 2 bit pulsed output), however,? gets two transmissions from JMRI about half a second apart (this is what "pulsed" does):?

7:41:07.415: Receive ua=1 IB=0 0 0?

17:41:07.484: Receive ua=1 IB=0 0 0?

17:41:07.499: Transmit ua=1 OB=10 2 0 0 0 0 0? (thrown bit on)?

17:41:07.588: Receive ua=1 IB=0 0 0?

17:41:07.654: Receive ua=1 IB=0 0 0?

17:41:07.716: Receive ua=1 IB=0 0 0?

17:41:07.794: Receive ua=1 IB=0 0 0?

17:41:07.860: Receive ua=1 IB=0 0 0?

17:41:07.929: Receive ua=1 IB=0 0 0?

17:41:07.996: Receive ua=1 IB=0 0 0?

17:41:08.006: Transmit ua=1 OB=0 0 0 0 0 0? ?(neither bit on)

17:41:08.070: Receive ua=1 IB=0 0 0?

17:41:08.142: Receive ua=1 IB=0 0 0?

17:41:08.213: Receive ua=1 IB=0 0 0?
(and vice versa when I click the turnout again).

In my setup, the sensor shows Active when the turnout shows Closed and Inactive when the turnout shows Thrown - the reverse of what would be hoped.? Obviously, someone is confused (perhaps me, perhaps the Arduino code).

Now I added one sensor feedback to each turnout.? Turnout 2 continues to work as expected: Click and you can throw the turnout and sensor goes active. Click again and turnout goes closed and sensor goes inactive.? Turnout 1 works (or rather doesn't work) as s. brackstone reported.? I think the Arduino code is getting confused by the two transmissions from JMRI when the two bit output is pulsed rather than steady state.

Possible solution:? Re-enter turnouts in JMRI with two-bit steady state output and all should be fine.? Or, you could switch to one bit output as Bob suggested and modify the Arduino code accordingly.

Jerry

___________________________________
jerryg2003@...

Re: Decoder Pro not seeing Power Cab #nce #powercab

#166994

Dave,
I look forward to getting home and trying this, though I am not at this point optimistic. ?Meantime, I looked, and those two drivers I had earlier installed seem to be missing, but there is a?SiLabsUSBDriver.kext in the Library/Extensions folder; nothing SiLabby in the System tree. ?shrugs. ?I will delete the one and follow your instructions, se where they lead.

Any opinion on those jumpers, given the specs I put in my initial Question on this topic?
Many Thanks,
Andrew.

Re: Issue copying profiles with long name

#166993

PS that is a windows file restriction has nothing to do with jmri

Bobby Abrams

Show quoted text

On Tue, Dec 17, 2019 at 2:42 PM Bobby Abrams via Groups.Io <balc99=[email protected]> wrote:

the name length restriction is 256 characters starting with c:\?

if this really is a problem change the directory where you keep the files
Bobby Abrams

On Tue, Dec 17, 2019 at 1:29 PM JerryG via Groups.Io <jerryg2003=[email protected]> wrote:
JMRI 14.17.7+R5bc91de, Windows 10.

Using the Config Profiles screen under Preferences, when I try to copy a profile named SPROGSim-CMRICom7, I get different behaviors depending on what I name the new profile.? If I attempt to name it SPROGSim-CMRICom8, I get an error that says "Unable to rename [where I keep my profiles]\JMRI\SPROGSimCMRICom8.jmri\profile\jmri-[long string of characters] to use new profile ID."? When I attempt to name the new profile simply "C8" it works fine.? However, a fully populated directory tree is created in both cases.

I tried a few more cases and it seems to work OK with some profile names and not others.? I thought I found a pattern related to name length (6 or less vs more), but then I found other cases that didn't work..

May have been an issue for a while as I tried this on JMRI 14.17.3 and got the same behavior.

Jerry
___________________________________
jerryg2003@...

Re: Issue copying profiles with long name

#166992

the name length restriction is 256 characters starting with c:\?

if this really is a problem change the directory where you keep the files

Bobby Abrams

Show quoted text

On Tue, Dec 17, 2019 at 1:29 PM JerryG via Groups.Io <jerryg2003=[email protected]> wrote:

JMRI 14.17.7+R5bc91de, Windows 10.

Using the Config Profiles screen under Preferences, when I try to copy a profile named SPROGSim-CMRICom7, I get different behaviors depending on what I name the new profile.? If I attempt to name it SPROGSim-CMRICom8, I get an error that says "Unable to rename [where I keep my profiles]\JMRI\SPROGSimCMRICom8.jmri\profile\jmri-[long string of characters] to use new profile ID."? When I attempt to name the new profile simply "C8" it works fine.? However, a fully populated directory tree is created in both cases.

I tried a few more cases and it seems to work OK with some profile names and not others.? I thought I found a pattern related to name length (6 or less vs more), but then I found other cases that didn't work..

May have been an issue for a while as I tried this on JMRI 14.17.3 and got the same behavior.

Jerry
___________________________________
jerryg2003@...

Re: Digitrax BXP88 - eight zone occupancy detectors

[email protected]

#166991

On Tue, Dec 17, 2019 at 01:52 PM, Allan Altheim wrote:

Using Digitrax DCS210, DS64s (4), and BXP88 (2) question is how address the two BXPs, each with eight zones, have addressed each BXP ID #.

Not quite clear. You ask 'HOW'? but you also say you 'HAVE' set each card ID#.?

You can not use JMRI to setup the? BXP88 as we could the BDL168. Digitrax changes.

You can use the JMRI Turnout Control to set the card ID and change OPSW settings but this is the same as using a Digitrax throttle.
So which ever is quickest for you.

Once this is done you view the output via PanelPro Tables : Sensors , Reporters.

Marc

Re: Signal mast logic #signalmasts

#166990

开云体育

Thanks Bob, is there a link to the documentation that would explain how to do number 2?

?

Jim

?

Sent from for Windows 10

?

Show quoted text

From: [email protected] <[email protected]> on behalf of Bob Jacobsen <rgj1927@...>
Sent: Tuesday, December 17, 2019 7:47:07 PM
To: [email protected] <[email protected]>
Subject: Re: [jmriusers] Signal mast logic

?

If you don’t want the Approach (yellow) to show, you could

?1) Not have each mast protecting the following one.? Just delete those references.

or

?2) Configure your mast definitions so that the Approach is mapped to “light the green output”

Bob

> On Dec 17, 2019, at 9:51 AM, James Anderson <james_anderson_999@...> wrote:
>
> Many thanks for the replies. Once again my lack of understanding. I was looking for a simple red/green system on the lights. I disabled the approach aspect on the mast and so when it could not go yellow it went? to red (your mention of yellow highlighted that to me so thanks ). I think I might have to rethink what I want to do and perhaps put virtual masts in between physical masts to hide the yellow.
>

--
Bob Jacobsen
rgj1927@...

Issue copying profiles with long name

#166989

JMRI 14.17.7+R5bc91de, Windows 10.

Using the Config Profiles screen under Preferences, when I try to copy a profile named SPROGSim-CMRICom7, I get different behaviors depending on what I name the new profile.? If I attempt to name it SPROGSim-CMRICom8, I get an error that says "Unable to rename [where I keep my profiles]\JMRI\SPROGSimCMRICom8.jmri\profile\jmri-[long string of characters] to use new profile ID."? When I attempt to name the new profile simply "C8" it works fine.? However, a fully populated directory tree is created in both cases.

I tried a few more cases and it seems to work OK with some profile names and not others.? I thought I found a pattern related to name length (6 or less vs more), but then I found other cases that didn't work..

May have been an issue for a while as I tried this on JMRI 14.17.3 and got the same behavior.

Jerry
___________________________________
jerryg2003@...

Re: Test version 4.17.7 of JMRI/DecoderPro is available for download

#166988

On Fri, Dec 13, 2019 at 08:30 AM, Bob Jacobsen wrote:

Test version 4.17.7 of JMRI/DecoderPro is available for download.

Thank you, Bob.
I have updated my RPi-JMRI image for the RaspberryPi to include JMRI 4.17.7, and published it here: https://mstevetodd.com/rpi
Hopefully, some users will be able to load this and provide additional feedback before the 4.18 release.
--SteveT

Re: Decoder Pro not seeing Power Cab #nce #powercab

#166987

开云体育

Andrew,

On 17 Dec 2019, at 7:07 AM, andrew.woolman <apwool@...> wrote:

SilabsUSBDriver.kext installed
??SilabsUSBDriver64.kext installed

This indicates you've got obsolete SiLabs drivers hanging around, probably in "/System/Library/Extensions/".

Delete all existing SiLabs drivers from?both?"/System/Library/Extensions/" and?"/Library/Extensions/". Then start again and follow the instructions below.

Installing NCE USB on Mac

===================

- Plug the USB side of the NCE USB into your Mac (you do not need to plug it into the PCP to do the next few steps.

- Go to System Report from Apple Menu->About This Mac->More Info.

- Look in the USB section and see if a Silicon Labs device is present. If not you have a USB hardware fault; cable, connector, port or device. That will need resolving before you go any further.

- Download and install SiLabs CP210x drivers from <>.

- Unplug the NCE USB.

- Open a Terminal Window (from /Applications/Utilities), copy and paste the following command in EXACTLY (including spaces and punctuation) then press Enter.

while : ;do clear;ls -lt /dev|head;i=$((i+1));echo $i;sleep 1;done

- This command should show about 10 lines of output and then sit looping, with a counter incrementing every second.

- Plug your device back in and wait a few seconds. Two new items with names like cu.SLAB_USBtoUART and tty.SLAB_USBtoUART should appear in the list. They should disappear if you unplug your device. If this does not happen, you do not have the correct drivers installed for your device and you will need to solve that before proceeding further.

(With later macOS versions, you'll probably need to go to System Preferences->Security & Privacy->General at this stage and allow the new Silabs driver to load the first time.)

- Once you have found your device, write down the name you see.You want the cu.xxx version not the tty.xxx version.

- If you have got this far you know your device is be being seen by the Mac, that it has a matching driver installed and the name of the connection port "cu.xxx" you need to select in JMRI.

<>

Configuration Instructions

===================

Here are the best settings for JMRI and jumpers for Power Cab (and also SB5).

Make sure you always unplug/replug both cables on the NCE USB after changing jumpers.?

It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems).

Power Cab Instructions

=================

The correct settings for a Power Cab V1.65 or V1.28 (as shown when the Power Cab starts up) and an NCE USB V6 (or you are not sure of the USB version) ?are:

- All USB Jumpers off (or at least 2, 3 & 4. Jumper 1 is ignored).

- JMRI preferences are:

-- System manufacturer: NCE

-- System connection: ?NCE USB

-- Serial port: <whatever is appropriate for your system>

-- USB version: V6.x.x

-- System: PowerCab

-- Additional Connection Settings checkbox ON

--- Baud rate: 9600.

The JMRI console log should then report V6.3.0. If it reports V7.3.0 and your Power Cab is V1.65, use the settings below instead.

If you don't get a version number or the system does not work, Use Help->System Console...->Copy to clipboard and paste into a post for us to see.

The correct settings for a Power Cab V1.65 or V1.65b and an NCE USB V7 ?are:

- All USB Jumpers on (or at least 2, 3 & 4. Jumper 1 is ignored).

- JMRI preferences are:

-- System manufacturer: NCE

-- System connection: ?NCE USB

-- Serial port: <whatever is appropriate for your system>

-- USB version: V7.x.x

-- System: PowerCab

-- Additional Connection Settings checkbox ON

--- Baud rate: 19200.

The JMRI console log should then report V7.3.7.

SB5 Instructions

============

The correct settings for an SB5 and an NCE USB V7 ?are:

- USB Jumper 4 on. All others off (or at least 2 & 3. Jumper 1 is ignored).

- JMRI preferences are:

-- System manufacturer: NCE

-- System connection: ?NCE USB

-- Serial port: <whatever is appropriate for your system>

-- USB version: V7.x.x

-- System: SB5

-- Additional Connection Settings checkbox ON

--- Baud rate: 19200.

The JMRI console log should then report V7.3.1.

General Troubleshooting

==================

If the system does not work after this:

- If your SB5/Power Cab is V1.65 rather than V1.65B, you may have been affected by a firmware issue (triggered by a System Reset).

- Your NCE USB may be set to a bad cab address (V7 only).

- There is a potential hardware issue with the NCE USB/Power Cab combination.

In either case, go through the following :

- Quit JMRI.

- Ensure neither LED on the NCE USB is stuck ON. If so, power cycle the USB by unplugging it from the cab bus cable.

- Ensure you have no other throttles connected.

- Restart JMRI and immediately go to Configure USB Interface under the NCE menu.

- Set the Cab ID to 3.

- Attempt a JMRI operation (use a throttle, Identify a decoder).

- The status line should stay green and it should work?

-If this does not work, do not fiddle with any other settings but instead:

-- Observe whether the Cab Bus LED on the NCE USB is stuck on and report back.

-- Use Help->System Console...->Copy to clipboard and paste into a post for us to see.

Re: Rotation of layout #layouteditor

#166986

See?: “LayoutEditor-Add-ability-to-rotate-entire-layout”.

Re: Verify Initial Setup

#166984

开云体育

Sorry, here is the log:

? 10 apps.AppsBase???????????????????????? INFO? - This log is stored in file: C:\Documents and Settings\KAREN\JMRI\systemfiles\messages.log [main]
??? 80 util.Log4JUtil??????????????????????? INFO? - * JMRI log ** [main]
??? 80 util.Log4JUtil??????????????????????? INFO? - This log is stored in file: C:\Documents and Settings\KAREN\JMRI\systemfiles\messages.log [main]
?? 110 apps.AppsBase???????????????????????? INFO? - DecoderPro 3 version 3.4-r23744 starts under Java 1.6.0_17 at Mon Jan 01 00:04:39 GMT-07:00 1990 [main]
? 2733 usbdriver.UsbDriverAdapter??????????? INFO? - NCE USB COM3 port opened at 9600 baud [main]
? 9643 util.FileUtil???????????????????????? INFO? - File path program: is C:\hoTrains\computerControl\jmri\run\ [main]
? 9643 util.FileUtil???????????????????????? INFO? - File path preference: is C:\hoTrains\computerControl\jmri\mikeG\ [main]
? 9653 util.FileUtil???????????????????????? INFO? - File path home: is C:\Documents and Settings\KAREN\ [main]
?13078 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 0 [Transmit]
?13269 nce.NceConnectionStatus?????????????? WARN? - Incorrect or no response from NCE command station [Transmit]
?23303 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 1 [Transmit]
?23423 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [Transmit]
?33448 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 2 [Transmit]
?33548 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [Transmit]
?43552 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 3 [Transmit]
?43652 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [Transmit]
?43662 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer:? [Receive]
?43662 nce.NceConnectionStatus?????????????? INFO? - NCE EPROM revision = 7.3.0 [AWT-EventQueue-0]
515881 jmrit.XmlFile???????????????????????? INFO? - No C:\hoTrains\computerControl\jmri\mikeG\roster\Proto_2000_E7_A.xml file to backup [AWT-EventQueue-0]

On 12/17/2019 12:48 PM, Mike G wrote:

Show quoted text

Hi,

I have no idea what happened. It was plugged into the cab buss, so I guess nothing should have happened. I still got the timeout status.

after finally hooking things up the proper way - using Power Cab and the NCE adapter, I was successful in reading decoders. The log after the first successful read is below. I am curious about why the timeouts. Also, If I use a later version of Decoder Pro, is it better at? figuring out which decoder it is? The reason I ask is that with two different locos it says it could be one of these - and shows about 6 options.

FYI - the Power Cab shows Pro Cab version 1,3 and Power Cab version 1.28C. All jumper positions are open on the USB adapter.

Thanks for your help, guys.

Peace,

Mike G.

On 12/17/2019 12:09 PM, Dave Heap wrote:

Ken and Mike,

On 17 Dec 2019, at 11:25 PM, Ken Cameron <kcameron@...> wrote:

Dave,

What changed about 410 seconds after you started JMRI that allowed JMRI to
see the command station? It does 10 second cycles to try to talk to the
command station. It times out at 10 seconds. After all that, it finally
worked. So something changed.

I assume that question was meant to be directed to Mike?

I'd like to know the answer to that as well.

Dave in Australia

-=-=-=-=-=-=-=-=-=-=-=-
?

Re: Verify Initial Setup

#166983

Hi,

I have no idea what happened. It was plugged into the cab buss, so I guess nothing should have happened. I still got the timeout status.

after finally hooking things up the proper way - using Power Cab and the NCE adapter, I was successful in reading decoders. The log after the first successful read is below. I am curious about why the timeouts. Also, If I use a later version of Decoder Pro, is it better at? figuring out which decoder it is? The reason I ask is that with two different locos it says it could be one of these - and shows about 6 options.

FYI - the Power Cab shows Pro Cab version 1,3 and Power Cab version 1.28C. All jumper positions are open on the USB adapter.

Thanks for your help, guys.

Peace,

Mike G.

Show quoted text

On 12/17/2019 12:09 PM, Dave Heap wrote:
Ken and Mike,

On 17 Dec 2019, at 11:25 PM, Ken Cameron <kcameron@...> wrote:

Dave,

What changed about 410 seconds after you started JMRI that allowed JMRI to
see the command station? It does 10 second cycles to try to talk to the
command station. It times out at 10 seconds. After all that, it finally
worked. So something changed.I assume that question was meant to be directed to Mike?

I'd like to know the answer to that as well.

Dave in Australia


-=-=-=-=-=-=-=-=-=-=-=-

Re: Signal mast logic #signalmasts

#166982

If you don’t want the Approach (yellow) to show, you could

 1) Not have each mast protecting the following one.  Just delete those references.

or

 2) Configure your mast definitions so that the Approach is mapped to “light the green output”

Bob

On Dec 17, 2019, at 9:51 AM, James Anderson <james_anderson_999@...> wrote:

Many thanks for the replies. Once again my lack of understanding. I was looking for a simple red/green system on the lights. I disabled the approach aspect on the mast and so when it could not go yellow it went  to red (your mention of yellow highlighted that to me so thanks ). I think I might have to rethink what I want to do and perhaps put virtual masts in between physical masts to hide the yellow. 
--
Bob Jacobsen
rgj1927@...

Losing Block Value Contents on Start Up

#166981

JMRI Ver 14.7.3
Windows 10

? ? ?Why is the block values being cleared during startup if track power is already on?? ?This does not happen if track power is off.

Roger

Re: Verify Initial Setup

#166980

Ken and Mike,

On 17 Dec 2019, at 11:25 PM, Ken Cameron <kcameron@...> wrote:

Dave,

What changed about 410 seconds after you started JMRI that allowed JMRI to
see the command station? It does 10 second cycles to try to talk to the
command station. It times out at 10 seconds. After all that, it finally
worked. So something changed.I assume that question was meant to be directed to Mike?

I'd like to know the answer to that as well.

Dave in Australia