Cookie Consent by Free Privacy Policy Generator Update cookies preferences
All Categories Interfaces Electric Nutrunners

Electric Nutrunners

Use the Devices > Tighten menus to configure nutrunner tools connected to a station, or you can configure your station to simulate a tool.

This will configure how the Tascus station will process Tighten steps within a production sequence.

Station Configuration

In this screen, you can select whether the station is connected to a tool using IO, Ethernet Open Protocol or Manual Entry method.

Downtime.png

Tool Interface

Tool Interface

IO Connector

Uses a digital input output device (Brainboxes or Wago) to control the nutrunner controller using it's digital inputs and outputs

Ethernet Open Protocol

Connect to the nutrunner controller via an Ethernet network cable, sends commands and reads data using Open Protocol

Manual Entry

Uses no hardware, prompts the operator to Pass or Fail the tighten operation. Use this when using manual torque wrenches

IO Connector

When using the IO Connector, use this page to specify which inputs and outputs are used to signal to the controller. You will need to ensure this page is configured the same way as the nutrunner controller via it's control panel.

Config.png

Ethernet Open Protocol

Use this screen to add tools using their IP address and port number to the Tascus station Tool Table

For Desoutter tools:

Tool ID 01 = wired tool

Tool ID 51 - wireless tool

setup:

Config.png

Configuring Psets

It is recommended to use a standard list of Psets across all controllers so that when you create a Tascus sequence, the same Pset will be selected, no matter which production station or tool is used.

Manual Entry

This mode is useful when in pre-production mode, and you don't have any tools to connect to. When the production sequence runs, the operator will be able to click a button on the screen to Pass or Fail the tighten operation

Downtime.png

Diagnostics

Use the Tighten > Diagnostics menu once you have configured the tool, to have full manual control and to confirm communications.

Diagnostics.png

Simulating a Tool

For setting up a sequence without a tool, select Settings > Station > Simulated Mode

Simulated.png

This will mean when a sequence runs, Tascus will simulate a tool running and successfully completing a tightening sequence.

Comms Sequence

Tascus runs through the following communications sequence with an Open Protocol controller.

TCP Connection Opened

Action

Tascus

Controller

  1. TCP Connection opened

Sends MID0001

Responds with MID0002

Checks MID0002 received

  1. Tool Disabled

Sends MID0042

Responds with MID0005

Checks MID0005 received

Retries up to 4 times

  1. Unsubscribe Results

Sends MID0063

Responds with MID0005 (Accepted)

OT with MID0004 Rejected

Checks MID0005 received

Retries up to 4 times

  1. Tool Enable

Sends MID0043

Responds with MID0005

Checks MID0005 received

Retries up to 4 times

  1. Select Pset

Sends MID0018 + Pset ID

  1. Subscribe Results

Sends MID0060

No Ack Flag = 0

Responds with MID0005 (Accepted)

OT with MID0004 Rejected

Checks MID0005 received

Retries up to 4 times

  1. Waiting for Results

Keeps polling for a message from the controller with last tightening results

Responds with MID0061

Last tightening results

Sends MID0062 Ack Last Result

Decodes last tightening results

  1. Unsubscribe Results

Sends MID0063

Responds with MID0005

  1. Disable Tool

Sends MID0042

Responds with MID0005

Checks MID0005 received

Retries up to 4 times

*Keep Alive

Sends MID9999

Every 5 seconds

Was this article helpful?

Thanks for your feedback!