[Documentation Update]: v5.4.0 Documentation updates

[peteGSX]

Documentation details

5.2.34 - ~<A address aspect>~ Command fopr DCC Extended Accessories. This command sends an extended accessory packet to the track, Normally used to set a signal aspect. Aspect numbers are undefined as sdtandards except for 0 which is always considered a stop.

• Exrail ~ASPECT(address,aspect)~ for above. The ASPECT command sents an aspect to a DCC accessory using the same logic as <A aspect address>.
• EXRAIL ~DCCX_SIGNAL(Address,redAspect,amberAspect,greenAspect)~ This defines a signal (with id same as dcc address) that can be operated by the RED/AMBER/GREEN commands. In each case the command uses the signal address to refer to the signal and the aspect chosen depends on the use of the RED AMBER or GREEN command sent. Other aspects may be sent but will require the direct use of the ASPECT command. The IFRED/IFAMBER/IFGREEN and ONRED/ONAMBER/ONGREEN commands contunue to operate as for any other signal type. It is important to be aware that use of the ASPECT or <A> commands will correctly set the IF flags and call the ON handlers if ASPECT is used to set one of the three aspects defined in the DCCX_SIGNAL command. Direct use of other aspects does not affect the signal flags. ASPECT and <A> can be used withput defining any signal if tyhe flag management or ON event handlers are not required.

5.2.33 - Exrail ~CONFIGURE_SERVO(vpin,pos1,pos2,profile)~ This macro offsers a more convenient way of performing the HAL call in halSetup.h In halSetup.h --- IODevice::configureServo(101,300,400,PCA9685::slow); In myAutomation.h --- CONFIGURE_SERVO(101,300,400,slow)

5.2.32 - Railcom Cutout (Initial trial Mega2560 only) This cutout will only work on a Mega2560 with a single EX8874 motor shield configured in the normal way with the main track brake pin on pin 9. <C RAILCOM ON> Turns on the cutout mechanism. <C RAILCOM OFF> Tirns off the cutout. (This is the default) <C RAILCOM DEBUG> ONLY to be used by developers used for waveform diagnostics. (In DEBUG mode the main track idle packets are replaced with reset packets, This makes it far easier to see the preambles and cutouts on a logic analyser or scope.)

5.2.31 - Exrail ~JMRI_SENSOR(vpin [,count])~ creates <S> types. This Macro causes the creation of JMRI <S> type sensors in a way that is simpler than repeating lines of <S> commands. JMRI_SENSOR(100) is equenvelant to <S 100 100 1> JMRI_SENSOR(100,16) will create <S> type sensors for vpins 100-115.

5.2.26 - Silently ignore overridden HAL defaults

• include ~HAL_IGNORE_DEFAULTS~ macro in EXRAIL The HAL_IGNORE_DEFAULTS command, anywhere in myAutomation.h will prevent the startup code from trying the default I2C sensors/servos.
  5.2.24 - Exrail macro asserts to catch : duplicate/missing automation/route/sequence/call ids : latches and reserves out of range : speeds out of range Causes compiler time messages for EXRAIL issues that would normally only be discovered by things going wrong at run time. 5.2.13 - EXRAIL ~STEALTH~ Permits a certain level of C++ code to be embedded as a single step in an exrail sequence. Serious engineers only.

5.2.9 - EXRAIL ~STASH~ feature

• Added ROUTE_DISABLED macro in EXRAIL

Page with issues

No response

[peteGSX]

Just pushed to devel branch a new EXRAIL macro that will send the same message to all serial throttles and all Withrottles. e.g. ROUTE(99,"send a message") ~MESSAGE("Chris moves in mysterious ways.")~ DONE

This will send format <m "text">\n to a dccex protocol throttle and Hmtext\n to a withrottle protocol.

I'm guessing the mod list to accept this will be:

ED Toolkit Protocol library (and anything using it) JMRI Web-throttle

[peteGSX]

Captured.