Machinery TwinDocs

Signal trace

Walk the dependency graph of any variable or object, with live values.

In a project with dozens of variables, "why is this thing moving like that?" needs a tool. Signal trace shows, for any variable or object, the full chain of what drives it and what it drives, with live values at every node.

Reading a trace

  • Upstream, the drivers: the variables a function reads, a cam's master, the state machine writing to it, the PLC tag feeding it.
  • Downstream, the consumers: variables reading this one, object axes bound to it, mechanisms using it as input.
  • Live values, each node shows its current value while simulating, so you can watch a value propagate through the chain and spot where it stops looking right.
  • Validation, broken references (a deleted variable still bound somewhere, a missing cam) are flagged.

Typical debugging flows

"The object doesn't move." Trace the object → find the bound variable → walk upstream until a node's value stops changing. That node's config is the problem (wrong master, mode still on Constant, PLC tag not updating).

"The motion is wrong by a factor." Walk the chain watching values: the node where magnitude jumps incorrectly has the bad scale factor.

"What breaks if I delete this?" Trace downstream before deleting a variable, every consumer is listed.

On this page