OC32 Firmware 0.0.2.3

Adjustments Servo Range

• There is a number of changes in the definition of Servo Range and (major modifications in) the internal programming code. This will make it possible to implement auto-suspend later. The behaviour of the OC32 should not have changed, since the definitions are "backwards compatible".

LED configuration

• It is now possible to configure the diagnostic LEDs on the OC32

OC32 Config 0.0.2.3

Tab General

Added the possibility to configure the diagnostic LEDs. Possible options: Green

• Basic DCC Packet = When a Basic DCC Packet is received within the configured address range
• eXtended DCC Packet = When an Extended DCC Packet is received within the configured address range
• OM32 Message = When an OM32 message is received with the correct module address
• OC32 Message = When an OC32 message is received with the correct module address. So called "poll messages" are ignored.
• Idle Flash = Steady "flash" - when no other function is selected

Orange

• DCC Checksum Error = If a DCC packet is received with "checksum" fault.
• All Received Datagrams = With any received datagram (DCC, RS232, RS485) - if no other function has been selecteerd

Tab OC32 Device Configuration

• Under Pin Configuration - Servo the settings for "Range" have been modified. "Delayed Range" has been removed and replaced by "Suspended" in combination with "Servo Initialized". The latter is "read-only", so it cannot be set, just read. The option "Auto Suspend" has been added however this option is not functional yet in 0.0.2.3!!.
• When jou click on the textlabel "Pin" (left) a pop-up appears by which you can copy, paste and clear the (= all!) settings of the respective pin.
• When you click on the textlabel "Aspect" (left, if "Show Details" is selected and Number of Aspects > 0) a pop-up appears by which you can copy, paste, clear and cleanup the settings of the respective Aspect. Cleanup means that instructions after an empty instruction are removed.

Note: If you configure servo-settings of an older firmware than 0.0.2.3 with OC32Config 0.0.2.3 unpredictable effects can happen. So in this case even more than otherwise the rule applies: If you use OC32Config 0.0.2.3 make sure your OC32 at least has firmware 0.0.2.3.

OC32 Config 0.0.2.3c

General

• Because the numbering of modules and outputs starting at address 1 is not exclusively bound to "Koploper", this option is now called "Start Numbering at 1"
• With the button "Transparent Mode", the RM-U or UCCI can be switched in Transparent Mode, in order to configure the OC32's behind the RM-U/UCCI. Thus from now on it is not necessary anymore to startup DinamoConfig for this. Of course your RM-U/UCCI needs to have the correct firmware to enable Transparant Mode RM-U/UCCI.

Tab OC32 Device Configuration

• Above the pin-number now is shown by which serial address (RS485/RS232) and by which DCC address the respecive Pin is called. With a serial connection the address depends on the module-address. With DCC addressing it depends on the configured DCC address range (Tab "General").
• If you enable "Show Details", clicking on the number in front of the instruction activates a pop-up by which you can insert or remove instructions. The instructions after the insertion/deletion point will shift one position.

OC32 Config 0.0.2.3d

Tab OC32 Device Configuration

• In OC32COnfig (0.0.2.3. or later) you wil find a button "Reload DD", meaning "Reload Device Definitions". With this button, while OC32Config is active, a new Device Definition file can be selected. From OC32Config 0.0.2.3d onwards, by holding the "Shift" key while clicking "Reload DD" a definition file can be added to the definitions already loaded in OC32Config.

Enjoy!