OC32 Release Notes 0.0.0.5_en

OC32 Firmware 0.0.0.5

• Added PWM Configuration Option
• Added PWM Level Command to OM32-command set

It is now possible to modify PWM behavior from the default OM32 mode.

OM32 working mode:

• The output can be set to 16 levels. Internally however, the OM32 has 64 levels. When “level” is applied, the user can choose between linear mode or logarithmic mode. In linear mode the 16 levels are spread equally over the internal 64 levels. In logarithmic mode the 16 levels are spread in such a way that a logarithmic characteristic is achieved. Logarithmic mode is optimized for driving LEDs
• Level-commands do not allow the output to gradually take the target level. The new level is immediately applied, or with a delay, but never gradually.
• When the “Fade”-bit is set in a command, the output gradually takes the new value (either off or on). The speed by which this happens is fixed and has a logarithmic nature. This approaches the fading of incandescent lamps when they are turned on and off.

When an OC32 output is NOT configured, it will automatically switch to PWM mode and imitate the above OM32 behavior as soon as an OM32 command is received for the output. Fading is logarithmic and the output-drive characteristic in level-mode is determined by the level-command.

You have the option to explicitly configure an output for PWM with the following options:

• Linear or logarithmic drive mode. The OC32 has 128 internal levels. In linear-drive mode the external levels are spread equally over the internal 128 levels. In logarithmic mode the external levels are spread in such a way that a logarithmic characteristic is achieved.
• Linear or logarithmic “acceleration”. The term “acceleration” refers to the gradual approach of the target value. Logarithmic acceleration imitates e.g. the fading of incandescent lamps. Linear acceleration can be used for e.g. motors and similar items.
• The fading-speed, referred to as “acceleration”. Acceleration is controlled by the “Acceleration Index (0..31)”. The acceleration is a logarithmic function of the acceleration-index. The higher the index, the faster the acceleration. Index 0 however means “immediate”, so no acceleration. Acceleration can be given as a function of the Acceleration Index and the Lin/Log modes. The following figures however should give a good impression how the timing works.

This diagram shows the difference between linear ans logarithmic fading for a change from 31 to 0. By example index 15 is choosen(click for a larger image)

This diagram shows the relation between the accelaration index and the total fading time from 0 to 31 or reverse.

The Acceleration Index that approaches OM32 behavior most is Index 28.

Parameters can be set as “actual values” and can be written to flash memory. When written in “flash”, settings are retrieved every time the module starts. When writing to flash-memory the setpoint can be written as initial value on which the (PWM) output starts.

When an OC32 output IS configured for PWM, the behavior is fixed and can not be altered “on the fly” by OM32 commands. So for a PWM configured output there is no difference between an OM32 Log-Level and an OM32 Lin-Level command. Lin or Log is fixed by the configuration.

While the OM32 can be controlled by 16 levels, the OC32 can be controlled by 32 levels. Since the Level-commands for the OM32 have only 16 levels an additional OM32 command is available. This command can be issued with 32 levels and “fade” bit When the “fade” bit is set, fading is used according to the configured acceleration parameters.

OC32 Config 0.0.0.5

Release 0.0.0.5 of OC32 Config enables the use of the expanded features of the firmware.
In this release there are 4 tabs:

• General: not yet used.
• OM32Test: This is for testing the OM32 functions. Note that only the original OM32 functions are supported in this tab
• Servo: This is for configuring and testing your servo's. Hold your mouse over the buttons without clicking for an explanation.
• PWM: This is for configuring and testing PWM parameters. Hold your mouse over the buttons without clicking for an explanation.

Further you find a checkbox "Koploper Numbering" at the top of the screen. The OC32 and Dinamo use logic numbering, so modules and outputs count starting at 0. Software, such as Koploper, often numbers modules and outputs starting from 1. If this is the case you can use this numbering scheme by checking the box.