The Micro830 auger-fill timer can use operator-selected presets instead of requiring a program edit and download for every product or bag-size change. The operator panel writes a setpoint value to PLC memory; the PLC validates that value and uses it to control the existing fill sequence.
Stop changing the timer in the program for each product
Manually editing the timer is the wrong production workflow when operators need to change among known recipes. It ties routine adjustments to someone who can edit, build, and download the PLC program, and it makes a timing change part of a code-change process.
Do not create a separate physical PLC input for every panel button. A touch panel communicates values and commands to PLC memory; the PLC program then decides what to do with them. The separate auger-run and agitator controls mentioned in the application are distinct commands, but they do not require a dedicated hardwired input for every product-and-size choice.
Keep the PLC responsible for the clutch/brake sequence and machine interlocks. The panel should request a fill time or an operating command, not directly replace PLC control of the output. Before changing the machine, identify the existing timer preset and the PLC logic that applies it.
Check: Online or in the program, locate the timer preset and confirm which PLC logic uses it to control the auger clutch/brake. Record the existing behavior as the baseline for commissioning.
Create one PLC setpoint for the selected fill time
Use one PLC variable as the requested fill-time value, expressed in the unit the PLC logic will consume. Configure each product-and-bag-size button to write its corresponding preset to that variable. Multiple buttons can write different values to the same variable; the PLC does not need a separate input or timer for each button.
Keep the operator-facing value separate from the machine output. The PLC should transfer the validated setpoint into the timer preset used by the fill sequence. That separation gives the PLC one place to check limits and prevents the display from taking over the control sequence.
The application describes fill durations in milliseconds, but does not identify the PLC variable type, timer resolution, or current timer implementation. Read those details in the Micro830 project before assigning a tag or setting the panel’s numeric format. Confirm that the PLC can represent the full preset range and that the timer’s time base supports the intended increments. Do not assume that a displayed millisecond value corresponds to one millisecond of actual timer resolution.
Check: With the machine stopped, write a test value through the panel and verify that the intended PLC variable changes to the expected numeric value and unit, without changing the clutch/brake output.
Assign each product button and the fine-adjust controls
Configure the product-and-size buttons as preset selection commands. Each button should write its assigned fill-time value to the shared setpoint. If the HMI software supports momentary or maintained actions, choose the action intentionally and test whether a held button repeatedly writes or leaves a command active; use the panel’s supported behavior and PLC logic to make selection predictable.
For fine tuning, implement separate increment and decrement actions in the PLC or HMI, with the PLC enforcing minimum and maximum permitted values. A one-millisecond step is appropriate only if the timer’s resolution and the numeric representation support it. Otherwise choose a step that matches the actual timer granularity and the process’s adjustment needs.
Prevent arithmetic wraparound or out-of-range values. At the lower limit, decrement should not create a negative duration; at the upper limit, increment should not exceed the validated maximum. Display the active setpoint so the operator can confirm which value is selected before a fill cycle begins.
The source also identifies separate auger-run and agitator commands. Keep these distinct from recipe selection and fill-time editing. Do not make an HMI button the sole means of a safety function; retain the machine’s existing PLC interlocks and safety design.
Check: Test every preset button and both adjustment actions with the machine stopped. Confirm the displayed and PLC values match, and verify that repeated presses at each limit do not produce an invalid value.
Configure the panel-to-PLC communication path
The described Micro830 and C-more Micro combination supports Modbus RTU as a communication option. In this arrangement, the panel reads or writes PLC memory values over the communication link; the buttons do not become individual PLC inputs. The exact panel driver, serial settings, PLC memory mapping, and address notation depend on the selected hardware and project configuration.
Use the manuals for the exact controller and panel models to set matching communication parameters and map the PLC setpoint and command variables to panel objects. Check register width, signed or unsigned interpretation, and the panel’s address convention against the PLC data type. A mismatch can make an apparently valid HMI value arrive in the wrong word, with the wrong sign, or at an unintended location.
Do not copy an address or serial configuration from another project without checking the current controller program and panel setup. If communication is not established, verify the selected driver and physical wiring, then compare the communication settings at both ends. Resolve read/write errors before testing machine motion.
Check: From the panel, read the intended PLC setpoint and write a harmless test value while stopped. Confirm stable communication and verify the PLC sees the same value at the mapped variable.
Keep the PLC in control of the fill sequence
Modify the existing program so the timer preset comes from the validated PLC setpoint rather than a constant that must be changed and downloaded for each recipe. Keep the PLC’s existing sequence responsible for starting and stopping the clutch/brake output. The operator panel selects or adjusts a value; PLC logic determines when that value can affect a fill cycle.
Decide when a changed setpoint takes effect. A conservative approach is to copy the selected value into the active timer preset at a defined point in the cycle, such as before a new fill starts, rather than allowing an edit to alter a fill already in progress. Confirm the actual sequence behavior in the existing program before applying that pattern.
Validate the requested fill time before using it. Use limits derived from the machine’s approved operating range and process testing; do not guess bounds from the HMI screen. If the PLC program cannot distinguish a valid selection from an invalid or stale command, add explicit validity logic before enabling the new operator workflow.
Check: In a stopped test, select a recipe and verify the PLC’s active timer preset updates at the intended point. Confirm the existing sequence and interlocks still govern the clutch/brake output.
Commission presets without risking an uncontrolled fill
Commission the change in stages. First test communications and values with motion inhibited. Then test the sequence under the machine’s approved safe commissioning conditions, monitoring the timer value and clutch/brake response. Keep the prior working program and a way to restore it available until the new interface passes acceptance testing.
- Compare each panel preset against the approved product-and-bag-size timing record.
- Verify increment and decrement behavior, including the lower and upper limits.
- Run the existing sequence and confirm the selected time is used for a new fill rather than changing unexpectedly mid-cycle.
- Check auger-run and agitator commands independently and confirm existing permissives or interlocks remain effective.
- Observe representative fills and verify the machine stops the auger as intended. Adjust process values only through the validated range and established production procedure.
Compare measured fills against the accepted process result; elapsed time alone does not prove correct fill weight. If a time change does not produce the expected result, check the selected value, PLC active preset, timer behavior, and the mechanical clutch/brake operation before changing the recipe again.
Check: Release the interface for operator use only after each preset, adjustment limit, independent command, and representative fill has passed the documented acceptance checks.
Separate a temporary restore from the permanent repair
If the panel cannot communicate or a recipe writes the wrong value, stop using the new selection path. Restore the known-good PLC behavior or approved manual setting under the site’s change-control process; do not bypass interlocks or continue production with an unverified timer preset.
The permanent repair is to correct the mapping, data type, serial configuration, limits, or PLC logic identified by the checks above, then repeat commissioning. Keep a record of the accepted product presets and the program/panel changes so another shift can identify the approved settings.
Stop and contact official AutomationDirect support for panel-driver or panel communication configuration questions, and Allen-Bradley support or the responsible controls integrator for Micro830 program or timer behavior that cannot be resolved from the project and product manuals. Provide the exact panel and controller model numbers, software versions, communication settings, PLC variable type, and observed values.
Frequently asked questions
What happens if I use one PLC input for every preset button?
That adds unnecessary point-to-point inputs for choices the panel can send as values. Map the buttons to a shared PLC setpoint instead, and let the PLC apply the selected time to its timer.
What happens if the one-millisecond adjustment does not change the fill time?
Check the PLC timer’s time base, resolution, and the setpoint data type. If the timer cannot represent a one-millisecond step, select a supported increment and verify the resulting fill in commissioning.
What happens if the C-more Micro writes a different value than the panel displays?
Stop using that value for production. Check the Modbus RTU mapping, address convention, register width, and signedness against the exact PLC variable, then retest with machine motion inhibited. Stop and escalate unresolved panel communication or Micro830 program behavior to the applicable official support channel or controls integrator; do not resume on an unverified preset.