Programmable Controller Message Output by Debug and Active Mode

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing programmable controllers face issues with debugging messages remaining after development, leading to network bandwidth usage and message content ambiguity, as well as the need to manually delete and rewrite debugging commands.

Innovation Solution

A programmable controller system with a parameter manager and character string data outputter that manages operation modes and outputs messages based on these modes, ensuring appropriate message display during debugging and activation by using first and second arguments to control message execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If debugging messages are incorporated into the program for network communication, then debugging can be performed during development, but debugging messages remain after activation causing message content ambiguity and network bandwidth usage

Engineering Contradiction:
Improvedebugging capabilityVSAvoidmessage identifiability
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent implements a mode parameter that dynamically changes the behavior of message output commands. The same program can adapt its message output behavior based on whether it is in debug mode or active mode, allowing debugging messages to be output during development while being suppressed during activation without modifying the program code.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent uses a mode parameter (debug mode or active mode) that changes the execution behavior of message output commands. By setting the mode parameter appropriately, the system can switch between outputting debugging messages and only outputting activation messages, thereby resolving the contradiction between debugging capability and message identifiability.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If debugging messages are incorporated into the program for network communication, then debugging can be performed during development, but network communication bandwidth is consumed by unused debugging messages

Engineering Contradiction:
Improvedebugging capabilityVSAvoidnetwork bandwidth usage
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The system dynamically adjusts message output behavior based on the mode parameter. During active mode, the controller selectively suppresses debugging messages while maintaining activation messages, thereby optimizing network bandwidth usage according to the operational context without sacrificing debugging capability during development.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

By changing the mode parameter between debug mode and active mode, the system controls whether debugging messages are output to the network. This parameter-based control allows the same program to efficiently use network bandwidth by suppressing unnecessary debugging messages during activation while enabling full debugging output during development.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If net commands are deleted or rewritten after debugging, then the program can be optimized for activation, but the program structure requires manual modification

Engineering Contradiction:
Improveprogram optimizationVSAvoidprogram modification process
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The message output command is designed to serve multiple functions through the mode parameter. The same command structure and same program code can be used for both debugging and activation phases, eliminating the need for separate debugging commands or manual deletion/rewriting of commands. The mode parameter universally controls the behavior across different operational phases.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system automatically adapts its message output behavior based on the mode parameter without requiring manual intervention to delete or rewrite commands. The programmable controller itself manages the differentiation between debugging and activation messages through the mode parameter, eliminating the need for manual program modification after debugging.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12353184B2Programmable controller, programmable controller system, and recording medium
Publication Date: 2025.07.08 MITSUBISHI ELECTRIC CORP
  • US12353184B2 patent drawing
  • US12353184B2 patent drawing
  • US12353184B2 patent drawing

AI summary

A programmable controller includes a parameter manager to manage a parameter including an operation mode setting indicating whether an operation mode of the programmable controller is an active mode or a debug mode, and a character string data outputter to output character string data based on a message output command included in a program in the programmable controller. The message output command includes a first argument specifying whether a command is to be executed when the operation mode is the active mode or to be executed when the operation mode is the debug mode. The character string data outputter outputs or does not output the character string data to a preset destination, based on a result of a comparison between the operation mode setting and the first argument.