• A block MUST be contiguous. ?For example, a-a-a-b-b-a-a-a is not valid. ?A track component with no block assignment will also break the contiguous rule.
  
• Gaps between blocks break block continuity. ?Most of your turnouts do not have block assignments.
  
• A good block design facilitates signaling.
  

• A valid panel has no red, magenta, or yellow connection points. ?There should only be green connections, along with blue for the A connection for cross-overs and slips.
  
• Use the Tools >> Check menu items to look for block issues. ?The should be no "Un-Connected Tracks" or "Non-Contiguous Blocks". ?"Un-Blocked Tracks" entries generally occur for secondary areas such as yards or branch lines.
  
• Sometimes Non-Contiguous will occur for separate unblocked areas.
  

• Missing track segments were added to a couple of sub-panels to fix red/yellow connection points.
  
• The anchor points at the end of lines on the sub-panels were changed to end bumpers. ?The was done using the "Change To" entry in the right click context menu ?for the anchor point.
• The track segment block assignments where extended to include connected turnouts. ?Whether I used he left or right side was arbitrary. ?
  
• CP Leech 330 cross-over was added to the main panel. ?Since that cross-over connects Block 915 and Block 916, it has to be on both the main and the CP Apollo sub-panel.

Hi folks, I’m new to DCC world and just got my share on two out of two non-working decoders. One being BLI P3, and while researching P3 issues I came across this thread on CV217.

?

Apparently, CV217 is not supposed to be documented, because it’s a service CV. The below clarification came directly from BLI tech support, when they were troubleshooting my issue. I’m just sharing and hope it can be of use for those working on BLI decoders.

?

BLI tech:

========

After setting CV217=196, it should either work or not work on the program track - but you could set it to lower or higher values to experiment (range of 0-255).

?

When we designed our latest decoder, we wanted to have a lot of capacitance to prevent pickup issues over frogs and such.

However, that design posed a problem with reading CV's sometimes and in some programming modes because when the energy was used to A) Charge the capacitors, and B) "chirp the motor" - the packet of data could not make it round trip back to the throttle.

Our engineer created CV217 to lessen the amount of power that was given to "chirp the motor" to overcome that obstacle. That's why it's not an NMRA standard - it's a BLI thing.

The higher you set CV217, the less power is given to the motor while programming.

========

2020-02-09 22:56:29,637 ptionhandler.UncaughtExceptionHandler ERROR - Uncaught Exception caught by jmri.util.exceptionhandler.UncaughtExceptionHandler [AWT-EventQueue-0]

java.lang.NullPointerException

at jmri.jmrix.dccpp.DCCppCommandStation.sendPacket(DCCppCommandStation.java:176)

at jmri.implementation.AccessoryOpsModeProgrammerFacade.writeCV(AccessoryOpsModeProgrammerFacade.java:174)

at jmri.jmrit.simpleprog.SimpleProgFrame.writePushed(SimpleProgFrame.java:223)

at jmri.jmrit.simpleprog.SimpleProgFrame$2.actionPerformed(SimpleProgFrame.java:66)

On Feb 9, 2020, at 4:45 AM, Trevor_R <twr@...> wrote:

Bob,

Sorry to have to ask another newbie question, but you stated in your reply:

You can also iterate through the list of running automats, etc.
I can't see any method to achieve this on the page you referenced, nor can I find an example anywhere. Would you be so kind as to provide an example of how to iterate through the list of threads displayed in the thread monitor?

Trevor.

Run build – press print – print window comes up – press properties – check “preview before printing”

OK my way out and “Canon Preview window” shows.?? The window shows the Manifest page.
Press “Start Printing”????? Window disappears and nothing happens, computer just sits there with no error messages.

开云体育