I have successfully created a few Signal Heads? (and then Signal Masts) to test my understanding of the process.? I then went to edit the raw xml file to create all 64 possible "turnouts" to use as signal heads for my 2 SE8C boards.? In the process, I noticed that there's a comment, the significance of which I can't seem to figure out.? In the xml file, it appears within the Turnout definition:

No
Thats a pr3 connected to a? command station in regular mode.??
Steve G.

On Aug 12, 2018, at 1:54 PM, Steve_G <RailRodder@...> wrote:
Command station consisting It is not enabled for PR3, it is enabled for "loconet over tcp" and LocoBuffer and appears to be enabled LocoBuffer II.

Ok, but that is PR3 As a command station right? ( I.e. the mode that allows using the PR3’s programming track outputs ). It should be anyway.

Paul

Command station consisting It is not enabled for PR3, it is enabled for "loconet over tcp" and LocoBuffer and appears to be enabled LocoBuffer II.

Steve G.

开云体育

Paul,

For me, the easiest method is to never create a Block. When I am creating a Layout Editor panel, I assign a block “user" name to the track component using the Edit context menu. If it is a new user name, the system will create the block automatically with the next available IBnnn.

Dave Sand

If I open the block table and select the 'Add' button I can then add 1 or more blocks. ?If I specify a block system name ?(e.g. IB1 ) and check 'Add a sequential range' I get blocks generated with system names of IB1, IB1:1 IB1:2 and so on. ?If I then edit a track segment on using the layout editor using the edit option on the segment's popup menu and select one of the 'IBx:y' system names as the block name for the block and hit 'Done' the dialogue doesn't close and the system log shows a null pointer exception. ?Conversely if I use the layout editor to create a new track segment and select one of the 'IBx:y' system names in the Block Name: drop down list *(e.g. IB1:3) a new track segment is created OK and assigned to newly created block with 'IB1:3' as the user name, so I now have two different blocks, one with IB1:3 as ?the system name and one with it as the user name. ?At the ?moment I suspect the easier approach is for me to generate a range of blocks with simple IB1, IB2, IB3 numbering manually.

I'm using version 4.13.2.

Regards

Paul

On Aug 12, 2018, at 12:06 PM, gritcityrailroad@... wrote:

Thanks. I thought I saw it enabled a couple of versions ago although I was probly mistaken. I just figured I did something to disable it.

Please double check your defaults.

On my Linux machine, I have noticed the default for Consist sometimes hides off the edge of the screen. Make sure it is set for your LocoNet connection.

Paul

开云体育

Thanks. I thought I saw it enabled a couple of versions ago although I was probly mistaken.? ?I just figured I did something to disable it.

Paul,
I noticed it a long time ago (yrs?) and then forgot about it,I can fix it this aft (my time), if someone doesn't get there first.
Steve G.

Mark,
what labels do you have set for buttons F1 and F2 ?

e.g? "Bell" and "Whistle" or "Horn", or something different?

Peter

开云体育

Hi Steve.
You are not missing anything, it's not enabled.
Steve G.

The LocoNet Consist Manager, which creates consists ( both “Universal” and Advanced ) in the LocoNet specific manner prescribed by Digitrax, is supposed to be enabled on all Digitrax command stations. ?If that isn’t the case any longer, then that is a bug we need to fix.

Hi Bob,
Thanks much! That was simple and worked perfectly (and I should have thought of it myself!).
Much appreciated.
Have fun!? :-)
Best regards,
Geoff Bunza

I think it’s been mentioned, but check out Those scripts are a very efficient way to get analog values (i.e. numbers) and digital bits into JMRI from an Arduino via a serial port.

Bob

On Aug 11, 2018, at 5:49 PM, JerryG via Groups.Io <jerryg2003@...> wrote:

Thanks for the ideas. I see a lot of experimenting ahead..

I’m currently connecting the Arduinos as C/MRI SMINI nodes which doesn’t suit my new purposes at all, allowing only sensor and turnout input (that is, zero or one) to JMRI. I need an interface where I can load JMRI memories (or reporters) with data so I can get numbers and characters from the layout to JMRI.

Jerry

--
Bob Jacobsen
rgj1927@...

You have to leave a reference to the SerialPort object (I.e. the thing that was returned when you called “open(..)” ) somewhere you can get it. Once you have that, you can call “close” on it whenever you want;

I.e. if you have

self.port = self.portID.open("JMRI", 50)

you need to keep that object around so you can later do

self.port.close()


Or store it in a global variable or whatever.

Bob

On Aug 11, 2018, at 8:07 PM, Geoffb <gbglacier@...> wrote:

Hi,
Question: I have a functioning script cal it scriptA working well using a serial port successfully as the input and output stream.
If I kill the script, the port is left open.
Is there a way to run a second script (call it scriptB) that can close the I/O streams and the previously opened port successfully?
The port is static, ie. the port can be explicitly known to both scripts.

The fact that the port remains open, prevents scriptA from being re-run.
Alternatively, can scriptA check to see if the port is already open and re-acquire it?

Any help, including specific scripts or pointers in the right direction would be much appreciated.
Thanks. Have fun! :-)
Best regards,
Geoff Bunza

--
Bob Jacobsen
rgj1927@...

JMRI’s “Turnout” concept is about _accessory_ decoders. They’re operated completely differently from how locomotive-style decoders are operated.

But you can write scripts to do this relatively easily:

*) Create an “Internal” turnout for each of your real turnouts. Call it whatever you want, with let’s say a user name like 200F12 (really doesn’t matter).
*) Do that for the entire group that runs on one address
*) You can now put those on panels, etc.

To connect them to your hardware
*) Start with the "jython/ThrottleFunctionForLight.py” script. It _almost_ does what you want, except it works from an internal Light instead of an internal Turnout. So you’ll have to change ON to THROWN, OFF to CLOSED, and a few “Light” references to “Turnout”. But once that’s done, whenever you change the internal turnouts mentioned above, e.g. on a panel, the script will notice that and send the corresponding function control.

Bob

On Aug 11, 2018, at 11:43 AM, Don Babcock via Groups.Io <donbab48@...> wrote:

Bob,

I can't tell you how to do it from a Digitrax throttle. I'm not a Digitrax guy and don't wnat to start a war by explaining why.

From any other system, I set the address for the decoder and press the function key that controls that turnout. Both NCE and Engine Driver ( the two systems I use at home) give me an indication of the state of the turnout.

What I want to do is set up a graphic indication under panel pro. I blindly assumed that a decoder for multiple turnouts used functions when I was building. It's my fault that I didn't check earlier that they used separate addresses for separate turnouts. Just trying to find a workaround.

Thanks for pointing to scripting. I'll take a look to see if I can handle that. It's been a few years since the days when I taught low level programing.

--
Bob Jacobsen
rgj1927@...

Hi Steve.
You are not missing anything, it's not enabled.
Steve G.


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.