开云体育

I have Ubuntu and Java installed, but JMRI cannot see any serial ports, does anyone have ideas on how to expose them, the JMRI instructions say to change the permissions, but it expects you to know the addresses, and I am not sure Chrome OS makes them available to crouton/Ubuntu.
--
Ed Fitzgerald?
RF&P MRR

On Dec 2, 2019, at 11:05 AM, Daniel Kubarych <danandsharek@...> wrote:

?I understand there are work arounds to get the turnout behavior that we seek. Plan A was use the inverted option. That will not work because the option is grayed out. I am sure there is a Plan B and a Plan C. My original question was "Why is the inverted option grayed out?" Is it an idiosyncrasy of LCC?

Not all systems JMRI supports have invert options.

It really is there for two cases:
1) you miss-wire the physical turnout actuator ( which isn’t always possible...)
2) when you have to install the turnout actuator backwards.

Since LCC events don’t know if they are for the “Normal” or “Reverse” position, they don’t really care about the physical layout. We give them the associated meaning in JMRI when we associate them with a turnout.

Paul

Absolutely correct and the reason I deleted my " wrong interpretation " post. Just an average Joe, unfortunately.

Marc

Marc,

I believe you have interpreted the table in the SE8C manual incorrectly - something that I have done many times in the past; those tables make sense to the engineer at Digitrax, and perhaps a few others, but the average joe often finds them difficult to understand.

Doug Stuard tested the SE8C operation very carefully with respect to SE8C OpSw14 and documented his findings. My notes show that he provided his test results in post # 163882, but I cannot determine which list, and on which site, that post came from. Searches of the jmriusers groups.io list did not find that post.

Doug found that the default, SE8C OpSw14=Thrown, made the SE8C respond ONLY to the turnout control packets found on the DCC track signal on the "RailSync" wires. LocoNet "Data" wires were ignored (for signal control) when OpSw14=Thrown.

He found that when SE8C OpSw14=Closed, the SE8C responded ONLY to the turnout messages found on the LocoNet "Data" wires. The DCC track signal on the "RailSync" wires was ignored in this case.

Regards,
Billybob

Andy,

The short flippant answer is 'coz that's how it was written' ;-)

However, what should be the case is that each of the 'Add' dialogs provide (at least) three buttons - 'OK', 'Apply', 'Cancel'.

Behaviour of each of these as follows:

'OK' - create/make the changes specified then close
'Apply' - create/make the changes specified but remain open
'Cancel' - discard changes/abort creation then close

It would be good to know which dialogs you've noticed that are not following this convention so that we can sort out consistent behaviour throughout.

Thanks.

Best regards,

Matt H

Hi Dave
I've tried dev build and all looks fine to me. Thanks for tracking it down and fixing it!

As a side note, is there a particular reason that some of the 'Tables' Add dialogs close after adding a new item (such as sensors and turnouts) whereas others (such as Memory Variables and block) stay open and allow further additions until they are actively closed?

Thanks
Andy

Chris,

Which way are you powering the Se8c? I think if it is using track for power,
it sees the turnout commands that way. Most people find it much more stable
using a wall wart for power.

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

Wayne,

In JMRI, a "Virtual Signal" is simply one which does not correspond to any physical hardware.

If you wish to create a "Virtual Signal", using JMRI's "Aspect signaling" and "Signal Mast" system, "simply":
. Open the Signal Mast table ("Tools->Tables->Signals->Signal Masts").
. Activate that window's "add" button. This pulls up the "Add/Edit Signal Mast" tool window.
- Select a User Name (I would use the word "virtual" somewhere in there, as a reminder!).
- Select the appropriate "Signal System" - probably the same as your other signals, assuming that you are using JMRI's "Aspect Signaling".
- Select the appropriate "mast type"
- Select the appropriate "mast driver". To add a "virtual mast", you do not associate the signal mast with physical hardware, such as selecting "Turnout Controlled Mast".
- For a "Turnout Controlled Mast", for each aspect shown, select "Create New" and "Internal". Enter a number for the JMRI "internal" turnout which is to activate the aspect, and choose a "set state" to be associated with the aspect. No two (or more) aspects should use the same "internal" turnout number/"Set State" combination.
- As necessary, disable those aspects which the mast supports but which you do not want your "virtual mast" to display.
- Once all the aspect information is filled in, select the "Create" button at the bottom of the window.

"Et voila!" You have created a "virtual signal". You may use it like any other signal mast.

- You may place it on a Layout Editor panel.
- On a Layout Editor panel you may use it as part of "discovered" signal mast pairs.
- On a Layout Editor panel, you may mark it there as "hidden when not editing" so that it does not show up on any displayed panel.

"Simple?" Maybe not so simple, but not difficult, either.

Regards,
Billybob

Wayne,

? ? ?Are you using sensors for your hidden track?? Have you created blocks with those sensors?? ?I use virtual signal masts at the junction between certain blocks for traffic control.? Dont need the SE8C unless you want to display them on the physical layout.

Roger

You don't need any hardware as the signals are virtual, that is they don't physically exist. The can be created either as heads or masts as there is a virtual option for both. All my buffer stops are virtual signals as they are needed for signal mast logic, even though they don't change aspect.

Hi Dave,

Fix works for me, has also resolved?

Again thanks for your time on this,

Steve.

Duncan,

For each track that has a schedule, select none or blank in the edit track window.? That will remove that schedule from the track.? You can later re-select the schedule if you want to.? In the Locations window, under tools, there's print or preview, there you can get a list of your schedules that have been assigned to a spur.

Dan

Guys,

I am trying to setup some panels using Firefox Tablets. The first two seem to work fine. I was reading somewhere that I could add virtual signals to them. Can somebody point me to a tutorial? I'm looking to use this on my hidden staging area If I can.

I'm currently using a Digitrax system, will I need to buy a SE8C to do this?

Wayne

That makes good sense to me.? I will experiment and see if it proves out.
Thanks Billybob!

Chris

You can not change the baud rate as it is a fixed value. Changing it in Device Manager will not help either,

This bug was fixed in JMRI 4.17.3 but once the damage is done ( JMRI 4.16, 19200 baud)? the only way to fix it is re-view the Locobuffer-USB connection in Preferences under JMRI 4.17.3 or higher and save it.? No need to change anything? This will correct the NUL value that is in both profile.xml files and issue will be resolved.

Marc

Chris,

By default (according to the SE8C manual I have), the SE8C has its OpSw 14 set to "thrown". This means that the SE8C gets its control messages from the DCC track signal. And, if you have the NCE DCC track signal driving your Standalone LocoNet "RailSync" wires, this would explain why you saw the NTxx messages controlling the SE8C.

But if you have SE8C OpSw 14 set to its non-default value of "closed", the SE8C will pay attention to the LocoNet "Data" wires. Your Standalone LocoNet gets its signal on the LocoNet "Data" wires via the LocoBuffer-USB, and the SE8C would therefore be controlled via JMRI "LTxx" control messages.

I suspect you had OpSw at its "default" value when the JMRI NTxx turnouts controlled the SE8C signals, and had changed SE8C OpSw 14 to "Closed" before finding that the JMRI "LTxx" turnouts were controling the SE8C signals.

Regards,
Billybob

Bob,? that confirms one of my thoughts that it was likely picking up the NCE commands via the Rail Sync connection. But I don't know why it chose NT over LT and then changed it's mind.?
Thanks for the input.
Chris

The SE8c can take inputs from the LocoNet cable _or_ from the track DCC signal. It could be that it decided to use the track signal with LT wasn’t working. But I’m not sure why it would do that.

Bob

On Dec 3, 2019, at 11:27 AM, heilichr via Groups.Io <heilichr@...> wrote:

Strange behavior.... I just installed my first SE8C and during initial testing it would only respond to NT commands, not LT. It has since resolved itself. Wondering what would have caused this?

Summary of my of setup (it's a frankenstein lol).
NCE PowerPro command station
JMRI 4.17.3
Stand-alone Loconet with Locobuffer USB rev N.
2 BDL168s for detection
C/MRI connection running an Arduino that runs a servo and signal lights at one turnout
Tam Valley Octopus and Octocoder running 8 servos.

All this worked fine when I connected to SE8C to the loconet (and still does). When I first connected the SE8C it appeared to be working, except that the Digitrax test signal light would not change aspect when the correct LT turnout addresses were sent from JMRI. It just stayed Red over Red. I know the SE8C was properly connected to the loconet because I was able to read and write OP-Switch settings. The signal was setup in JMRI as LT turnouts and those turnouts were used to create an SE8C signal head. When I could not get the signal to work, I decided to connect a tortoise (SW address 01) and try it. By accident, I found it would respond to to switch address NT01 but not LT01.

This prompted me to send NT addresses to the signal heads and sure enough, they worked! But the story doesn't end here. I took the SE8C to my friends Digitrax layout to set the Board ID to 8. Back at home, I reinstall it and the now signals and tortoise no longer respond to the NT addresses. Instead, they correctly respond to LT addresses and not the NT.

Yes, it works fine now. But I'm the kind of guy who needs to understand why things happen to prevent future problems. Do any of you guys have any idea what could have caused this?
Any help, explanation or theories would be greatly appreciated!

Best Regards,
Chris Heili

--
Bob Jacobsen
rgj1927@...