Hi,
This is now working - thank you once more for your support
I had to change True to False for short addresses in
addressPanel.setAddress(throttle[0], True)
And I use a list rather than the roster to get each loco id because I want the throttles in alphabetical order to be able to find each throttle window quickly
|
Locked
Trying to place signals at edge connector boundary between panels
Hi,
Running 4.12 and trying to set signal heads at an edge connector boundary between two layout editor panels. I am getting the error:
Error - Block "B:2" exists, but is not assigned to track on this panel.
When I try from one panel. When I try from the other panel I get a different error:
Error - The two blocks entered do not join at an anchor point. Please enter the correct blocks and try again.
The blocks identified appear to be the correct ones. The edge connectors are linked and indicate as a "Block Divider".?
Signals have to be between block boundaries right? How is this supposed to work? Can signaling cross panel boundaries?
Thanks,
Allen
Mountain RR
|
Hi. Have you installed the system?? You can look for Steve Todd's setup,so connect an HDMI cable to the Pi to an HDMI device - monitor or HD TV.? Get a decent wireless or Blue Tooth keyboard and mouse. If you're going to use Steve's setup see this site?? ?. It's the easiest and has great and easily followed directions. You can set it the long and complicated way, so if you need directions, post again and I'll provide some instructions. Working with Linux takes a little getting used to - it's not unlike Windows in some aspects but commands are different. Steve suggests getting TightVNC client but I prefer RealVNC - you can easily access your devices offsite. My experience with TightVNC is the it works well with Virtual Network not a task for a beginner. Both VNC's work in the local environment so you can run a Pi headless (no input or output devices required), just? VNC cllient software.
On Wednesday, September 12, 2018, 3:33:27 PM EDT, Ken Bates via Groups.Io <kenbates@...> wrote:
Hi, ? Well I ordered it, and now it has arrived. ? CanaKit Raspberry Pi 3 B+ (B Plus) Complete... ? ? ? Has anyone got a list of the Must Do¡¯s, and the Must NOT do¡¯s ? ? I currently run :- ? Prodigy Advance 2 (MRC) , Windows 7,? JMRI 4.12+Rb6a9bb1, Java 1.8.0_181 (en_GB). ? WiThrottle on iPad¡¯s (2), Engine Driver on old phones (2) ? All with no problems and I have a basic understanding of my system. ? The Raspberry route is an unknown venture¡¡¡ ? Ken Bates in Essex, UK ? ?
|
Locked
LCC Block Signals Via JMRI/Raspberry PI 3 B+
I just purchased my first Raspberry pi 3 B+. I am planning to use it to control block signals with a rr-cirkits LCC buffer, power point, BOD 8, LCC signal tower, and CT coils. I have a micro SD card with NOOBS preloaded(basic RPI). Should I still use that program to get started on the initialization of the Raspberry PI/JMRI? What proper steps should I take for a successful installation and operation?
|
Hi, ? Well I ordered it, and now it has arrived. ? CanaKit Raspberry Pi 3 B+ (B Plus) Complete... ? ? ? Has anyone got a list of the Must Do¡¯s, and the Must NOT do¡¯s ? ? I currently run :- ? Prodigy Advance 2 (MRC) , Windows 7,? JMRI 4.12+Rb6a9bb1, Java 1.8.0_181 (en_GB). ? WiThrottle on iPad¡¯s (2), Engine Driver on old phones (2) ? All with no problems and I have a basic understanding of my system. ? The Raspberry route is an unknown venture¡¡¡ ? Ken Bates in Essex, UK ? ?
|
Tony, I would think that a PR4 or PR3 would be the way to go using a dedicated program track.? I ?am hoping that my issues are due to a defective PR4 that Digitrax will hopefully fix.? A friend has a PR3 and we were able to use that with JMRI to program a number of sound decoders from a Tsunami 1 on an Athearn Genesis up to the newest ESU LokSound Full Throttle decoder on a Scale Trains loco.? ? John ? Sent from for Windows 10 ?
toggle quoted message
Show quoted text
From: ADSent: Wednesday, September 12, 2018 10:34 AM To: [email protected]Subject: Re: [jmriusers] PR4 Issues ? I now have sound engines that jmri/digitrax cant program. If i want to buy something to program the decoders can someone who understands everything thats been said so far on the issue give a conclusion as exactly what i should buy with exactly what power supply for it. Tony Thanks for your response guys. ? I will be returning the unit to Digitrax later today to have them take a look at it. ? John ? Sent from for Windows 10 ? ? The PR3 use to come with a PS12 and then later a PS14. The generally accepted power need for the PR3 is at a minimum 14 volts but the sweet spot is 16 to 18 volts. Mine is running with 16 and I can program anything. Now I also have a PT100 in line to help with the sound decoders.? John,?
i also use a PR4 on a dedicated programming track. ?I found I could read all the regular loco decoders but not the sound decoders. ?Reading thru some of the posts a common issue seemed to be the stock power supply that comes from Digitrax. ?It outputs 15 volts but only in the milliamp range. ?I hooked up my RRAMP meter and discovered that the output to the rails was 12.7 volts with no load. ?The voltage dropped to 12.1 volts with a standard decoder, but it dropped to 11.3 with a QSI Sound decoder and 11.1 with a Soundtraxx decoder. ?I purchased a 5 amp power supply for the PR4 and now the voltage never drops below 12 volts regardless of what decoder in sitting on the rails. ?I still get an occasional 308 no response message when reading some CVs, which I attribute to perhaps those CVs are not used within that particular sound file, but I am able to read all my locos now with my PR4. ?
Incidentally, I asked this question of the Digitrax support team and they did not reply, so I just took a chance and bought the higher amperage supply. ?I¡¯ve been a Digitrax user since they first came out in the 90¡¯s and I am pretty frustrated that they did not reply and that I had to figure this out on my own so to speak (I did make some logically deductions from what I read here and drew my own conclusions)
i hope this helps.
George
|
I now have sound engines that jmri/digitrax cant program.
If i want to buy something to program the decoders can someone who understands everything thats been said so far on the issue give a conclusion as exactly what i should buy with exactly what power supply for it.
toggle quoted message
Show quoted text
On Sep 12, 2018, at 10:19 AM, John Umberger < jumberger88@...> wrote: Thanks for your response guys. ? I will be returning the unit to Digitrax later today to have them take a look at it. ? John ? Sent from for Windows 10 ? ? The PR3 use to come with a PS12 and then later a PS14. The generally accepted power need for the PR3 is at a minimum 14 volts but the sweet spot is 16 to 18 volts. Mine is running with 16 and I can program anything. Now I also have a PT100 in line to help with the sound decoders.? John,?
i also use a PR4 on a dedicated programming track. ?I found I could read all the regular loco decoders but not the sound decoders. ?Reading thru some of the posts a common issue seemed to be the stock power supply that comes from Digitrax. ?It outputs 15 volts but only in the milliamp range. ?I hooked up my RRAMP meter and discovered that the output to the rails was 12.7 volts with no load. ?The voltage dropped to 12.1 volts with a standard decoder, but it dropped to 11.3 with a QSI Sound decoder and 11.1 with a Soundtraxx decoder. ?I purchased a 5 amp power supply for the PR4 and now the voltage never drops below 12 volts regardless of what decoder in sitting on the rails. ?I still get an occasional 308 no response message when reading some CVs, which I attribute to perhaps those CVs are not used within that particular sound file, but I am able to read all my locos now with my PR4. ?
Incidentally, I asked this question of the Digitrax support team and they did not reply, so I just took a chance and bought the higher amperage supply. ?I¡¯ve been a Digitrax user since they first came out in the 90¡¯s and I am pretty frustrated that they did not reply and that I had to figure this out on my own so to speak (I did make some logically deductions from what I read here and drew my own conclusions)
i hope this helps.
George
|
Thanks for your response guys. ? I will be returning the unit to Digitrax later today to have them take a look at it. ? John ? Sent from for Windows 10 ?
toggle quoted message
Show quoted text
From: David KlemmSent: Tuesday, September 11, 2018 10:45 PM To: [email protected]Subject: Re: [jmriusers] PR4 Issues ? The PR3 use to come with a PS12 and then later a PS14. The generally accepted power need for the PR3 is at a minimum 14 volts but the sweet spot is 16 to 18 volts. Mine is running with 16 and I can program anything. Now I also have a PT100 in line to help with the sound decoders.? John,?
i also use a PR4 on a dedicated programming track. ?I found I could read all the regular loco decoders but not the sound decoders. ?Reading thru some of the posts a common issue seemed to be the stock power supply that comes from Digitrax. ?It outputs 15 volts but only in the milliamp range. ?I hooked up my RRAMP meter and discovered that the output to the rails was 12.7 volts with no load. ?The voltage dropped to 12.1 volts with a standard decoder, but it dropped to 11.3 with a QSI Sound decoder and 11.1 with a Soundtraxx decoder. ?I purchased a 5 amp power supply for the PR4 and now the voltage never drops below 12 volts regardless of what decoder in sitting on the rails. ?I still get an occasional 308 no response message when reading some CVs, which I attribute to perhaps those CVs are not used within that particular sound file, but I am able to read all my locos now with my PR4. ?
Incidentally, I asked this question of the Digitrax support team and they did not reply, so I just took a chance and bought the higher amperage supply. ?I¡¯ve been a Digitrax user since they first came out in the 90¡¯s and I am pretty frustrated that they did not reply and that I had to figure this out on my own so to speak (I did make some logically deductions from what I read here and drew my own conclusions)
i hope this helps.
George
|
Thanks Steve !! I will be on my way tp UPS shortly to send the unit back to Digitrax.? I will also check the PS14. ? Thanks again, John ? Sent from for Windows 10 ?
toggle quoted message
Show quoted text
From: BreezlysSent: Wednesday, September 12, 2018 10:03 AM To: [email protected]Subject: Re: [jmriusers] PR4 Issues ? I have both a PR3 and a PR4.? With the PR3 I use an 18VDC regulated power supply, and it will program anything (including the often hard-to-program sound decoders).
I've used only the included PS14 with my PR4, and not with as many brands/models of decoders as I've done with the PR3, but it hasn't failed to read a decoder yet.? It's also MUCH faster than the PR3, especially when reading TCS WOW decoders.
If your PR4 is having issues reading decoders, it may well need that return trip to Digitrax.? You may also want to check the PS14 to be sure it's operating up to spec.
HTH,
Steve
"Breezlys"? ?
|
I have both a PR3 and a PR4.? With the PR3 I use an 18VDC regulated power supply, and it will program anything (including the often hard-to-program sound decoders).
I've used only the included PS14 with my PR4, and not with as many brands/models of decoders as I've done with the PR3, but it hasn't failed to read a decoder yet.? It's also MUCH faster than the PR3, especially when reading TCS WOW decoders.
If your PR4 is having issues reading decoders, it may well need that return trip to Digitrax.? You may also want to check the PS14 to be sure it's operating up to spec.
HTH,
Steve
"Breezlys"? ?
|
Locked
Re: NCE usb interface not comunicating
On 12 Sep 2018, at 1:14 PM, Ken Cameron < kcameron@...> wrote: Just to add, from the log, you are talking with the NCE-USB. The traffic
beyond that going to the command station is what is not replying.
Correct.
As said, baud rate is frequently the issue.
Not if you are seeing the V7.3.x response in the log. That indicates the correct baud rate at both ends. But trying other connection
cables for the cab bus may be another issue. Check the little fingers in
each female connector to make sure all are straight and not bent and
crossing.
The appearance of"NCE EPROM revision = x.x.x" in the JMRI system console shows that the USB connection is working, the baud rate is correct and the NCE-USB is receiving power from the NCE cab bus via pins 2 & 5 of the cables/connectors between the USB and the Power Cab.
The next step is to check what happens to the Cab Bus LED on the NCE USB if you attempt to program/use a JMRI throttle, etc.. Both the LEDs on the NCE USB should normally be off, flashing briefly when you attempt an operation. If the Cab Bus light comes on and sticks on, you have a communication failure between the NCE USB and the Power Cab. There are several possible causes for this:
0) You have an extra throttle connected and set to Cab Address 3.
1) There is an incomplete circuit on pins 3 & 4 of the cables/connectors between the USB and the Power Cab. This could be a fault wire, plug attachment or a bent contact wire on one of the four sockets between the two. If you have a spare cable try swapping. Examine the contact finger wires on all four sockets. Try plugging the USB into a different socket (rear or front).
2) There is a communication lockup due to one or other device having a slightly incorrect RS422 driver chip. Your PCP needs some resistors fitted to fix this. Check your PCP against the information on this site and make sure they are fitted. <>
3) Your NCE USB, Power Cab or PCP has a hardware fault - this is extremely unlikely. If you change the baud rate on the jumpers (it isn't pin one, but
changes by making other selections), you also have to change it in the JMRI
connection preferences.
I would suggest trying 19,200 and put all the jumpers on the NCE-USB. This
is another valid combination. I would very?strongly recommend against changing either the baud rate in JMRI or the NCE USB settings at this stage. Doing so will not solve your problem and will introduce other possible causes to the list above.
While the above configuration is optimum for a a V7 NCE USB and a V1.65B Power Cab, there is more setup involved (choice of cab bus address) and a potential problem with V1.65 or older Power Cab firmware.
Dave in Australia
|
I don't have Windows 10, but in older Windows versions it was possible to manually change the COM port allocated to a USB-Serial device under the Properties->Advanced tab of the device.
I don't know you can still do so with Win 10. You'd also need to check that the change persisted across restarts and unplug/replug. I also say warnings that a restart may be needed to see any change correctly. (Maybe an F5 refresh could work in Device Manager as well?)
Someone with Win 10 may be able to confirm/deny.
The New England Convention 2018
toggle quoted message
Show quoted text
On 12 Sep 2018, at 8:03 AM, Bob Potter < rnp@...> wrote: Peter, as I had previously mentioned:
"I had a lot of trouble using Com 5 on my Win 10 desktop. I had to delete the port entirely and when device manager then selected Com 7, DP startup problems went away. Don't do this unless all other options produce negative results- it is difficult to get a deleted port reinstalled. I don't know for sure but Win 10 may use the port for other options in the OS. You could try with any other devices you may be running internal or external like a disk drive or plug & play memory, etc. Take a look at System devices as well as Ports in Device Manager to see possible conflicts or duplications.".
I have since discussed this errant Com5 problem in Win10 with others (not model RR enthusiasts) but software engineers from my previous life. To sum up; Com5 can indeed be flakey in some instances of the Win10.
No one has spent enough time on the problem to determine why or when. I like Com7.
|
Locked
Re: NCE usb interface not comunicating
Just to add, from the log, you are talking with the NCE-USB. The traffic
beyond that going to the command station is what is not replying.
As said, baud rate is frequently the issue. But trying other connection
cables for the cab bus may be another issue. Check the little fingers in
each female connector to make sure all are straight and not bent and
crossing. If you change the baud rate on the jumpers (it isn't pin one, but
changes by making other selections), you also have to change it in the JMRI
connection preferences.
I would suggest trying 19,200 and put all the jumpers on the NCE-USB. This
is another valid combination.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
|
The PR3 use to come with a PS12 and then later a PS14. The generally accepted power need for the PR3 is at a minimum 14 volts but the sweet spot is 16 to 18 volts. Mine is running with 16 and I can program anything. Now I also have
a PT100 in line to help with the sound decoders.?
toggle quoted message
Show quoted text
John,?
i also use a PR4 on a dedicated programming track. ?I found I could read all the regular loco decoders but not the sound decoders. ?Reading thru some of the posts a common issue seemed to be the stock power supply that comes from Digitrax. ?It outputs 15 volts
but only in the milliamp range. ?I hooked up my RRAMP meter and discovered that the output to the rails was 12.7 volts with no load. ?The voltage dropped to 12.1 volts with a standard decoder, but it dropped to 11.3 with a QSI Sound decoder and 11.1 with a
Soundtraxx decoder. ?I purchased a 5 amp power supply for the PR4 and now the voltage never drops below 12 volts regardless of what decoder in sitting on the rails. ?I still get an occasional 308 no response message when reading some CVs, which I attribute
to perhaps those CVs are not used within that particular sound file, but I am able to read all my locos now with my PR4. ?
Incidentally, I asked this question of the Digitrax support team and they did not reply, so I just took a chance and bought the higher amperage supply. ?I¡¯ve been a Digitrax user since they first came out in the 90¡¯s and I am pretty frustrated that they did
not reply and that I had to figure this out on my own so to speak (I did make some logically deductions from what I read here and drew my own conclusions)
i hope this helps.
George
|
John,?
i also use a PR4 on a dedicated programming track. ?I found I could read all the regular loco decoders but not the sound decoders. ?Reading thru some of the posts a common issue seemed to be the stock power supply that comes from Digitrax. ?It outputs 15 volts but only in the milliamp range. ?I hooked up my RRAMP meter and discovered that the output to the rails was 12.7 volts with no load. ?The voltage dropped to 12.1 volts with a standard decoder, but it dropped to 11.3 with a QSI Sound decoder and 11.1 with a Soundtraxx decoder. ?I purchased a 5 amp power supply for the PR4 and now the voltage never drops below 12 volts regardless of what decoder in sitting on the rails. ?I still get an occasional 308 no response message when reading some CVs, which I attribute to perhaps those CVs are not used within that particular sound file, but I am able to read all my locos now with my PR4. ?
Incidentally, I asked this question of the Digitrax support team and they did not reply, so I just took a chance and bought the higher amperage supply. ?I¡¯ve been a Digitrax user since they first came out in the 90¡¯s and I am pretty frustrated that they did not reply and that I had to figure this out on my own so to speak (I did make some logically deductions from what I read here and drew my own conclusions)
i hope this helps.
George
|
Hi Jay, Thanks so much for the response.? Good to know that I am not alone regarding this problem. I am operating on Win 10 myself. ? Let me know how you make out and I will advise the same. ? Thanks, John ? ? ? Sent from for Windows 10 ?
toggle quoted message
Show quoted text
From: JaySent: Tuesday, September 11, 2018 8:32 PM To: [email protected]Subject: Re: [jmriusers] PR4 Issues ? Hi John, I also had the exact same issue as you.
Mine is at Digitrax right now.
They waffled for 3 weeks before they would look at it.
I tried it on Win 10 & Mac OS X.
Neither worked.
I used a DCC++ Command Station on both & it worked flawlessly.
Jay
|
Locked
Re: Help needed with Team Digital SRC162
Steve,
My best guess when reading the SRC162 document is that a "group" is simply a pair of sequential outputs which associated with a single address, with one output taking the state from a LocoNet message, and the other output taking the opposite state from that same LocoNet message. I am guessing that outputs 1&2 may be grouped, as may outputs 3&4, and outputs 5&6 may be grouped, ... and outputs 15&16 may be grouped.
It appears that Team Digital has created a "smart programming" mechaniasm (I'll call this "smart programming mode 1", and it is shown in the top part of the table at the top of page 4) to "bulk-assign" the addresses of the eight "output groups" and eight associated "input groups" using a single "switch" command. In this case, the addresses are sequentially increasing from the single "switch" command. Since you don't want sequential output addresses (you want randomly-assigned addresses) values, you CANNOT use "smart programming" to assign the output addresses.
Instead you need to individually program CV values. JMRI can help you do this.
"Simply" program outputs 1&2 to the same address and the same command type, with the Output 2 using the opposite sense of output 1. Then program inputs 1&2 to that very same address and command type, with input 1 configured to send a "throw" command and input 2 configured to send a "close" command.
In this way, SRC162 input 1 asks the command station to "throw" Switch X, and SRC162 outputs 1&2 see the LocoNet request to "throw" Switch X and sets output 1 appropriately for "thrown" and sets output 2 to the opposite value.
Repeat this for each of eight pairs ("groups") of inputs and outputs.
(I'll send an XML "off list" that might do the job.)
Regards,
Billybob
|
Locked
Re: NCE usb interface not comunicating
On Tue, Sep 11, 2018 at 05:04 PM, <62fordjim@...> wrote:
Hi
check the dip switches on your USB board.. It is possible? the speed doesn't match that set up in JMRI ( You have JMRI set to 9600). Ideally 19200 is better but both ends need to match whatever your speed setting John
|
Hi John,
I also had the exact same issue as you.
Mine is at Digitrax right now.
They waffled for 3 weeks before they would look at it.
I tried it on Win 10 & Mac OS X.
Neither worked.
I used a DCC++ Command Station on both & it worked flawlessly.
Jay
|
Locked
Re: Help needed with Team Digital SRC162
See for some information on problems with JMRI being able to properly read from some Team Digitial devices, including the SRC162. It is possible that the ability to READ the SRC162 is causing problems in figuring out the correct programming.
The workaround presented there may be of help to you - this workaround allows JMRI to read a LocoNet-connected SRC162 CVs. I've excerpted this workaround, below.
"As a workaround, change your connection configuration to reflect that "transponding present:" is set to "Yes". This will allow the "Programming on the Main" LocoNet messages to be processed during CV reads.
You would probably want to restore the setting to "No" after configuring your SRC162 devices."
Regards,
Billybob
|
ahouse3761
Ken Cameron
Glikestrains