开云体育

Warning - Connectivities for "Block Bonton TT Spur 1" in panels Bonton and Bondale are not compatable

SwissChris All Messages By This Member #161751 JMRI.4.14+Rd060e0b (Connected machine) JMRI 4.15.9 (Non Connected Machine) Windows 10 Professional (Both Machines) Physical Connections Digitrax PR 4 into DCS 50 (Loconet 1) used for sensors Digitrax DCS 52 USB (Loconet 2) Used for turnouts signals and any DCC controlled accessories (Fleischmann Turntable) Gaugemaster (MRC) Prodigy 2 for track power These connections are run as simulations on the definition PC. Physical connections on the connected PC with no error messages about the connection I use 1 PC to define the layout and another to run the layout with a networked drive being used to store the panels, Roster and Jython scripts. The above message appears whenever I load my panels onto my layout defining PC. It shows the message for all connections on my DCC powered Fleischmann Turntable. The turntable is able to be controlled from either panel on the connected machine. ? I have removed the turntable from both panels and redefined on both and the message still appears. Clicking on a turntable exit, on 1 panel does affect the turntable on the other panel. Clicking a turnout on 1 panel affects both panels. Signals show the same aspect on both panels. I only get this message in JMRI 4.15.9?which I am using on my non connected machine. The error message does not appear in JMRI 4.14 which I am using on my connected machine. Both machines run Win 10. I write the layout on the non connected machine and only change panels with the connected machine when I find an error, or to fine tune the panels. Panels are stored with a Date / Time number in the filename.e.g. Bondale 20190715 0855 and are kept for up to 1 month so I can back track if any errors show up. Why more than 1 panel? As time goes on, I'll be using Raspberry Pis to control the various areas of the layout with a master panel on the PC for overall control Any ideas please?
Dave Sand All Messages By This Member #161755 Chris, You have a subtle difference in the block assignments on the two panels which was uncovered by code changes since 4.14. If you upload the panel xml file and any custom components, we should be able to identify the source of the message. Dave Sand toggle quoted message Show quoted text On Jul 15, 2019, at 3:25 AM, SwissChris <chris@...> wrote: JMRI.4.14+Rd060e0b (Connected machine) JMRI 4.15.9 (Non Connected Machine) Windows 10 Professional (Both Machines) Physical Connections Digitrax PR 4 into DCS 50 (Loconet 1) used for sensors Digitrax DCS 52 USB (Loconet 2) Used for turnouts signals and any DCC controlled accessories (Fleischmann Turntable) Gaugemaster (MRC) Prodigy 2 for track power These connections are run as simulations on the definition PC. Physical connections on the connected PC with no error messages about the connection I use 1 PC to define the layout and another to run the layout with a networked drive being used to store the panels, Roster and Jython scripts. The above message appears whenever I load my panels onto my layout defining PC. It shows the message for all connections on my DCC powered Fleischmann Turntable. The turntable is able to be controlled from either panel on the connected machine. I have removed the turntable from both panels and redefined on both and the message still appears. Clicking on a turntable exit, on 1 panel does affect the turntable on the other panel. Clicking a turnout on 1 panel affects both panels. Signals show the same aspect on both panels. I only get this message in JMRI 4.15.9 which I am using on my non connected machine. The error message does not appear in JMRI 4.14 which I am using on my connected machine. Both machines run Win 10. I write the layout on the non connected machine and only change panels with the connected machine when I find an error, or to fine tune the panels. Panels are stored with a Date / Time number in the filename.e.g. Bondale 20190715 0855 and are kept for up to 1 month so I can back track if any errors show up. Why more than 1 panel? As time goes on, I'll be using Raspberry Pis to control the various areas of the layout with a master panel on the PC for overall control Any ideas please?
SwissChris All Messages By This Member #162811 Since I posted and uploaded the XML file, I've redrawn both the main, and the local panels pertaining to the turnatable.and the problem is still there. I've now upgraded to JMRI 4.16 on all machines and the error message now appears on all JMRI 4.16 on PCs both connected and unconnected Windows 10 Proffessional on PCs connected and unconnected XML files stored on a network drive accessable by all PCs Currently 1 connected PC, 1 unconnected tower and 1 unconnected laptop
Dave Sand All Messages By This Member #162813 Chris, Sorry, I missed your upload back in July. It appears that block connectivity cannot handle the same turntable definition on two different panels. If I remove the block assignments from one of the turntables, then the errors do not occur. Probably not a good solution. I find it curious that the York turntable does not have the same issue. I suspect that is because it is not DCC enabled. Or it might be caused by multiple entry and exit tracks that connect to other blocks. A brute force approach that might work is creating virtual blocks for the second Bonton turntable and link the real and virtual blocks with Logix or a script. Dave Sand toggle quoted message Show quoted text On Aug 14, 2019, at 6:03 PM, SwissChris <chris@...> wrote: Since I posted and uploaded the XML file, I've redrawn both the main, and the local panels pertaining to the turnatable.and the problem is still there. I've now upgraded to JMRI 4.16 on all machines and the error message now appears on all JMRI 4.16 on PCs both connected and unconnected Windows 10 Proffessional on PCs connected and unconnected XML files stored on a network drive accessable by all PCs Currently 1 connected PC, 1 unconnected tower and 1 unconnected laptop
Spuds McCat All Messages By This Member #162819 I normally see that error when use the wrong block on one of the panels. Check the blocks that neighbor toblock "Bonton TT Spur 1" and make sure they're really the same. II've found blocks with ALMOST the same name, being one above/below the block I meant, etc. toggle quoted message Show quoted text On Thu, Aug 15, 2019 at 12:08 AM Dave Sand <ds@...> wrote: Chris, Sorry, I missed your upload back in July. It appears that block connectivity cannot handle the same turntable definition on two different panels.? If I remove the block assignments from one of the turntables, then the errors do not occur.? Probably not a good solution. I find it curious that the York turntable does not have the same issue.? I suspect that is because it is not DCC enabled.? Or it might be caused by multiple entry and exit tracks that connect to other blocks. A brute force approach that might work is creating virtual blocks for the second Bonton turntable and link the real and virtual blocks with Logix or a script. Dave Sand > On Aug 14, 2019, at 6:03 PM, SwissChris <chris@...> wrote: > > Since I posted and uploaded the XML file, I've redrawn both the main, and the local panels pertaining to the turnatable.and the problem is still there. I've now upgraded to JMRI 4.16 on all machines and the error message now appears on all > JMRI 4.16 on PCs both connected and unconnected > Windows 10 Proffessional on PCs connected and unconnected > XML files stored on a network drive accessable by all PCs > Currently 1 connected PC, 1 unconnected tower and 1 unconnected laptop >
Dave Sand All Messages By This Member #162822 A turntable spur is normally a single track segment, optionally with a block assignment. The track segment is not connected to anything except its turnout ray location and an end bumper. This means that the spur block has no block neighbors. If this occurs on two different panels, the indicated warning occurs. This appears to apply to any track segment with a block assignment but no block neighbors. If I split the spur track segment, assign it a different block name (such as appending a letter) and make the new track segment hidden on both turntables, the problem does not occur. Since it is a dummy block, occupancy is not affected. And since it is hidden, the panel looks the same when not in edit mode. Dave Sand toggle quoted message Show quoted text On Aug 14, 2019, at 9:36 PM, Spuds McCat <spudsmccat@...> wrote: I normally see that error when use the wrong block on one of the panels. Check the blocks that neighbor toblock "Bonton TT Spur 1" and make sure they're really the same. II've found blocks with ALMOST the same name, being one above/below the block I meant, etc. On Thu, Aug 15, 2019 at 12:08 AM Dave Sand <ds@...> wrote: Chris, Sorry, I missed your upload back in July. It appears that block connectivity cannot handle the same turntable definition on two different panels. If I remove the block assignments from one of the turntables, then the errors do not occur. Probably not a good solution. I find it curious that the York turntable does not have the same issue. I suspect that is because it is not DCC enabled. Or it might be caused by multiple entry and exit tracks that connect to other blocks. A brute force approach that might work is creating virtual blocks for the second Bonton turntable and link the real and virtual blocks with Logix or a script. Dave Sand On Aug 14, 2019, at 6:03 PM, SwissChris <chris@...> wrote: Since I posted and uploaded the XML file, I've redrawn both the main, and the local panels pertaining to the turnatable.and the problem is still there. I've now upgraded to JMRI 4.16 on all machines and the error message now appears on all JMRI 4.16 on PCs both connected and unconnected Windows 10 Proffessional on PCs connected and unconnected XML files stored on a network drive accessable by all PCs Currently 1 connected PC, 1 unconnected tower and 1 unconnected laptop
Jeff_Rowe All Messages By This Member #166500 Hi Dave, is this problem with turntable stub tracks going to be fixed? ? I also have a TT with 25 stub tracks on two different panels showing this connectivity problem using JMRI 4.16. ?Not sure your suggestion in post #162822 is appealing. Thanks, Jeff Rowe O Scale Trainmaster, Golden State Model Railroad Museum, Pt. Richmond CA
Dave Sand All Messages By This Member #166571 Jeff, The warning will no longer appear as of the 4.17.7 test release. Dave Sand toggle quoted message Show quoted text ----- Original message ----- From: Jeff_Rowe <jhrowe@...> To: [email protected] Subject: Re: [jmriusers] Warning - Connectivities for "Block Bonton TT Spur 1" in panels Bonton and Bondale are not compatable Date: Friday, November 29, 2019 2:59 PM Hi Dave, is this problem with turntable stub tracks going to be fixed? ? I also have a TT with 25 stub tracks on two different panels showing this connectivity problem using JMRI 4.16. ?Not sure your suggestion in post #162822 is appealing. Thanks, Jeff Rowe O Scale Trainmaster, Golden State Model Railroad Museum, Pt. Richmond CA

Previous Topic Next Topic