Looked at screen shots. That is PanelPro, not DecoderPro and that is why I was not seeing same.? I program exclusively via DecoderPro.
'Tools' tab is not an option in DecoderPro.? That PanelPro method is a throw back to how DecoderPo USE to function, way back.

In previous versions we had the option to select the various Programmers. I see now that option is still valid but only via PanelPro.
That is taking the "long way home" to me. But interresting none the less.

Marc

开云体育

Your driver is not installed.?

Hi,

Trying to get my Mac to see JMRI. I have an NCE Power cab, NCE USB interface. Serial Port is not showing up in JMRI setup

MAC OS X Mojave 10.14.2
JMRI version 4.14
NCE USB Interface - Removed Jumpers
Installed ( I think) Silabs USB driver for Mac.

Mac System Info shows
CP2102 USB to UART Bridge Controller:
? Product ID:??? 0xea60
? Vendor ID:??? 0x10c4? (Silicon Laboratories, Inc.)
? Version:??? 1.00
? Serial Number:??? 0001
? Speed:??? Up to 12 Mb/sec
? Manufacturer:??? Silicon Labs
? Location ID:??? 0x14200000 / 12
? Current Available (mA):??? 500
? Current Required (mA):??? 100
? Extra Operating Current (mA):??? 0

NCE USB connected with coiled cable supplied with Power Cab to right port on the right side.

Trying to set up Decoder Pro
System Manufacturer : NCE
System Connection: NCE USB
Serial Port: Only thing that shows up is cu. Bluetooth
USB Version V7.x.x
System PowerCab
Connection Prefix N
Connection Name NCE
Baud Rate 9600


Ran while : ;do clear;ls -lt /dev|head;i=$((i+1));echo $i;sleep 1;done in Terminal window, cu.SLAB_USBtoUART and tty.SLAB_USBtoUART never appeared when I connected device

PowerCab v 1.3
Cab address 02

LED on NCE USB are off

Appreciate anyone that can assist...

Hello Bob,
opening the LocoNet Monitor with JMRI just started (no commands touched before) unveiled a particularly weird behavior, the screen was flooded with this continuously scrolling text, which made it impossible for me to clear:

18:05:09.260: [B0 78 27 10]? Interrogate LocoNet Turnouts/Sensors with bits a/c/b of 1/0/0; addresses...
??? 33-40, 97-104, 161-168, 225-232, 289-296, 353-360, 417-424, 481-488,
??? 545-552, 609-616, 673-680, 737-744, 801-808, 865-872, 929-936, 993-1000,
??? 1057-1064, 1121-1128, 1185-1192, 1249-1256, 1313-1320, 1377-1384, 1441-1448, 1505-1512,
??? 1569-1576, 1633-1640, 1697-1704, 1761-1768, 1825-1832, 1889-1896, 1953-1960, 2017-2024.
18:05:09.277: [B0 78 27 10]? Interrogate LocoNet Turnouts/Sensors with bits a/c/b of 1/0/0; addresses...
??? 33-40, 97-104, 161-168, 225-232, 289-296, 353-360, 417-424, 481-488,
??? 545-552, 609-616, 673-680, 737-744, 801-808, 865-872, 929-936, 993-1000,
??? 1057-1064, 1121-1128, 1185-1192, 1249-1256, 1313-1320, 1377-1384, 1441-1448, 1505-1512,
??? 1569-1576, 1633-1640, 1697-1704, 1761-1768, 1825-1832, 1889-1896, 1953-1960, 2017-2024.
18:05:09.277: [B4 30 00 7B]? LONG_ACK: Switch request Failed!

Note that the number of "Interrogate..." messages before the "Switch request Failed!" varies randomly. It seems to me that the program is continuously interrogating the command station on the status of some sensors (which I don't have, since the TC is only hooked up to the computer and a programming track on my desk; and I haven't configured any sensors in JMRI ever since this was a new clean install and all config files were cleared). I was curious to see what would happen so I let it run and after some time (not long, maybe a minute or less) the Twin-Center spontaneously reset itself, then the same text began scrolling again. The only way I found to stop it (so I could clear the screen) was to press the on/off power button (either on JMRI or on the TC, both ways worked). So I decided to investigate some more and I found out that starting DecoderPro with the track power already turned on wouldn't have this effect and the Monitor window was blank. I don't know if this issue can be related to the programming problems we are dealing with, but I thought it would be useful to tell you since it was preventing me from proceeding.
Anyway, here are the LocoNet traces you requested. This is what appears on the Monitor when trying to read decoder type from JMRI:

18:58:09.896: [EF 0E 7C 23 00 00 00 00 00 07 00 7F 7F 46]? Byte Read in Paged Mode on Service Track: CV8.
18:58:17.910: [EF 0E 7C 23 00 00 00 00 00 07 00 7F 7F 46]? Byte Read in Paged Mode on Service Track: CV8.
18:58:25.931: [EF 0E 7C 23 00 00 00 00 00 07 00 7F 7F 46]? Byte Read in Paged Mode on Service Track: CV8.
18:58:43.925: [83 7C]? Set Global (Track) Power to 'ON'.
18:58:43.945: [83 7C]? Set Global (Track) Power to 'ON'.

and this is what the Monitor says when I read CV 1 from the TC keypad:

19:02:34.553: [E5 07 01 49 42 41 56]? Uhlenbrock IB-COM / Intellibox II Start Programming Track.
19:02:43.240: [ED 1F 01 49 42 71 72 01 00 2C 70 00 00 00 00 10 01 00 2C 00 00 00 00 00 00 00 00 00 00 00 64]? Read CV in Direct Byte Mode from PT for Uhlenbrock IB-COM / Intellibox - CV: 1.
19:02:43.240: [81 7E]? Master is busy.
19:02:43.247: [B4 6F 01 25]? LONG_ACK: The Slot Write command was accepted.
19:02:46.808: [E7 0E 7C 00 00 00 72 07 00 1C 2C 7F 7F 2F]? Programming Response: Uhlenbrock IB-COM / Intellibox II Programming Read Was Successful: CV29 value 44 (0x2C, 00101100b).
19:02:50.547: [E5 07 01 49 42 40 57]? Uhlenbrock IB-COM / Intellibox II Stop Programming Track.

Note that the first and last messages appear respectively when I enter and exit programming mode on the Twin-Center, that is when the relay clicks.
I hope this information can help, looking forward to hear news :)
Best regards,
Marco

You configure the C/MRI nodes into JMRI, you first select a type, then (within the limitations of that type) you configure the input and output cards, which in turn determines how many Sensors and Turnouts that node has.

For your project, keeping them all on a single (virtual) C/MRI node will simplify the connection to your hardware. Lots of people have individual C/MRI nodes that are much larger than 64 inputs. That’s only two input cards; there’s a layout near hear with 5 input cars (more 115 connected inputs) and 7 outputs on a single node.

Bob

On Jan 10, 2019, at 6:35 PM, Don Weigt <dweigt47@...> wrote:

I hope the C/MRI IDs make sense. I don't know how many bits can be handled by one node, especially as my interface won't be using the usual C/MRI code or hardware. Right now, I have all 64 C/MRI sensors labelled as being in one node... As there's no hardware, the C/MRI error checking won't work yet.

--
Bob Jacobsen
rgj1927@...

Don,

Yes, blocks are always internal. If the occupancy sensor assignment specified the user name, then when that name is moved to a CMRI sensor, no change is required for the block.

Dave Sand

David,?

If the user can type anything in the Topic, then he/she could certainly type "sensor/" in anywhere as well, or what I'd like to enter "servoboard.0003/", then devices can certainly filter.

I would prefer we keep the Topic prefix in the Connection preferences, it would save some time typing "TxNamib/" for every one of the sensors and turnouts, but we might also have to field some support calls when there is not a trailing '/' or one to many of them in the combined topic!? (But if we only store the Topic in the tables, a quick search and replace in any text editor can solve that lazy typing issue.)

Speed

Seth,

Thanks for reminding me about the metrics. I hadn't thought of them since
I've not had to go looking for stuff like that and forgot some of the other
good stuff that got put into the system last year when the whole interface
for CMRI nodes got greatly improved. It really is a nice result compared to
what we used to have.

I'll have to play with that next time at the layout.

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

I am running JMRI 4.12.?? See the screenshot in the Photos section, it is in the album called "Programmer format question".

开云体育

I am running 7 SMINIS at 28800 baud and there is no noticeable response lag at all. Using a quad core i7 Mac mini with 10 go ram and a ssd.?

On my layout, I have 17 SMINI's and 1 SUSIC running at 19,200. I have not had any real problems with response time with JMRI. This was on a Windows 7 machine that is 7 years old. Prior to that, it was on a WIndows 2000 machine, which also was fine.
A couple of years ago, I switched over to VB6. No dissatisfaction with JMRI; just decided to have a go at VB6. It turned out I enjoyed doing the programming, which was a surprise to me. I found that there was a noticeable improvement in response time when I switched to VB6. It jumps out at you, more or less like getting a new computer does. But, JMRI was fine when I was using it.

Michael Pennie

开云体育

You don't need to compute the delays, use the "CMRINet metrics" under CMRI on the PanelPro control panel, it displays them for you.

From the topic Setting serial port speed for CMRI connection to JMRI
From: Ken Cameron
Date: Thu, 10 Jan 2019 08:11:39 EST
Jerry,

Keep in mind that JMRI will poll a node then give it time to reply. Then it
gets that reply or times out before polling the next node. So how fast each
node responds adds up quick. Use the Command Monitor under CMRI to watch the
traffic and do your timings. I would take a sample to a file for 10-20
seconds. Then using Excel I'd process it and compute the delays and
specifically look for how much any single delay varies. So if a given node
usually replying in 50mSec but every now and then 300mSec, I'd be curious
why.

-Ken Cameron, Member JMRI Dev Team


I find it hard to believe JMRI used with C/MRI is useful if it runs that slowly. It seems useless for things like scanning control panel switches and such. If that ~ 1 second cycle is to read all input data, it's too slow. If it's for each byte? Yikes!

?

As I recall, C/MRI boards simply respond when polled. That should be quite fast. What's causing the delay? Is C/MRI still running in BASIC? Is JMRI so complex it's slow?

?

My home brew I/O cycles through all inputs and outputs in less than 250 ms. Any slower becomes very annoying. I have 8 bytes of photodetector input data, and 16 of turnout position. These need to be read frequently, or they will lag too much.

My railroad as formerly built also had about 25 output bytes. They only need to be written to for initializing and when an output changes. But, the outputting needs to be fast, or it will delay the inputting too much.

What is realistic response time for driving signals and turnouts, and reading turnout positions and occupancy detectors? Is it really several seconds, or even longer?

-- 
Seth Neumann
Mountain View, CA

开云体育

FWIW, Chuck and I did some testing on systems with SMINIs, cpNodes and Mixed SMINI/cpNodes.??? Normal polling response is in the range of 25-50mS per node.??? It is just slightly longer with bigger nodes (that is the cpNodes have between 16 and 144 i/o and the fully built out ones poll a little slower, all SMINIs have 24 in/48 out so they are all the same).

Seth

Jerry,

Yes, having dead nodes in the list will kill the response time. It is
waiting and timing out for each of those. I wrote a script to enable/disable
polling per node, but now I think it is in the config page for the node.
Telling it to not bother what isn't there will make a world of difference.

-Ken Cameron, Member JMRI Dev Team

-- 
Seth Neumann
Mountain View, CA

Don,

To expand on Ken’s response, some other thoughts.

If you want a gap, include a small track segment and set it hidden. Make sure that it has the same block assigned as one its neighbors for block routing continuity.

When I am developing a new track plan, I assign each block a different color so that the block boundaries are very clear.

If your internal turnouts and sensors have user names that were used during panel development, then you can move the user names to the corresponding CMRI name. If you later restructure your CMRI configuration, you can move the names again.

Dave Sand

Don,

Yes the anchor point between two blocks are where you can place signals.
When drawing the layout, I'll activate a detector sensor to make it show on
the panel as an occupied block (you have to create the block and assign that
detector to it) so I can confirm where the ends are.

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

Bob

Why does it mean that?

Thanks Bob and Speed,

This is good news. So essentially a user can create and format any type of topic for there own use. I love it.

Great work guys. I look for to being able to use this system.

Thanks,

Dave, Brisbane Australia