|
I think I have reached the bowels of searching on how to get JMRI to recognize the AIU 01s when using an SB5.
I can confirm the following in my JMRI Preferences:
System Manufacturer: NCE
System Connection: NCE USB
USB Version - 7.x.x
Baud Rate: 9,600
USB Interface Jumper: 3 on (all others off).? NOTE: I have also tried 4 on (all others off)
The throttle reads: NCE SB5 - 1.65B
;
NOTE: I did see a YouTube that suggested using System: Power Pro instead of SBS on JMRI preferences.
At the end of the day, JMRI does not recognize my AIU01s.
I can control turnouts, etc., but have had no success in block detection.
Any assistance is greatly APPRECIATED!!!
Russ (Denver)
|
I would suggest that you use all four jumpers on and change your baud rate
to 19,200.
Next, I presume you confirmed the USB version by looking at the JMRI log
during startup?
Then, make sure the AIU has a valid address set. I'd suggest trying 3 first
for the address.
Add the sensor to JMRI, I'd use the address value and :1 for the value. So
3:1 for the first sensor. I'd add the box to set a range and give it a 14.
This way all your sensors are created.
Then try toggling a sensor with a wire from the common pin on the AIU to the
input pin, try more than one. Do any of the sensors change?
Last would be including your Help->Console Log, cut/paste it into the email.
It will tell us lots if something isn't working right.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
|
Riss, On 22 Nov 2019, at 12:19 PM, wilkinsonrussel@... wrote:
I think I have reached the bowels of searching on how to get JMRI to recognize the AIU 01s when using an SB5.
I can confirm the following in my JMRI Preferences:
System Manufacturer: NCE
System Connection: NCE USB
USB Version - 7.x.x
Baud Rate: 9,600
USB Interface Jumper: 3 on (all others off). NOTE: I have also tried 4 on (all others off) 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.
The throttle reads: NCE SB5 - 1.65B
;
NOTE: I did see a YouTube that suggested using System: Power Pro instead of SBS on JMRI preferences.
Not a good idea.
At the end of the day, JMRI does not recognize my AIU01s.
I think Ken has the clue. More below...
I can control turnouts, etc., but have had no success in block detection.
1) Once you've made the setting changes I recommend above, make sure you are seeing V7.3.1 being reported in the JMRI console log. 2) Make sure you can still control turnouts, run trains etc. 3) The only valid addresses for an AIU with SB5 are the range 2-10 inclusive, but it must not clash with other connected devices (throttles, NCE USB, etc.). The range 8-10 is preferred because ordinary throttles can't use this range, only NCE USB, AIU, Mini Panel (type 'C' throttle-class devices). 4) Go to the NCE->Show Cabs menu. You should be able to see your Pro Cab and the NCE USB, plus any other plugged-in devices. You may need to Refresh a couple of times to see everything. 5) Pick a valid free address in the range 2-10 for your AIU and set the jumpers as per the AIU manual. Note the actual switches orientation and ON-OFF positions may be confusing. 6) Plug the AIU in and do a couple of Refreshes in the Show Cabs menu. The AIU should appear at your chosen address. 7) When (and only when) you have the AIU appearing in Show Cabs, you can start creating sensors, as per Ken's instructions. The address format is xx:nn where xx is the NCE cab bus address and nn is 1 to 14 for the sensors on that board. "Use Create A Range" of 14 to save work. The actual system names created will be non-intuitive and have gaps. 8) If your sensors don't start responding to inputs, there are further troubleshooting steps you can take by viewing the NCE Command Monitor, but we can cover that later. Dave in Australia
|
Ken,
You da man!
All jumpers, baud 19,200 and AIU cab addresses of 4-6 work.
Not sure where you live, but I owe you a dinner!
Many Thanks,
Russ
toggle quoted message
Show quoted text
On Nov 21, 2019, at 6:43 PM, Ken Cameron <kcameron@...> wrote:
?I would suggest that you use all four jumpers on and change your baud rate
to 19,200.
Next, I presume you confirmed the USB version by looking at the JMRI log
during startup?
Then, make sure the AIU has a valid address set. I'd suggest trying 3 first
for the address.
Add the sensor to JMRI, I'd use the address value and :1 for the value. So
3:1 for the first sensor. I'd add the box to set a range and give it a 14.
This way all your sensors are created.
Then try toggling a sensor with a wire from the common pin on the AIU to the
input pin, try more than one. Do any of the sensors change?
Last would be including your Help->Console Log, cut/paste it into the email.
It will tell us lots if something isn't working right.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
|
Ken, Spoke to soon - I am not getting the following System Console readout:
2019-11-24 17:07:38,280 util.Log4JUtil ? ? ? ? ? ? ? ? ? ? ? ?INFO ?- * JMRI log ** [main]
2019-11-24 17:07:38,322 util.Log4JUtil ? ? ? ? ? ? ? ? ? ? ? ?INFO ?- This log is appended to file: C:\Users\wilki\JMRI\log\messages.log [main]
2019-11-24 17:07:38,330 util.Log4JUtil ? ? ? ? ? ? ? ? ? ? ? ?INFO ?- This log is stored in file: C:\Users\wilki\JMRI\log\session.log [main]
2019-11-24 17:07:38,350 apps.Apps ? ? ? ? ? ? ? ? ? ? ? ? ? ? INFO ?- PanelPro version 4.16+R6f9aced starts under Java 1.8.0_191 on Windows 10 x86 v10.0 at Sun Nov 24 17:07:38 MST 2019 [main]
2019-11-24 17:07:39,131 apps.Apps ? ? ? ? ? ? ? ? ? ? ? ? ? ? INFO ?- Starting with profile Minturn__Leadville.3ec3124a [main]
2019-11-24 17:07:40,847 node.NodeIdentity ? ? ? ? ? ? ? ? ? ? INFO ?- Using 52ab71e0-0a5b-11e9-8000-00051bd280dd as the JMRI storage identity for profile id 3ec3124a [AWT-EventQueue-0]
2019-11-24 17:07:41,347 xml.AbstractSerialConnectionConfigXml INFO ?- Starting to connect for "NCE" [main]
2019-11-24 17:07:42,581 usbdriver.UsbDriverAdapter ? ? ? ? ? ?INFO ?- NCE USB COM3 port opened at 19200 baud [main]
2019-11-24 17:07:42,699 nce.NceConnectionStatus ? ? ? ? ? ? ? INFO ?- NCE EPROM revision = 7.3.7 [AWT-EventQueue-0]
2019-11-24 17:07:43,764 util.FileUtilSupport ? ? ? ? ? ? ? ? ?INFO ?- File path program: is C:\Program Files (x86)\JMRI\ [main]
2019-11-24 17:07:43,764 util.FileUtilSupport ? ? ? ? ? ? ? ? ?INFO ?- File path preference: is C:\Users\wilki\JMRI\Minturn__Leadville.jmri\ [main]
2019-11-24 17:07:43,779 util.FileUtilSupport ? ? ? ? ? ? ? ? ?INFO ?- File path profile: is C:\Users\wilki\JMRI\Minturn__Leadville.jmri\ [main]
2019-11-24 17:07:43,779 util.FileUtilSupport ? ? ? ? ? ? ? ? ?INFO ?- File path settings: is C:\Users\wilki\JMRI\ [main]
2019-11-24 17:07:43,779 util.FileUtilSupport ? ? ? ? ? ? ? ? ?INFO ?- File path home: is C:\Users\wilki\ [main]
2019-11-24 17:07:43,779 util.FileUtilSupport ? ? ? ? ? ? ? ? ?INFO ?- File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2019-11-24 17:07:45,047 PanelPro.PanelPro ? ? ? ? ? ? ? ? ? ? INFO ?- Main initialization done [main]
2019-11-24 17:08:53,446 nce.NceSensorManager ? ? ? ? ? ? ? ? ?WARN ?- timeout awaiting poll response for AIU 6 [NCE Sensor Poll]
2019-11-24 17:08:53,446 jmrix.AbstractMRTrafficController ? ? WARN ?- Timeout on reply to message: 9B 06 consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2019-11-24 17:08:53,663 jmrix.AbstractMRTrafficController ? ? WARN ?- timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread]
2019-11-24 17:09:33,479 nce.NceSensorManager ? ? ? ? ? ? ? ? ?WARN ?- timeout awaiting poll response for AIU 6 [NCE Sensor Poll]
2019-11-24 17:09:33,479 jmrix.AbstractMRTrafficController ? ? WARN ?- Timeout on reply to message: 9B 06 consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2019-11-24 17:09:33,697 jmrix.AbstractMRTrafficController ? ? WARN ?- timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread]
2019-11-24 17:10:13,496 nce.NceSensorManager ? ? ? ? ? ? ? ? ?WARN ?- timeout awaiting poll response for AIU 5 [NCE Sensor Poll]
2019-11-24 17:10:13,496 jmrix.AbstractMRTrafficController ? ? WARN ?- Timeout on reply to message: 9B 05 consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2019-11-24 17:10:13,531 jmrix.AbstractMRTrafficController ? ? WARN ?- timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread]
2019-11-24 17:10:18,930 audio.JoalAudioFactory ? ? ? ? ? ? ? ?INFO ?- Initialised JOAL using OpenAL: vendor - OpenAL Community version - 1.1 ALSOFT 1.15.1 [Listed Table Generation]
2019-11-24 17:10:53,499 nce.NceSensorManager ? ? ? ? ? ? ? ? ?WARN ?- timeout awaiting poll response for AIU 6 [NCE Sensor Poll]
2019-11-24 17:10:53,499 jmrix.AbstractMRTrafficController ? ? WARN ?- Timeout on reply to message: 9B 06 consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2019-11-24 17:10:53,704 jmrix.AbstractMRTrafficController ? ? WARN ?- timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread]
2019-11-24 17:11:33,501 nce.NceSensorManager ? ? ? ? ? ? ? ? ?WARN ?- timeout awaiting poll response for AIU 5 [NCE Sensor Poll]
2019-11-24 17:11:33,501 jmrix.AbstractMRTrafficController ? ? WARN ?- Timeout on reply to message: 9B 05 consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2019-11-24 17:11:33,706 jmrix.AbstractMRTrafficController ? ? WARN ?- timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread]
On Thu, Nov 21, 2019 at 6:43 PM Ken Cameron < kcameron@...> wrote: I would suggest that you use all four jumpers on and change your baud rate
to 19,200.
Next, I presume you confirmed the USB version by looking at the JMRI log
during startup?
Then, make sure the AIU has a valid address set. I'd suggest trying 3 first
for the address.
Add the sensor to JMRI, I'd use the address value and :1 for the value. So
3:1 for the first sensor. I'd add the box to set a range and give it a 14.
This way all your sensors are created.
Then try toggling a sensor with a wire from the common pin on the AIU to the
input pin, try more than one. Do any of the sensors change?
Last would be including your Help->Console Log, cut/paste it into the email.
It will tell us lots if something isn't working right.
-Ken Cameron, Member JMRI Dev Team
|
Russel,
Since the log shows the line:
2019-11-24 17:07:42,699 nce.NceConnectionStatus INFO - NCE
EPROM revision = 7.3.7 [AWT-EventQueue-0]
We know you are talking to the USB ok. Now it would seem you have it looking
for a AIU device at cab 6 address. The log shows no response for it. Same
for a device using cab 5 address. Do you have other AIU boards addressed? Do
they work?
One thing I don't recall you mentioning is the firmware version in the SB5.
Depending on that, address issues might exist. Also, what is the cab id for
the USB board you are using? That will give another clue.
I recall 1.65B had a problem with falling back to the smaller range equal to
the 1.28 firmware is a command station reset had ever been performed. So if
you check that, it could be important.
In the meantime you could test the AIU at cab id 2, 3, 4 as a test, using
whatever isn't being used by the USB. For that test, a throttle isn't
needed. That can confirm the boards are using. Of hand, I'm guessing a
problem with the address dip switches could be the likely issue.
Try using the command "NCE->Show Cabs" it will confirm what cab ids are in
use. Hit the refresh once or twice just to make sure. This is the best way
to see if you have an address issue with the boards.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
|
In your system console text, it shows that there is a response to the command to poll the AIU, a "30" which means command not supported.? I believe you need to have your AIUs in a lower address range for it to work in your setup.? So I think your very close to getting it working.
Dan
|
Found this on the NCE site with regards to AIUs:
Valid cab addresses (for cabs in) a Powercab system are 2,3,4, or 5. Total of 4 actual cabs. 6 and 7 are unused. 8,9 and 10 can be used for other cab devices (AIU,USB) only.
?Valid cab addresses (for cabs) in an SB5 system are 2,3,4,5, 6 and 7. Total of 6 actual cabs. ?8,9 and 10 can be used for other cab devices (AIU,USB) only.
?If the AIU cab address is higher than 10 it will not work due to the limits of the command stations.
|
Here's a link to a table that shows how to properly configure the jumpers for the USB.? I believe you should set up your jumpers so you get a 7.3.1 response, not a 7.3.7 that's showing in your console text.
Dan
|
Here's a link to a table that shows how to properly configure the jumpers for the USB.? I believe you should set up your jumpers so you get a 7.3.1 response, not a 7.3.7 that's showing in your console text. You are quite correct, as I had posted in an earlier message on this thread, which shows exactly what jumper and JMRI settings to use. It appears Russ may not have seen it:
Dave in Australia
|
Valid cab addresses (for cabs in) a Powercab system are 2,3,4, or 5. Total of 4 actual cabs. 6 and 7 are unused. 8,9 and 10 can be used for other cab devices (AIU,USB) only.
?Valid cab addresses (for cabs) in an SB5 system are 2,3,4,5, 6 and 7. Total of 6 actual cabs. ?8,9 and 10 can be used for other cab devices (AIU,USB) only.
?If the AIU cab address is higher than 10 it will not work due to the limits of the command stations.
Correct, but there's further qualification needed regarding firmware versions:
If your Power Cab firmware (second screen at startup of your Power Cab, after the "Pro Cab V1.3" message) is: - "V1.28C" the only valid addresses for extra cabs are 3 & (unofficially) 4. - "V1.65" the only valid addresses for extra throttles ?are 3, 4 and 5. Non-throttle devices such as the NCE USB, Mini Panel or AIU can also use addresses 8, 9 & 10. However if you have ever done a System Reset, you will have lost all the extra addresses and be back to the V1.28C restrictions. - "V1.65B" the only valid addresses for extra throttles ?are 3, 4 and 5. Non-throttle devices such as the NCE USB, Mini Panel or AIU can also use addresses 8, 9 & 10.
Similar ?comments apply to the SB3/5 with the range 2-5 for V1.28 and 2-7 for V1.65B.
Dave in Australia
|
I've found better results with the 7.3.7 (all jumpers on) setting.
Effectively it says the USB will attempt to pass all commands to the command
station. All the other settings have combinations of restrictions that match
different versions of different command station.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
|
Ken, On 25 Nov 2019, at 2:44 PM, Ken Cameron <kcameron@...> wrote:
I've found better results with the 7.3.7 (all jumpers on) setting.
Effectively it says the USB will attempt to pass all commands to the command
station. All the other settings have combinations of restrictions that match
different versions of different command station. The original USB V7 documentation showed 7.3.7 for ALLSYS. The revised USB V7 documentation shows 7.3.7 for PowerCab. The revised USB V7 documentation shows 7.3.1 for SB5 (19,200). The revised USB V7 documentation no longer shows ALLSYS. Dave in Australia
|
Ken Cameron