开云体育

I have the Heljan DCC Turntable which I believe is similar to the Walthers Turntable. Whilst most of you are probably unfamiliar with the Heljan Turntable and MERG, what I would like to do is to control my turntable in JMRI. Can someone please advise the general setup required for the turntable and I shall explore the MERG modules to see if I can achieve this.
Best wishes
Peter

On Sun, Nov 3, 2019 at 11:21 AM, Klaus Killinger wrote:

I have adjusted this for VSD. If I select a Roster in VSDecoder Manager now, a Throttle will be opened automatically. Would that suit your needs?

Yes, if by that you mean, within VSDecoder Manager,?by selecting a Roster and then a Roster Entry two events happen:
1) VSD Manager (with Engine Start and function buttons) opens
2)JMRI throttle opens.

If this is so, do I have to update JMRI?

Right now I've linked the VSD files to a particular loco. So when I select a Roster and then a Roster Entry the linked VSD profile is automatically selected and all I hit is OK.

Conrad

Hi Dave,
That's an interesting request, but not supported via the existing WiThrottle Server protocol, and I don't see it being added to it.
The hardware approach suggested by Jared sounds valid.
However, there might be other software-only paths worth pursuing that don't involve EngineDriver. Here are two that come to mind:
1) There are several SSH Android apps that basically provide a "button" on Android for running a command on RaspberryPi. I know people are using it for "shutdown" functions. Those might support sending the proper "date -s ....." commands, populated with current time from the Android.?
2) Pass the current time by remotely setting a memory variable in JMRI, then use a jython script to set the current time from that value. The memory variable could be set via a simple javascript program accessed from the Web Server.

--SteveT

Ken Cameron hit a similar error a long time ago:

It was thought to be fixed, but perhaps it’s recurred. It’s associated with extra files in your preferences directory. The minimal content for that is:

DecoderProConfig3.properties
log
preferences
My_JMRI_Railroad.jmri
nodeIdentity.xml
profiles.xml

You can find that by opening the Terminal application (from Applications -> Utilities), or if DecoderPro will cooperate for long enough:

Help meny -> select Locations... and then click the “Open Settings Location” button.

I’d be curious what else you have in that directory. Thanks

Bob


--
Bob Jacobsen
rgj1927@...

On Sun, Nov 3, 2019 at 01:43 PM, Klaus Killinger wrote:

It's not feasible by changing the engine tags. But it can be coded in VSD. It's possible to declare two function buttons, let's say "throttle_up" F6 and "throttle_down" F7. What should happen if I click on F6? I guess (1) play the accel-sound of the current notch and (2) loop the notch sound of the next notch. Right?

Klaus,

I'll play with that to see what happens.

Conrad

On Sun, Nov 3, 2019 at 01:31 PM, Klaus Killinger wrote:

Now the question is why button1 is looping the mid-file (idle.wav) without a click. The reason is that the mid-file process is looping the whole WAV file. This usually works well. VSD, however, separates the WAV file into several 250ms long parts. The issue might be the length of the last part.

Klaus,

Yes, I now remember the 250ms chopping up of the wav file.? So I have to look at the file lengths.? Maybe make them exactly n multiples of 250ms.

Conrad

Thank you! That screen shot was very helpful. Working on it…

Bob

On Nov 3, 2019, at 1:19 PM, Fran Giacoma <frangiacoma@...> wrote:

No trouble at all, Bob; I truly appreciate what you and the JMRI team do to make this hobby more enjoyable.

I did what you asked, but had the same problem as described above except the "About" section worked; Preferences caused it to bomb. I posted a new screen shot of the problem log in the Fran Giacoma album in the Photos. Also, here is a copy of the system console:

2019-11-03 16:15:48,922 util.Log4JUtil INFO - * JMRI log ** [main]
2019-11-03 16:15:50,080 util.Log4JUtil INFO - This log is appended to file: /Users/frangiacoma/Library/Preferences/JMRI/log/messages.log [main]
2019-11-03 16:15:50,081 util.Log4JUtil INFO - This log is stored in file: /Users/frangiacoma/Library/Preferences/JMRI/log/session.log [main]
2019-11-03 16:15:50,087 apps.AppsBase INFO - DecoderPro version 4.17.5ish+jenkins+20191030T1007Z+R8c99e77 starts under Java 1.8.0_231 on Mac OS X x86_64 v10.15.1 at Sun Nov 03 16:15:50 EST 2019 [main]
2019-11-03 16:15:50,365 gui3.Apps3 INFO - Starting with profile My_JMRI_Railroad.3f6a8dfb [main]
2019-11-03 16:15:50,441 node.NodeIdentity INFO - Using jmri-njWZSchJGhNiaa7fXjS0GE-3f6a8dfb as the JMRI storage identity for profile id 3f6a8dfb [AWT-EventQueue-0]
2019-11-03 16:15:50,582 xml.AbstractSerialConnectionConfigXml INFO - Starting to connect for "LocoNet" [main]
2019-11-03 16:15:50,583 jmrix.AbstractSerialPortController WARN - old profile format port speed value converted [main]
2019-11-03 16:15:50,973 locobufferusb.LocoBufferUsbAdapter INFO - LocoBuffer-USB adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2019-11-03 16:15:50,977 locobuffer.LocoBufferAdapter INFO - cu.usbserial-FTF5YQN port opened at 57600 baud with DTR: true RTS: true DSR: true CTS: true CD: false [main]
2019-11-03 16:15:51,027 loconet.LnPacketizer INFO - lnPacketizer Started [main]
2019-11-03 16:15:51,062 loconet.LnPacketizer WARN - Ignore LocoNet packet with bad checksum: 9A C2 [LocoNet receive handler]
2019-11-03 16:15:51,063 loconet.LnPacketizer WARN - run: unexpected LocoNetMessageException: {} [LocoNet receive handler]
jmri.jmrix.loconet.LocoNetMessageException
at jmri.jmrix.loconet.LnPacketizer$RcvHandler.run(LnPacketizer.java:317)
at java.lang.Thread.run(Thread.java:748)
2019-11-03 16:15:51,440 util.FileUtilSupport INFO - File path program: is /Applications/JMRI/ [main]
2019-11-03 16:15:51,440 util.FileUtilSupport INFO - File path preference: is /Users/frangiacoma/Library/Preferences/JMRI/My_JMRI_Railroad/ [main]
2019-11-03 16:15:51,441 util.FileUtilSupport INFO - File path profile: is /Users/frangiacoma/Library/Preferences/JMRI/My_JMRI_Railroad/ [main]
2019-11-03 16:15:51,441 util.FileUtilSupport INFO - File path settings: is /Users/frangiacoma/Library/Preferences/JMRI/ [main]
2019-11-03 16:15:51,442 util.FileUtilSupport INFO - File path home: is /Users/frangiacoma/ [main]
2019-11-03 16:15:51,442 util.FileUtilSupport INFO - File path scripts: is /Applications/JMRI/jython/ [main]


Fran

--
Bob Jacobsen
rgj1927@...

No trouble at all, Bob; I truly appreciate what you and the JMRI team do to make this hobby more enjoyable.

I did what you asked, but had the same problem as described above except the "About" section worked; Preferences caused it to bomb. I posted a new screen shot of the problem log in the Fran Giacoma album in the Photos. Also, here is a copy of the system console:


Fran

Am 03.11.2019 um 16:43 schrieb conrad:

Just a note on the manual notching idea.? As is obvious from the structure of the engine tags, manual notching using function buttons is not feasible.? The run, accel, decel can't work with just function buttons.? There is not way to smoothly transition up or down the notches.

It's not feasible by changing the engine tags. But it can be coded in VSD. It's possible to declare two function buttons, let's say "throttle_up" F6 and "throttle_down" F7. What should happen if I click on F6? I guess (1) play the accel-sound of the current notch and (2) loop the notch sound of the next notch. Right?


Klaus

Could you try something for me?

1) Drag the JMRI folder out of Applications to the trash
2) Reboot the Mac
3) Drag the new JMRI folder from the 4.17.5 installation virtual disk to the Applications folder

Then try DecoderPro again.

Thanks, and sorry for the trouble.

Bob

On Nov 3, 2019, at 7:01 AM, Fran Giacoma <frangiacoma@...> wrote:

Was running DecoderPro V4.16 on a MacBook Pro (mid 2016 model) using Catalina 10.15.1 and Java 8 Update 231 and I just installed the latest test version 4.17.5.
Same problems as described in my post #165018. Plus any of the options (Preferences, About, etc.) in the drop down under DecoderPro in the toolbar cause the error message (see my post #165019) to appear. I have to use Force Quit to get out of DecoderPro.

--
Bob Jacobsen
rgj1927@...

Conrad,

Am 03.11.2019 um 16:26 schrieb conrad:

I have made an interesting discovery about engine clicking sounds. I found an RDC recording that only had two notches, idle and run. Both of them sound perfect in WavePad Sound Editor (uncompressed, 8 bit wav) but within the engine tags they click (dropout?) at the end. The startup, shutdown, accel and decel have no clicks. So, I tried the idle one as a standalone function with the idea of manually notching the RDC. Well, to my surprise there are no clicks.

That's really creative. I've tried it. I created a function button1 with start-file (start.wav), mid-file (idle.wav) and end-file (stop.wav). It worked without a click, so far so good.

Next I would have to create a function button2 with start-file (idle-accel.wav), mid-file (notch1.wav) and end-file (decel-idle.wav).

But how could I pause button1, before I click on button2? The problem is that VSD is not designed to create such process flows.

Now the question is why button1 is looping the mid-file (idle.wav) without a click. The reason is that the mid-file process is looping the whole WAV file. This usually works well. VSD, however, separates the WAV file into several 250ms long parts. The issue might be the length of the last part.

You wrote "The startup, shutdown, accel and decel have no clicks". That's because these sounds are played only once at a time.

This points to something in the engine tags that is “causing” the clicks. Thus it may not be the wav files themselves as previously discussed.

No, it's an audio issue.

Klaus

JMRI is about your only option to deal with these excessively complex decoders.

^^^^^^^^^

Excessively?
Somehow to get the features people want complexity is required.

Dave,
Here you go:

Conrad,

Today I think that the "Load Throttles Layout" function is not the right way to do it.

A few days ago I looked at the "Throttle" button in window "DecoderPro:Entries" (bottom right). You have to select a Roster, then you can open a suitable Throttle.

I have adjusted this for VSD. If I select a Roster in VSDecoder Manager now, a Throttle will be opened automatically. Would that suit your needs?

Klaus


Am 03.11.2019 um 16:14 schrieb conrad:

Just a note on the manual notching idea.? As is obvious from the structure of the engine tags, manual notching using function buttons is not feasible.? The run, accel, decel can't work with just function buttons.? There is not way to smoothly transition up or down the notches.

However I am intrigued by the lack of clicks, pops, etc. when the engine run files are used with function buttons.

Conrad

HEADLINE:? NO ENGINE CLICKING SOUNDS FOUND WHEN FUNCTION BUTTON USED

I have made an interesting discovery about engine clicking sounds. I found an RDC recording that only had two notches, idle and run. Both of them sound perfect in WavePad Sound Editor (uncompressed, 8 bit wav) but within the engine tags they click (dropout?) at the end. The startup, shutdown, accel and decel have no clicks. So, I tried the idle one as a standalone function with the idea of manually notching the RDC. Well, to my surprise there are no clicks.

This points to something in the engine tags that is “causing” the clicks. Thus it may not be the wav files themselves as previously discussed.

Here are my engine tags:

<sound-event name="ENGINE" label="Throttle" buttontype="ENGINE">

<trigger name="ENGINE_STARTSTOP" type="THROTTLE">

<event-name>F4</event-name>

<target-name>ENGINE</target-name>

<action>NOTHING</action>

</trigger>

<trigger name="ENGINE_NOTCH" type="THROTTLE">

<event-name>SpeedSetting</event-name>

<target-name>ENGINE</target-name>

<action>CHANGE</action>

</trigger>

<trigger name="ENGINE_STOP" type="FLOAT" valtype="FLOAT">

<event-name>SpeedSetting</event-name>

<target-name>ENGINE</target-name>

<match>0.0</match>

<compare-type>LT</compare-type>

<action>STOP</action>

</trigger>

</sound-event>

<sound name="ENGINE" type="diesel3">

<fade-in-time>0</fade-in-time>

<fade-out-time>0</fade-out-time>

<gain>0.8</gain>

<start-sound>

<file>sounds/engine/rdc/rdc_startup.wav</file>

</start-sound>

<shutdown-sound>

<file>sounds/engine/rdc/rdc_shutdown.wav</file>

</shutdown-sound>

<idle-notch>1</idle-notch>

<!-- Only 2 engine files, idle & run. Click at end of each -->

<notch-sound>

<notch>1</notch>

<next-notch>2</next-notch>

<prev-notch>1</prev-notch>

<accel-limit>50</accel-limit>

<decel-limit>0</decel-limit>

<file>sounds/engine/rdc/rdc_idle.wav</file>

<accel-file>sounds/engine/rdc/rdc_idle_run.wav</accel-file>

<decel-file>sounds/engine/rdc/rdc_idle.wav</decel-file>

</notch-sound>

?

<notch-sound>

<notch>2</notch>

<next-notch>2</next-notch>

<prev-notch>1</prev-notch>

<accel-limit>100</accel-limit>

<decel-limit>50</decel-limit>

<file>sounds/engine/rdc/rdc_run.wav</file>

<accel-file>sounds/engine/rdc/rdc_run.wav</accel-file>

<decel-file>sounds/engine/rdc/rdc_run_idle.wav</decel-file>

</notch-sound>

And here are the tags for a function button (F25).? Ignore the REVERSE label, it’s an avatar:

<!-- F25 Reverse -->

<sound-event name="REVERSE" label="Reverse" buttontype="TOGGLE">

<trigger name="REVERSE_BUTTON_STOP" type="BUTTON">

<event-name>BUTTON</event-name>

<target-name>REVERSE</target-name>

<match>false</match>

<action>STOP</action>

</trigger>

<trigger name="REVERSE_BUTTON_START" type="BUTTON">

<event-name>BUTTON</event-name>

<target-name>REVERSE</target-name>

<match>true</match>

<action>LOOP</action>

</trigger>

<trigger name="REVERSE_STOP" type="BOOLEAN">

<event-name>F25</event-name>

<target-name>REVERSE</target-name>

<match>false</match>

<action>STOP</action>

</trigger>

<trigger name="REVERSE_START" type="BOOLEAN">

<event-name>F25</event-name>

<target-name>REVERSE</target-name>

<match>true</match>

<action>LOOP</action>

</trigger>

</sound-event>

<sound name="REVERSE" type="configurable">

<start-file>sounds/engine/rdc/rdc_startup.wav</start-file>

<mid-file>sounds/engine/rdc/rdc_idle.wav</mid-file>

<end-file>sounds/engine/rdc/rdc_shutdown.wav</end-file>

<start-sound_duration>4000</start-sound_duration>

<gain>0.5</gain>

</sound>

I'm going to try this with other VSD files that have engine clicks, pops, growls, etc.

Conrad

On Fri, Nov 1, 2019 at 05:22 AM, Klaus Killinger wrote:

Conrad,

Thanks for the confirmation and the explanations.

Now I would like to mention the following JMRI function (again on the risk that you already know this):
PanelPro > Tools > Throttles > Save Throttles layout
This allows to save one or more open throttle's. Of course there is also a "Load Throttles layout" function.

I'm curious if that would be helpful to you.

Klaus

Klaus,

I have no recollection of saving throttles but "Load Throttles Layout" shows the following:

5514 CB&Q 2-80-2 Heavy Mikado.xml
ThrottlesPreferences (T61laptop's conflicted copy 2019-10-04).xml
ThrottlesPreferences.xml
WiThrottlesPreferences (T61laptop's conflicted copy 2019-10-04).xml
WiThrottlesPreferences.xml

I do have a T62 laptop with JMRI but also am running on both a Raspberry Pi and now a old Dell (w/ Engine Driver on a tablet).

Conrad

PS I'm off to a bigger discovery.? See my post on clicking engine sounds.

Was running DecoderPro V4.16 on a MacBook Pro (mid 2016 model) using Catalina 10.15.1 and Java 8 Update 231 and I just installed the latest test version 4.17.5.?
Same problems as described in my post #165018. Plus any of the options (Preferences, About, etc.) in the drop down under DecoderPro?in the toolbar cause the error message (see my post #165019) to appear. I have to use Force Quit to get out of DecoderPro.

Fran Giacoma

Thanks for explaining that George. I'll simply swap them round on my older panels. In reality I never quite got my head around the Left and Right - whichever I did I seemed to get wrong and have to change it!

I'm glad you've also addressed the shapes on the web as that's a feature that I've just found and started to use - it makes so much difference to the layout being able to add a few platforms for instance. I now use the web output as my 'go to choice' as it's so convenient on tablets.

I'll look out for the changes when they appear in the next test release.

Andy