Locked
Re: JMRI / DCS240 set up question and why so slow?
Thank you for replying.? I do direct byte programming wherever I go, thank you for that confirmation.?
It just perplexes me that the speed of communication between the controller and locomotive in a non-programming environment (say, setting speed step from 0 to 80, or turning a forward light on or off) is relatively instant, whereas reading a small packet of data in the programming environment is remarkably slow. ? ?? Even if there are 120 CV settings on one sheet, why can't the software create ONE string and send that data packet instead of individual packets for each string??? I don't expect there to be a simple answer, nor do I expect there to be ANY answer... just things I think about as I watch the reading/writing color bars do their thing on the screen during a read or write.
In the end, the computer interface for programming decoders is a great and necessary achievement over throttle programming.? Keep up the good work!
|
Locked
Re: New user experience attention for the UX people
Really simple, and for everyone:?? "'The download links below are for all installs - new and update.? If you are updating from a version prior to x.xx.x, see the data migration steps that may be necessary in the installation notes.'
|
Locked
Re: New user experience attention for the UX people
Yes.? What Jan and Tom said (in his second thoughts) would be solve this problem 100%.
|
Locked
Re: New user experience attention for the UX people
I merged something similar to the suggestion below while doing the JMRI 4.14 update. I dialed it back a little bit, as it ended up being somewhat repetitive. Repetition can help understanding, but it can also cause the readers to say TLDR and not get good info. Bob On Dec 22, 2018, at 3:11 AM, Jan Carr <jan.carr20@...> wrote:
Bob: Reading through all this and looking at the downloads page again, I agree with tooons, the original poster when he says
just remove this entire line: "If you've previously installed a working version of the program, you only need to download and install one of the files listed here."
To clarify that the download files are for either new installs or updates, it may be worthwhile saying just that after the opening sentences as follows:
If you've never installed a version of this program before, please read the installation guide (on the left) for your computer type and layout hardware. They will show you how to install the things that are needed before the program will run. These additional preliminary steps are one-time only and not necessary when updating. The JMRI download files listed here can be used for either a new installation or updating an existing installation.
I understand that I can submit this change through the github process which I will do. But since the submission process is new to me I will be learning on the job so give me a couple of days.
Jan
-- Bob Jacobsen rgj1927@...
|
Let's start at the beginning.
Defined the JMRI connection to the SUSIC which is built with the RS232 parts to match the match the Keyspan. Baud rate and card configured to address 0?? Or is there an RS232 to RS485 adapter in the mix?
You see the SUSIC to set up the cards? These are the newer 32 bit cards or 24 bit?
If you've gotten the basics set up correctly do you get the 1 to 1 heart beat on the SUSIC when you start JMRI?
In your tables if you bring up the inputs can to read them with a jumper to "ground"?
Do you see the data lights blink on the SUSIC as you try to set switch outputs or read inputs?
There's more we can test but this should get you started.
Jim Albanowski
|
Locked
Re: MQTT Connection in JMRI
Dave,
If you made a mistake you think anybody else might make, let us know. It
might serve to help others avoid the same hang up. It is like the OpSig
rule: Only make new mistakes.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
Locked
Re: Virtual Sound Decoder - Clicks on looped sound files
Hello Tim,
Creating a clean loop sound could be challenge. I also have the experience that taking a zero crossing point may be insufficient.
Another cause for a "bad click" could be a bug in a JMRI audio library. That issue was resolved in JMRI 4.3.2. So, please update, if you have installed an older version.
On the XML config file.
Right, the fade-in-time and fade-out-time is set in milliseconds. But it's not yet implemented in Diesel sounds.
As a reference to the XML commands may be helpful:
-
-
Have you already tried the EMD_645_Turbo.vsd (for a download see )? There is a slight click on notch 2, but other notches are fine.
Klaus
Am 22.12.2018 um 21:35 schrieb Timothy Miller:
toggle quoted message
Show quoted text
Hello all,? I have had much success with the virtual sound decoder except in one area.? I have created my own decoder config and sound files and am having issues with the Looped throttle notch sounds having a very bad click as each loop restarts.? ?When creating my audio files, I was extremely careful to set my loop points at zero crossing points in the sound waves.? I checked the loop in my sound editor and everything was smooth. I have installed OpenAL as the directions state.? All functions work fine except the click in the output of the looped files.
Is there a setting that may be causing the sound file to not start exactly at the beginning?Is this a limitation to the OpenAL or the sound management system?
I noticed in the XML config file, there is a Fade in and Fade out setting.? I assume it is milliseconds.? The example scripts are set to 5.? I tried 0 and 10 with not noticeable changes.
I also have looked for a reference to the XML commands for the sound decoder and found none.? I learned what I needed by studying the example config files.
Any help here would be greatly appreciated.??Tim
Timothy Miller
|
Locked
Re: MQTT Connection in JMRI
Hey Sorry Guys, found my mistake. Got it working now.
Dave, Brisbane Australia
|
Locked
Re: MQTT Connection in JMRI
Hello All,
I wanted to have a go at configuring MQTT in JMRi 13.7. I have been able to connect to broker.hivemq.com and I have MQTT Dashboard on my phone. I tried to add a turnout to the turnout table for MQTT but I have not been able to get any notification on the dashboard.?
Is there a simple test setup that I can follow for testing?
Thanks in advance,
Dave, Brisbane Australia.
|
Locked
Re: Virtual Sound Decoder - Clicks on looped sound files
While my experience with jmri is very limited (so far), my professional expertise is in the audio realm. It is probably something like the decoder creating an endpoint in the waveform that didn't correspond to your zero crossing. Just chopping it randomly would very likely create a pop.
?If you'd like to email or post the file in question, I'd be happy to examine it for irregularities (if you feel it may be something in your original file).?
Another trick might be creating a cross fade at the suspected end/start point. ?
On Sat, Dec 22, 2018 at 4:19 PM Timothy Miller < tmiller@...> wrote: Hello all,? I have had much success with the virtual sound decoder except in one area.? I have created my own decoder config and sound files and am having issues with the Looped throttle notch sounds having a very bad click as each loop restarts.? ?When creating my audio files, I was extremely careful to set my loop points at zero crossing points in the sound waves.? I checked the loop in my sound editor and everything was smooth. I have installed OpenAL as the directions state.? All functions work fine except the click in the output of the looped files.?
Is there a setting that may be causing the sound file to not start exactly at the beginning? Is this a limitation to the OpenAL or the sound management system?
I noticed in the XML config file, there is a Fade in and Fade out setting.? I assume it is milliseconds.? The example scripts are set to 5.? I tried 0 and 10 with not noticeable changes.?
I also have looked for a reference to the XML commands for the sound decoder and found none.? I learned what I needed by studying the example config files.? ?
Any help here would be greatly appreciated.?? Tim
Timothy Miller
-- Andrew Roberts
Potomac Sound LLC
PO Box 223
Monrovia, MD 21770-0223
(301) 332-6111
Andrew@...
|
Locked
Re: DecoderPro Will Not Read Programming Track
123 is the key to the question. If you get "Found mfg 123 (Masoth Electronic, GMBH) version 123; no such decoder defined.", and/or all CVs return a value of 123 and long address 15,227 it is 100% certain that you cannot communicate with the decoder and that one of two possibilities have happened: 1) Preferences->Defaults has Service Programmer (and possibly other items) set to Infernal. 2) Preferences->Connections has System Connection set to Simulator. Possibility (1) is the most likely. It would most likely have occurred due to a previous failure to open a connection. If there is no alternative to Infernal, you currently have a problem with the connection to your DCC system and you need to resolve the connection problem before proceeding. If an alternative is available select that, restart JMRI and try again. Warning, the Infernal problem can happen again in the future if you have any connection problems. See comments at: /g/jmriusers/message/153294This will be fixed in JMRI V4.14 -- Dave in Australia
On 23 Dec 2018, at 6:51 AM, Norman Beveridge via Groups.Io <norman.beveridge@...> wrote:
I need help with accessing the programming track, which previously worked perfectly, but no longer. For some reason the program will no longer correctly read values for the CVs when the loco is on the programming track. It now reads 123 as the value for each and every CV. Yet my NCE controller does correctly read the values. Maybe I have something set up wrong?
|
Locked
Re: DecoderPro Will Not Read Programming Track
My version is 4.11.4+R4534304.
I checked defaults, and yes it had changed to internal.? I reset to NCE as you suggested.? Now working perfectly.? THANKS to Peter and Tom.? I will get the upcoming version, and hopefully this problem is fixed.
Thanks again.
|
Locked
Re: Virtual Sound Decoder - Clicks on looped sound files
Hey Timothy,
It may indeed be something else, something like you hypothesized... but, it might be the nature of the waveform on either side of the zero crossing. ?For example, if the signal is throttling downward towards negativity, and then jumps upward from zero, that ¡®could¡¯ appear to be a digital brick wall.
Or not:),
jim
PS sometimes digitalization doesn¡¯t like a given ¡®clean¡¯ zero crossing... have you tried a different crossing nearby?
|
I'd say start by confirming the node configuration is showing the right type
and bits of the I/O cards on the SUSIC. Next confirm you have the right
turnout names for those cards. So the turnouts would match the sensor
numbers but only for half of them. So if the sensors were numbered (for 32
bit cards) CS1-> CS64, the turnouts would be CT1->CT32.
Next would be confirming that the command to the node is changing correctly.
Use the CMRI Monitor to watch the traffic. Key would be the output bit
string changes as you change the turnouts in the JMRI table. That would
confirm JMRI is sending the right information.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
-receiving inputs from sensors- blocks indicate occupied correctly on layout panel -can't get turnouts to operate - turnout simulation works on panel - cmri hardware is one Susic node with one output card & two input cards -the turnouts are connected with SM2's - they will operate the turnouts if an output signal is manually applied turnouts should operate by clicking on them on the layout, correct? computer information :
Inspiron 5537
Windows 7
JMRI 4.12
Java 1.8.0_191
Keyspan K19H usb adapter - com 4
DCC - EasyDcc
|
Sorry Peter,
I had actually thought I had posted it on the NCE Board. But will do.
Thank
Dave
Sent from my iPhone 6 Plus
toggle quoted message
Show quoted text
On Dec 22, 2018, at 14:36, Peter Ulvestad <ulvestad@...> wrote:
Not JMRI related. You should take this discussion to the NCE forum.
/g/NCE-DCC
--
Peter Ulvestad
JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -
|
Locked
Virtual Sound Decoder - Clicks on looped sound files
Hello all,? I have had much success with the virtual sound decoder except in one area.? I have created my own decoder config and sound files and am having issues with the Looped throttle notch sounds having a very bad click as each loop restarts.? ?When creating my audio files, I was extremely careful to set my loop points at zero crossing points in the sound waves.? I checked the loop in my sound editor and everything was smooth. I have installed OpenAL as the directions state.? All functions work fine except the click in the output of the looped files.?
Is there a setting that may be causing the sound file to not start exactly at the beginning? Is this a limitation to the OpenAL or the sound management system?
I noticed in the XML config file, there is a Fade in and Fade out setting.? I assume it is milliseconds.? The example scripts are set to 5.? I tried 0 and 10 with not noticeable changes.?
I also have looked for a reference to the XML commands for the sound decoder and found none.? I learned what I needed by studying the example config files.? ?
Any help here would be greatly appreciated.?? Tim
Timothy Miller
|
Locked
Re: DecoderPro Will Not Read Programming Track
Go to your preferences and check your defaults tab, most likely have changed to internal. Change back to NCE.
The update JMRI to 4.14 when it is released, hopefully in the next day or two.
--
Peter Ulvestad
JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -
|
Locked
Re: DecoderPro Will Not Read Programming Track
Norman, What version of Jmri?? Your symptom points to Preferences - Defaults being set to Internal. Jmri? 4.10 had a problem automatically doing this and not telling you. It continued into 4.12. I understand 4.14 due in a few days has this fixed. In the meantime, go to Edit-> Preferences -> Defaults and change anything set on Internal to your correct System. Save changes (lower left corner) and restart Jmri. Tom Wilson
Colorado Springs, CO
On Sat, Dec 22, 2018, 12:51 PM Norman Beveridge via Groups.Io <norman.beveridge= [email protected] wrote: I need help with accessing the programming track, which previously worked perfectly, but no longer.? For some reason the program will no longer correctly read values for the CVs when the loco is on the programming track.? It now reads 123 as the value for each and every CV.? Yet my NCE controller does correctly read the values.? Maybe I have something set up wrong?
I am open to suggestions.
I tried searching for a related topic, but found nothing.? But then I am not good with key words.
|
Not JMRI related and should be moved to a more appropriate forum.
--
Peter Ulvestad
JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -
|
Bob Jacobsen
Ken Cameron
Dave Lowe
Andrew Roberts
Jim Wells
Peter Ulvestad