Keyboard Shortcuts
Likes
- Jmriusers
- Messages
Search
Locked
Re: Using NCE Powercab and Megapoints
Nigel, just had a look and a fiddle and the servos are now working correctly. Thanks for your advice
|
Locked
Re: programing on MRC system error message programer in use
Carrs,
The other comment I'd make is that baud rate setting issues in 4.16 could be the problem you saw there. Using 4.17.4 would be a good choice for trying 'current' JMRI developments. It fixed the baud rate issues that plagued many users of 4.16. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.org www.syracusemodelrr.org |
Locked
Re: VSD Notching Question
#vsdecoder
Conrad, Stephen,
Am 26.10.2019 um 16:46 schrieb conrad: Stephen, you stated that "What bothers me much more is to have engine start-up and shutdown sounds play every time the train is started and stopped. Locomotives are not routinely shut down just because the train has stopped. If did this, I would add the Stop position to the throttle and make use of that."Right, the sound shut down should not happen just because the train has stopped. I updated the engine auto-start functionality of VSDecoder in 2018 (see JMRI Test Release 4.11.3, published on February 15, 2018). Stephen, if you are using JMRI 4.11.3 or a newer version there must be another reason for this behavior. And I'm interested in clearing that up. All engine types (steam, steam1 and diesel3) should work as follows: * by default, the engine sound is started by clicking the "Engine Start" button, or stopped by clicking the "Engine Off" button * VSD allows to define a throttle function key to start or stop the engine sound * VSD allows to auto-start the engine sound after adding a VSDecoder (checkbox in VSDecoder Preferences, valid for all newly added VSDecoders) * VSD allows to auto-start an individual VSDecoder by declaring "<auto-start>yes</auto-start>" in the config.xml file Klaus |
Locked
Re: Signaling & detection on trackage containing magnetic ballast
Being a cheapskate, ballast that came anywhere near what I wanted happened to be the local lake beach sand, sifted, but as I discovered full of metal particles. My solution at the time was to run the proposed ballast over a very large speaker magnet numerous times, this resulted in a material loss of about 60% ( lightened the colour to ) of metal particles.? I still however made sure ballast did not touch underside of rails and of course was glued in place.? I did have some less than zero readings but that all disappeared once white glue was totally dry. I have had NO issues regarding any false readings even though they are in a harsh environment. ( Mobile train show display )? PS? I did go over track with magnet after dry to be sure and my detectors are set at 20k ohm operation. John.
|
Locked
Re: programing on MRC system error message programer in use
¿ªÔÆÌåÓýcarrs, I have taken jmri? completely off my computer and went back and installed version 4.12.1 and every thing works like it should I can program, speed match etc. I then tried to reload 4.16 and I then get the message that programmer in use so I have reset to 4.12 and will wait until I see 4.17 is set as a final release in the mean time I am up and running. Thanks for all the help Simply waiting for the 4.18 is certainly not going to fix your problem. As far as I know, no one else has reported the same problem so there's nothing we as developers can do until we have someone who is both encountering the problem and is willing to work with us. Dave in Australia |
Locked
Re: Signaling & detection on trackage containing magnetic ballast
I've found enough motors and speakers 'clouded' by magnetic particles to say
'avoid'! On the cone of a speaker, it kills the sounds by adding weight to the moving parts. For motors, it tends to find a way to sneak in and wear something. On the outside it may affect the magnetic field. I'd say the possible issues make it something to use away from the tracks. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.org www.syracusemodelrr.org |
Locked
Re: Signaling & detection on trackage containing magnetic ballast
Stick the two probes of an ohm meter into the jar.? Compress the ballast.? If you get any reading other than infinite I would discard the idea of using that ballast.? As far as I know, only ferrous materials are attracted to magnets.? Ferrous materials can conduct electricity and give false detections.? Personally, I wouldn't touch it!
Dave... |
Locked
Re: programing on MRC system error message programer in use
I have taken jmri? completely off my computer and went back and installed version 4.12.1 and every thing works like it should I can program, speed match etc. I then tried to reload 4.16 and I then get the message that programmer in use so I have reset to 4.12 and will wait until I see 4.17 is set as a final release in the mean time I am up and running. Thanks for all the help
|
Locked
Re: MIld panic: all ID tags appear to be gone
Paul, |
Locked
Re: Using NCE Powercab and Megapoints
Hi Nigel, thanks for the reply. I have also posted in the NCEforum, just trying to cover all bases as I'm so new to this. Having reread the manual I think you are correct about simple mode. As I am not going to use a mimic board I had assumed that I was connecting direct to the servo controller as in the note. NOTE: If connecting directly to a Servo Controller you must set slave mode on the Servo Controller. I will have a look at things again tomorrow and try your suggestion. Many thanks
|
¿ªÔÆÌåÓýDave ? I am trying to use the best approach to creating signalling and was steered to using masts instead of heads on MERG and this is where I started. I was provided the methodology of creating a software node (Node 99) as part of JMRI in the Turnouts table. I used this link to set up the aspects of each signal in CBUS and tested this link to make sure it worked. I then created the masts and they worked back to the signals OK and matched the masts that I placed on the panel. We were told that Signal Masts were better than Signal Heads. I was expecting to receive advice on how to then add the required logic which we were informed would be an easy step, but this thread dried up about 2 weeks ago. What I am trying to do must be very common to UK modellers using JMRI as I am trying to simulate 1950¡¯s/60¡¯s colour light signalling which followed steam rules. Junctions had individual signals (no feathers) for each route and signal heads replaced semaphore signals. An example being the bracket junction signals available commercially. I wonder if I should explore other UK systems (other than BR2003) to see if I can use an alternative. My problem is that I have a lot of work to do to achieve a result and I need to make sure whatever the approach I use, I can understand fully and be able to use the knowledge I learn to be able to plan and handle any issue(s) I come across. ? I really appreciate what you have done for me on here but I have to be honest about my own short-comings. One other thing I need to do is to sort out the blocks. I have used the Check function and am horrified. ? Very best wishes and thanks. Peter ? ? From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: 26 October 2019 20:28 To: [email protected] Subject: Re: [jmriusers] Setting up signals in JMRI to MERG CBUS ? Peter, ? The signal heads are on the panel for debugging purposes. ? As the SD2 virtual mast changes, the SD7-SD9 heads should also change. ?If they change on the panel, but the physical heads on the layout do not change, then there is most likely an issue external to JMRI. ? The aspect for SD2 is calculated by signal mast logic using the turnout positions and occupancy states for the routes to the 3 destination masts. ?If the layout is not reporting those states correctly, SD2 will not display a valid aspect which then affects the signal head results as created by gantry.py. ? I skipped over a question at the beginning of this process: ?Do you plan to use JMRI signal mast logic (SML) or create custom signal mast logic using Logix? ? Dave Sand ? ? ? ----- Original message ----- From: "peter.s.drury via Groups.Io" <peter.s.drury@...> Subject: Re: [jmriusers] Setting up signals in JMRI to MERG CBUS Date: Saturday, October 26, 2019 1:33 PM ? Hi Dave I carried out the steps in the following order. Removed the two new .py scripts from the startup menu. Re-started JMRI. Loaded your new panel file. Ran the gantry.py script. Tested the setup. ? The Signal heads SD7-SD9 are still present on the panel. I have a very real problem because my physical signals (SD7 ¨C SD9) are not changing and therefore I do not have the functionality that I had when all signals heads were on separate masts. I have little confidence that I can use this methodology because it relies on knowledge of programming and I really do not understand it well enough. I thought I could select each junction signal based on the feedback from the turnouts giving the position of each turnout (Closed or Thrown) which the MERG system provides to the Turnout Table. Each of the Junction Signals would be paired. The logic would establish which pair to compare and set the appropriate aspect. I thought that this could be done li logix. I m sorry but my skills do not meet the requirements to handle scripts confidently. Many thanks for your help but I feel I am letting you down. Best wishes Peter ? ? From: [email protected] <[email protected]> On Behalf Of Dave Sand ? Peter, ? The startup sequence in the profile that I uploaded has 3 steps.
? Panel specific initialization is handled by RTXINITIALIZER. ? ? RTXINITIALIZER1T? Route 1C Init?? ?? Antecedent: R1? ??? [x]? R1? IF? RTXINITIALIZER type??? ???????????? THEN?? ?????????????? On Change To True, Run Script from file, preference:scripts/gantry.py.?? ?????????????? On Change To True, Run Script from file, preference:scripts/TurnoutSimulator.py.?? ?????????????? On Change To True, Set Sensor, "Reset" to Active?? ? This is the first Logix that runs after the panel xml file has been fully loaded and is ready to go. ?I load the gantry.py script here rather than in the profile start up actions. ?This guarantees that there are no startup sequencing issues. ?If you never run in simulation mode, the startup.py and TurnoutSimulator.py scripts are not needed. ?There are also two Routes that would not be needed. ? When I created the virtual mast (SD2 South Gantry), I should have selected 3 Aspect Signal. ?It still has the flashing caution, but it only shows when you manually change the aspect. ?During normal operation using signal mast logic the flashing caution will not occur. ? I have uploaded an updated panel xml file. ?SD2 South Gantry is now a 3 Aspect Signal and the old SD7-SD9 masts have been removed. ? ? Dave Sand ? ? ? ----- Original message ----- From: "peter.s.drury via Groups.Io" <peter.s.drury@...> Subject: Re: [jmriusers] Setting up signals in JMRI to MERG CBUS Date: Saturday, October 26, 2019 6:50 AM ? Good morning Dave Sorry for the delay in replying, didn't get back until 0200 Friday. I have run through your modified panel. I modified the original startup files as can be seen here. I hope this is correct. With the above changes I tried the changes to the panel. Observations: SD2 and SD3 both have included unwanted signal aspects (Flashing Red & Yellow, Double Yellow) . The latter becomes apparent when SD3 is yellow - SD 2 becomes Double Yellow. I could not find a way of restricting these unwanted aspects The indivual heads of the Mast SD2 do not display. SD7-9 are the heads that communicate to the Software Node via the Turnout Table. For this reason to hardware gantry signals do not update the physial signals. Signalling follows the routing and, depending on the destination mast, displays the correct SD2 aspect. I could not find an entry for virtual Signal SD2 in the tables. I suspect I have an error in my loading of the startup files. Thanks again for your support. ? ? ? ? ? |
Locked
Re: Flash rate for signals
Thanks Bob.? I'll try and get this downloaded in the next day or two. Cheers, Dennis Drury Dayton, NV The miracle is this: the more we share the more we have. Leonard Nimoy On Sat, Oct 26, 2019 at 11:36 AM Bob Jacobsen <rgj1927@...> wrote: This is now in the development builds (I.e. ) and will be in JMRI 4.17.5 (which is due out sometime soon) |
Locked
VSD Prototypical Diesel Engine Operation?
#vsdecoder
My previous posts on notching got me interested in prototypical diesel/electric operation.? I knew that Digitrax's sound decoders have three notch modes: auto, semi-auto and manual.
But now I see that ESU also has manual notching and more.? So is it possible to do something similar with VSD?? Note that Klaus' steam file has a coast function.? Here is ESU's system, taken from their ALCO 6-539T engine: "Recorded from a ALCO S-2 File also contains an "Isolation Switch" Mode on F15 when Standing Still. Pressing F15 while not moving will lower the prime mover and lock the motor. F15 must be turned off to begin moving. Another Mode is "Reverser In Center Position". When pressing F24 while stopped, the motor will lock so you can throttle through the notches like the prototype in neutral. F24 must be turned off to begin moving. This project has "Run 8" mode. When turning on F26 with F28 off, the prime mover goes to run 8. Turning off F26 returns the prime mover sounds back to normal mode. This project has "Coast" mode. When turning on F27 with F28 off, the prime mover goes to idle for coasting purposes. Turning off F27 returns the prime mover sounds back to normal mode. You can still use F26 and F27 for manual nothing. You have to keep both F26 and F27 off before pressing F28 to turn on manual notching. Once F28 is on, you can use F26 to notch up and F27 to notch down. F26, F27, and F28 must be turned off to return to normal mode." Conrad |
Locked
Re: Using NCE Powercab and Megapoints
¿ªÔÆÌåÓýThis sounds like a NCE to Megapoints issue, not really JMRI.?? So, you ought to take it up with those companies, or the support forums for those items. ? The setup should work,? I¡¯m working on a layout which uses NCE, and has a Megapoints DCC module, connected to Megapoints servo controllers.? So, there is nothing
fundamentally incompatible about them.? ?Reading the DCC Module manual, unless you have a Megapoints Multipanel Process, you should have the DCC Module in ¡°Simple¡± mode, not ¡°Gateway¡±? (and if just trying to prove it all works, start with ¡°Simple¡± and move
on to adding the Multipanel Processor and ¡°Gateway¡± mode later). ?? Once you have the NCE system sending turnout commands to the Megapoints DCC module, which are then acted upon by the Servo Controllers,? then start to look at JMRI integration. ? ? -????????? Nigel
? From: [email protected] [mailto:[email protected]]
On Behalf Of Mick
Sent: 26 October 2019 14:20 To: [email protected] Subject: [jmriusers] Using NCE Powercab and Megapoints ? Hi all, brand new to JMRI and DCC so trying to get my head around things. I have an NCE powecab with usb module setup on a test track and have that working correctly, also using Megapoints DCC module and servo controller. I have manage
to control my loco from the on screen throttle but cannot seem to find a way to connect to the megapoints boards. I have the dcc module set to gateway mode and the servo controller as slave. Power to the dcc module is taken from the main control board. |
Peter, The signal heads are on the panel for debugging purposes. As the SD2 virtual mast changes, the SD7-SD9 heads should also change. ?If they change on the panel, but the physical heads on the layout do not change, then there is most likely an issue external to JMRI. The aspect for SD2 is calculated by signal mast logic using the turnout positions and occupancy states for the routes to the 3 destination masts. ?If the layout is not reporting those states correctly, SD2 will not display a valid aspect which then affects the signal head results as created by gantry.py. I skipped over a question at the beginning of this process: ?Do you plan to use JMRI signal mast logic (SML) or create custom signal mast logic using Logix? Dave Sand ----- Original message ----- From: "peter.s.drury via Groups.Io" <peter.s.drury@...> Subject: Re: [jmriusers] Setting up signals in JMRI to MERG CBUS Date: Saturday, October 26, 2019 1:33 PM Hi Dave I carried out the steps in the following order. Removed the two new .py scripts from the startup menu. Re-started JMRI. Loaded your new panel file. Ran the gantry.py script. Tested the setup. ? The Signal heads SD7-SD9 are still present on the panel. I have a very real problem because my physical signals (SD7 ¨C SD9) are not changing and therefore I do not have the functionality that I had when all signals heads were on separate masts. I have little confidence that I can use this methodology because it relies on knowledge of programming and I really do not understand it well enough. I thought I could select each junction signal based on the feedback from the turnouts giving the position of each turnout (Closed or Thrown) which the MERG system provides to the Turnout Table. Each of the Junction Signals would be paired. The logic would establish which pair to compare and set the appropriate aspect. I thought that this could be done li logix. I m sorry but my skills do not meet the requirements to handle scripts confidently. Many thanks for your help but I feel I am letting you down. Best wishes Peter ? From: [email protected] <[email protected]> On Behalf Of Dave Sand ? Peter, ? The startup sequence in the profile that I uploaded has 3 steps.
? Panel specific initialization is handled by RTXINITIALIZER. ? ? RTXINITIALIZER1T? Route 1C Init?? ?? Antecedent: R1? ??? [x]? R1? IF? RTXINITIALIZER type??? ???????????? THEN?? ?????????????? On Change To True, Run Script from file, preference:scripts/gantry.py.?? ?????????????? On Change To True, Run Script from file, preference:scripts/TurnoutSimulator.py.?? ?????????????? On Change To True, Set Sensor, "Reset" to Active?? ? This is the first Logix that runs after the panel xml file has been fully loaded and is ready to go. ?I load the gantry.py script here rather than in the profile start up actions. ?This guarantees that there are no startup sequencing issues. ?If you never run in simulation mode, the startup.py and TurnoutSimulator.py scripts are not needed. ?There are also two Routes that would not be needed. ? When I created the virtual mast (SD2 South Gantry), I should have selected 3 Aspect Signal. ?It still has the flashing caution, but it only shows when you manually change the aspect. ?During normal operation using signal mast logic the flashing caution will not occur. ? I have uploaded an updated panel xml file. ?SD2 South Gantry is now a 3 Aspect Signal and the old SD7-SD9 masts have been removed. ? ? Dave Sand ? ? ? ----- Original message ----- From: "peter.s.drury via Groups.Io" <peter.s.drury@...> Subject: Re: [jmriusers] Setting up signals in JMRI to MERG CBUS Date: Saturday, October 26, 2019 6:50 AM ? Good morning Dave Sorry for the delay in replying, didn't get back until 0200 Friday. I have run through your modified panel. I modified the original startup files as can be seen here. I hope this is correct. With the above changes I tried the changes to the panel. Observations: SD2 and SD3 both have included unwanted signal aspects (Flashing Red & Yellow, Double Yellow) . The latter becomes apparent when SD3 is yellow - SD 2 becomes Double Yellow. I could not find a way of restricting these unwanted aspects The indivual heads of the Mast SD2 do not display. SD7-9 are the heads that communicate to the Software Node via the Turnout Table. For this reason to hardware gantry signals do not update the physial signals. Signalling follows the routing and, depending on the destination mast, displays the correct SD2 aspect. I could not find an entry for virtual Signal SD2 in the tables. I suspect I have an error in my loading of the startup files. Thanks again for your support. ? ? ? |
Locked
Re: Flash rate for signals
This is now in the development builds (I.e. ) and will be in JMRI 4.17.5 (which is due out sometime soon)
Running the ¡°SetSignalFlashRate.py¡± sample script will lengthen the default 750ms on, 750ms off to 1000 on/off, i.e. about 1/3 slower. You can make your own modified version for whatever other rate desired. Bob -- Bob Jacobsen rgj1927@... |
¿ªÔÆÌåÓýHi Dave I carried out the steps in the following order. Removed the two new .py scripts from the startup menu. Re-started JMRI. Loaded your new panel file. Ran the gantry.py script. Tested the setup. ? The Signal heads SD7-SD9 are still present on the panel. I have a very real problem because my physical signals (SD7 ¨C SD9) are not changing and therefore I do not have the functionality that I had when all signals heads were on separate masts. I have little confidence that I can use this methodology because it relies on knowledge of programming and I really do not understand it well enough. I thought I could select each junction signal based on the feedback from the turnouts giving the position of each turnout (Closed or Thrown) which the MERG system provides to the Turnout Table. Each of the Junction Signals would be paired. The logic would establish which pair to compare and set the appropriate aspect. I thought that this could be done li logix. I m sorry but my skills do not meet the requirements to handle scripts confidently. Many thanks for your help but I feel I am letting you down. Best wishes Peter
? From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: 26 October 2019 16:10 To: [email protected] Subject: Re: [jmriusers] Setting up signals in JMRI to MERG CBUS ? Peter, ? The startup sequence in the profile that I uploaded has 3 steps.
? Panel specific initialization is handled by RTXINITIALIZER. ? ? RTXINITIALIZER1T? Route 1C Init?? ?? Antecedent: R1? ??? [x]? R1? IF? RTXINITIALIZER type??? ???????????? THEN?? ?????????????? On Change To True, Run Script from file, preference:scripts/gantry.py.?? ?????????????? On Change To True, Run Script from file, preference:scripts/TurnoutSimulator.py.?? ?????????????? On Change To True, Set Sensor, "Reset" to Active?? ? This is the first Logix that runs after the panel xml file has been fully loaded and is ready to go. ?I load the gantry.py script here rather than in the profile start up actions. ?This guarantees that there are no startup sequencing issues. ?If you never run in simulation mode, the startup.py and TurnoutSimulator.py scripts are not needed. ?There are also two Routes that would not be needed. ? When I created the virtual mast (SD2 South Gantry), I should have selected 3 Aspect Signal. ?It still has the flashing caution, but it only shows when you manually change the aspect. ?During normal operation using signal mast logic the flashing caution will not occur. ? I have uploaded an updated panel xml file. ?SD2 South Gantry is now a 3 Aspect Signal and the old SD7-SD9 masts have been removed. ? ? Dave Sand ? ? ? ----- Original message ----- From: "peter.s.drury via Groups.Io" <peter.s.drury@...> Subject: Re: [jmriusers] Setting up signals in JMRI to MERG CBUS Date: Saturday, October 26, 2019 6:50 AM ? Good morning Dave Sorry for the delay in replying, didn't get back until 0200 Friday. I have run through your modified panel. I modified the original startup files as can be seen here. I hope this is correct. With the above changes I tried the changes to the panel. Observations: SD2 and SD3 both have included unwanted signal aspects (Flashing Red & Yellow, Double Yellow) . The latter becomes apparent when SD3 is yellow - SD 2 becomes Double Yellow. I could not find a way of restricting these unwanted aspects The indivual heads of the Mast SD2 do not display. SD7-9 are the heads that communicate to the Software Node via the Turnout Table. For this reason to hardware gantry signals do not update the physial signals. Signalling follows the routing and, depending on the destination mast, displays the correct SD2 aspect. I could not find an entry for virtual Signal SD2 in the tables. I suspect I have an error in my loading of the startup files. Thanks again for your support. ? ? ? |
Locked
Re: Signaling & detection on trackage containing magnetic ballast
Jim: What happens when you spread some ballast and run a magnet over it resting a few mm above the tops of the rails? I ask because magnetic field strengths vary greatly and there will be some combination of distance and magnet strength that the ballast will not jump up to the magnet. Well designed products that use magnets, like speakers and motors, maximize the efficiency of their magnets by minimizing magnetic leakage which makes external fields smaller by design. So strong magnets don't necessarily mean high external fields. I would do some experimenting before assuming that there is a concern in practice.
But if there is a concern can you not find some ballast that is non-magnetic such as by mixing powdered pigment (art supplies or dry weathering product) with aggregate that is the right shape and size? Jan |
Locked
Windows 10 Firewall and Engine Driver App on Android
#windows10
#enginedriver
#firewall
Had a Google and unable to find how to set the Windows 10 Firewall rules for?Engine Driver App on Android?
So, this is what worked for me; Open settings (in Windows)
Click on Update & Security
Click on Windows Security
Click on Firewall & network protection
Click on Allow an app through firewall
Scroll down to panelpro.exe
Put a tick (check) in the box on the left of panelpro and put a tick in the box in the private column
Click OK
David ? |
Peter, The startup sequence in the profile that I uploaded has 3 steps.
Panel specific initialization is handled by RTXINITIALIZER. ? RTXINITIALIZER1T? Route 1C Init?? ?? Antecedent: R1? ??? [x]? R1? IF? RTXINITIALIZER type??? ???????????? THEN?? ?????????????? On Change To True, Run Script from file, preference:scripts/gantry.py.?? ?????????????? On Change To True, Run Script from file, preference:scripts/TurnoutSimulator.py.?? ?????????????? On Change To True, Set Sensor, "Reset" to Active?? This is the first Logix that runs after the panel xml file has been fully loaded and is ready to go. ?I load the gantry.py script here rather than in the profile start up actions. ?This guarantees that there are no startup sequencing issues. ?If you never run in simulation mode, the startup.py and TurnoutSimulator.py scripts are not needed. ?There are also two Routes that would not be needed. When I created the virtual mast (SD2 South Gantry), I should have selected 3 Aspect Signal. ?It still has the flashing caution, but it only shows when you manually change the aspect. ?During normal operation using signal mast logic the flashing caution will not occur. I have uploaded an updated panel xml file. ?SD2 South Gantry is now a 3 Aspect Signal and the old SD7-SD9 masts have been removed. Dave Sand ----- Original message ----- From: "peter.s.drury via Groups.Io" <peter.s.drury@...> Subject: Re: [jmriusers] Setting up signals in JMRI to MERG CBUS Date: Saturday, October 26, 2019 6:50 AM Good morning Dave Sorry for the delay in replying, didn't get back until 0200 Friday. I have run through your modified panel. I modified the original startup files as can be seen here. I hope this is correct. With the above changes I tried the changes to the panel. Observations: SD2 and SD3 both have included unwanted signal aspects (Flashing Red & Yellow, Double Yellow) . The latter becomes apparent when SD3 is yellow - SD 2 becomes Double Yellow. I could not find a way of restricting these unwanted aspects The indivual heads of the Mast SD2 do not display. SD7-9 are the heads that communicate to the Software Node via the Turnout Table. For this reason to hardware gantry signals do not update the physial signals. Signalling follows the routing and, depending on the destination mast, displays the correct SD2 aspect. I could not find an entry for virtual Signal SD2 in the tables. I suspect I have an error in my loading of the startup files. Thanks again for your support. |