01 / APPLICATION
C# / .NET
WinForms HMI
Manual/automatic modes, recipes, equipment status, alarms and operator records.
WEIWANG / APPLICATION & DEVELOPMENT
Custom AOI Software, PC & PLC Development
Connect machine vision with equipment operation. Discuss custom AOI software, PC applications and PLC programs around your process sequence, interfaces and acceptance requirements.
Discuss your project ↗PC-BASED ARCHITECTURE
Connect vision,
equipment and the host.
WeiWang's customary PC-based stack connects C#/.NET and Machine Vision with PLC handshakes, MQTT data exchange and SECS host communication.
C# / .NET
02 / VISION
Machine Vision
AOI core
Acquisition, ROIs, localization, measurement and defect analysis, with results and image records.
03 / EQUIPMENT
PLC
Control & handshakes
Trigger, Ready/Busy, result acknowledgement and recovery, defined for the actual controller.
04 / FACTORY HOST
MQTT / SECS
Host integration
Publish/subscribe status and inspection data through MQTT; implement SECS/HSMS messages against the host specification.
MQTT topics, data fields, SECS messages and GEM scope are agreed with the customer. Equipment motion and time-critical handshakes remain part of the control workflow.
Discuss PC-based / MQTT / SECS integration ↗Start with the equipment workflow
Define triggering, acquisition, inspection, result reporting and fault handling before splitting responsibilities between AOI software, the PC application and the PLC.
- Vision algorithms, localization and measurement
- Operator interfaces and parameter management
- PLC sequences and inspection handshakes
PC software and inspection interfaces
Depending on the project, discuss C# WinForms and Machine Vision-based development. Plan recipe parameters, manual and automatic operation, equipment status and diagnostic information around operator and maintenance needs.
- Recipes and access requirements
- Images, results and event records
- Communication status and diagnostic messages
PLC programs and communication
Successful read/write access is only one part of integration. Define timing, busy protection, timeouts, retries and result acknowledgement against the actual PLC model and existing program.
- Trigger, Busy, Ready and result confirmation
- Data formats, units and register definitions
- Disconnection and recovery behavior
Scope the delivery before development
Share the operating sequence, existing software availability, camera and PLC models, communication specification and expected cycle time. Agree on test conditions and deliverables before implementation.
- New development or bounded changes
- Simulation and on-site validation conditions
- Source code, documentation and maintenance scope
Frequently asked questions
Can you assess changes to existing software?
Provide the architecture, source availability, licensing conditions and change scope so compatibility and testing can be evaluated.
What PLC information is needed?
Provide the model, communication method, register map, data formats, handshake sequence and an available test environment.
Explore related applications
PLC & MACHINE SOFTWARE DEVELOPMENT
PLC and Complete Machine Software Development
Custom PLC programming and complete machine software development, covering PC-based operator interfaces, manual and automatic operation, equipment sequences, recipe management, alarms, production records and device communication. Integrate AOI inspection triggers, Ready/Busy handshakes, OK/NG results and offset feedback with PLC control, MQTT and SECS/HSMS host communication. Functions, interfaces and acceptance criteria are defined around each machine’s requirements.