Objects and device capabilities

An Object wraps registers, protocols, and device details in business actions that Pages and Graphs can call, such as home an axis, read a point, or run an inspection. For the complete setup flow, see Configure Objects, Pulsar, PLC, Vision, and Safety.

When to use this page

• You are deciding between an Object, PLC Tag, Pulsar point, or Vision Inspection.
• You need the basic Object Tree operations and relationship model.
• A module is enabled, but its resource or Object is missing.
• You need to identify parameters that require on-site engineering approval.

Where to go

Task	Entry point
Add, select, group, or delete an Object	Editor Object Tree
Edit a general Object and its references	Select the Object → Properties
Enable Motion, PLC, or Vision	Settings → General
Configure the Pulsar bus, axes, groups, and IO	Settings → Axis/IO
Edit PLC POUs, Tags, and Tasks	Resources → PLC
Configure Cameras, Inspections, and versions	Resources → Vision or Settings → Vision
Configure engineering interlocks	Resources → Safety
Create a custom Object	Resources → Scripts, then Build

Object Tree basics

Action	How
Add a root Object	Open the context menu in an empty Object Tree area and choose a type
Add a child	Use the parent context menu or another hierarchy action supported by the editor
Inspect and edit	Select the Object and use Properties
Change hierarchy	Drag the Object to its intended parent
Delete	Use the Object context menu after checking Page and Graph references
Call from a Graph	Drag the Object into the Graph and select an available method

A parent-child relationship means ownership, such as a Pulsar Bus owning axes and IO. An Object reference means usage, such as a station Object using a scanner. Do not use hierarchy as a substitute for an explicit business reference.

Choose a device capability

Need	Recommended capability
EtherCAT motion, axes, interpolation, and IO	Motion module and Pulsar Objects
LD, ST, FBD, or SFC control logic	PLC module and PLC resources
Camera capture and visual inspection	Vision module, Camera, Inspection, and Vision Object
Modbus, Omron Host Link, or S7-200 Smart	Matching communication Object
Process recipes	Single RecipeManager Object
Lightweight tabular data on one device	RecordStore
Timed steps, logging, or organizational nodes	Timer, Logger, or Node
Custom protocol or customer equipment	Custom Script Object

Motion and Pulsar

After enabling and saving Motion module, Axis/IO becomes available. Maintain the bus, axes, motion groups, and IO points there. Pulsar Objects in Object Tree are the interfaces used by Pages and Graphs.

Verify online operation in the order bus, feedback, action. Confirm the target and bus state, read axis and IO feedback, and only then send motion or output commands under low-risk conditions. Start, Debug, or Connect again before expecting configuration changes in a new runtime instance.

PLC

After enabling and saving PLC module, open the PLC root context menu and choose Initialize PLC, then select LD, ST, FBD, or SFC. PLC resources are organized as POUs, Tags, and Tasks. Resolve control-logic and address diagnostics through Build before online testing.

Vision

After enabling Vision module, add a Camera and Inspection, prepare OK, NG, and boundary samples, and validate candidate versions under Versions & Debug. Confirm a production version only after sample and on-site retesting.

Safety

Safety depends on Motion configuration. Create Safety Inputs, Safety Outputs, and Safety Interlocks in that order, then resolve diagnostics in Problems. Run or connect again after saving.

danger

Theseus Safety provides engineering interlocks. It is not a certified safety PLC and does not replace hardware emergency stops, safety relays, or safety controllers.

Use Objects in Pages and Graphs

• Call semantic Object methods instead of copying low-level addresses into Pages or Graphs.
• Use Graphs to coordinate equipment steps, waits, timeouts, and failure branches.
• Use Page Methods for UI interaction, not as the complete equipment process.
• After changing Objects, device configuration, or Graphs, stop and restart the app to verify a new runtime instance.

RecordStore example

For a device point table:

1. Add RecordStore in Object Tree.
2. Define fields such as point name, address, type, and notes in Properties, and choose a suitable storage mode.
3. Use the Object methods from a Page or Graph to read, add, update, and delete rows.
4. Test an empty table, normal records, duplicates, and invalid data.

RecordStore fits lightweight rows owned by one device. Put large histories, complex queries, or cross-device shared data in an external system and use a Query.

What success looks like

• Device names and hierarchy in Object Tree make sense to process and site staff.
• Pages and Graphs call semantic methods rather than scattered address constants.
• Pulsar, PLC, and Vision authoring configuration agrees with online feedback.
• Missing modules, types, references, or artifacts produce actionable Problems diagnostics.
• Safety and every real output have separate human acceptance evidence.

Common issues

An Object type is missing or marked in red

Check whether its module is enabled, its custom Script or PLC Build succeeded, and the current environment contains the required plugin. Do not substitute a similar type.

Device settings are saved, but online behavior did not change

A running instance does not replace its device tree automatically. Stop, then Start, Debug, or Connect again.

I cannot drag an Object into a Graph or find its methods

Resolve Object type, Build, and callable diagnostics, then refresh resources. Confirm that you are using a configured instance rather than an unavailable type.

Page or Graph breaks after deleting an Object

Search references before deletion. Restore the Object, or migrate every reference and validate again.

How AI can help

AI can organize device lists, inspect references, draft configuration, and add test cases. For example:

Perform a read-only review of the current Object Tree, Pulsar, PLC, and Vision configuration. Group findings by device semantics, missing references, unit or range risks, and unverified actions. Do not connect equipment or issue outputs.

Device, PLC, Vision, and Safety content generated by AI still requires review by the responsible specialists.

What a person must confirm

• Protocols, addresses, units, ranges, direction, limits, homing, and task intervals.
• Preconditions, failure branches, and recovery for every real action.
• Vision sample coverage and the production version.
• Hardware safety circuits and Safety interlocks. AI cannot approve a safety design.