Skip to content

Denso

Couples Denso RC8/RC9 controllers and the WinCaps virtual controller (b-CAP). Platform: Windows only.

ParameterExample
Host127.0.0.1
Controller typeRC8 or RC9
WinCaps projectC:\Projects\Cell1\Cell1.WPJ

Addresses are VRC variable symbols: IO<n> for a Boolean, I<n> integer, F<n> float, S<n> string. Joint positions are published as <interface>.axis1 … axisN; an address axis<n> binds a joint under a signal name of your own instead. A virtual controller connection needs the WinCaps project file on the gateway PC.

A position variable P<n> becomes six signals <name>.x, .y, .z (mm) and .rx, .ry, .rz (degrees) plus <name> holding the robot figure, where <name> is the signal’s name. As a PLCOutput it is read; as a PLCInput it is written as one position with the figure the controller reported — and, like every write, only with write access.

  • Manually. Enter the VRC variable symbol: IO<n> (Boolean), I<n> (integer), F<n> (float), S<n> (string), P<n> (position). axis<n> binds a joint under a name of your own.
  • Browse. No browse: enter addresses by hand.
  • File import. No file import. A virtual controller connection needs the WinCaps project file on the gateway PC, but it is not a signal source.
  • From the model. Use Addresses → Import address table… in the signal-mapping section of the CONNECT panel: a CSV or TSV with name;address[;dataType[;topic]] rows, where the name is the model’s signal name. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. Fill from controller… has nothing to match, because this protocol cannot be browsed. See Configuring interfaces.

How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.