OnTakt User Guide: Difference between revisions

From Knowledge Base
(move tools and maintenance)
Line 10: Line 10:


== Machines ==
== Machines ==
See [[OnTakt Machines]].
See [[OnTakt: Machines]].


== Processes ==
== Processes ==

Revision as of 14:44, 14 February 2023

Getting Started

  1. Set an administrator password
  2. Set the time zone
  3. Define the shop's shift times
  4. Create the first machine

Machines

See OnTakt: Machines.

Processes

Processes allow you to connect machines and programs to tools and inventory tracking. A process is the combination of a machine, a set of program from that machine, a set of tool assemblies that are used for the process, and settings that define the behavior of OnTakt while that process is running.

Creating a process

  • Go to the Processes page
  • Click Create Process
  • Enter a name for the new process and click Create.

Adding programs to a process

  • Right-click the program in the list and click Edit
  • Choose the process to add the program to from the Processes menu
  • Click Save Changes

Aggregating data

To view all the parts produced by a process on any given day, click the group's name in the list of program groups in the Groups section of the Programs page. This chart can then be navigated like an individual machine chart. Note that goals and events are not shown because they can vary between machines.

Part counting

Some looping programs do not enter a completed state, so they can't increment the part count reported by the control. In these cases, it is possible for OnTakt to read the part count from a common variable (also known as a macro variable) that the program can increment each time it loops, producing an accurate part count in OnTakt.

To use this mode, set the part count variable option of the program in OnTakt to the number of the variable on the control that you will be writing to.

A note about common variables on FANUC controls: only variables #500 through #549 are read by OnTakt. Attempting to use a variable outside that range for part counting or value reporting will not work. This is because these are the only common variables that persist across machine restarts on FANUC Series 30i/31i/32i, 0i-D/F, and PMi-A controls.

Variables

OnTakt can read the values of common variables (also called macro variables) from the machine control when it saves a part and add these values to the part record. You can also set up notifications to be alerted as soon as the machine reports a variable that is above, below, or at a threshold you set.

Because the indices of these variable may change between programs, OnTakt allows you to assign names to variable numbers on a per-program basis. This process is called variable mapping:

  1. Go to the Programs page
  2. Right-click on the program you want to assign variables for
  3. Click Edit
  4. To add a variable mapping, click Add Row in the "Variable mapping" section of the program editor
  5. In the text fields that appear, enter the name of the variable and the index that this program uses to store it. When entering the name, all of the names that are already used appear as suggestions. This allows you to click one and use it so that names can be consistent between users and programs.
  6. For notifications, choose a comparison and a threshold. For example, to be notified when a variable is greater than 5, choose ">" for the comparison and enter 5 for the threshold. To turn off notifications, choose "Never" for the comparison (and the threshold will be saved, but ignored).
  7. Add as many mappings as you need. You can remove a mapping by clicking Delete Row in the row of the mapping you want to remove.
  8. When you are done, click Save

The next time a cycle running this program completes, the part record will contain the values of these variables under the names you specified. To view this information, you can open the part editor from a machine chart page, or go to the Parts page, right-click on the part, and then click Edit.

If a machine does not report a named variable when the part is created, a warning will appear on the dashboard until it shows up for a future part.

Serial numbers

OnTakt has a special mapped variable name for serial numbers. If you enter SERIAL as the data name, OnTakt will treat this variable as containing the serial number of the part. This will appear as a suggested name even if you have not used it before.

Example use case: When running parts from bar stock of a known length, a common variable can count the number of parts made from the current bar. When it is a couple parts away from the number of parts you know you can make from one bar, send a notification to prepare to replace it soon instead of waiting for a machine alarm to reduce downtime.

Programs

Each machine has a set of programs that it has reported. OnTakt creates a new program item for each filename the machine reports having loaded even if no parts or events are recorded.

Tools

See OnTakt: Tools.

Inventory

Inventory items are types of tools that are ordered. For example, a certain type of tool insert may be used for many different tools. This insert would be an inventory item, and each tool using it would be linked so that they subtract from the total stock when the tools are replaced.

Maintenance

See OnTakt: Maintenance.

Reports

Report options

OnTakt can collect a lot of data very quickly, and the report options allow you to pick out the data you need without downloading everything.

Machines

Generating a report requires that you select at least one machine.

The parts, programs, or events from selected machines will be included.

Date range

If you frequently export data, you may wish to only include data that was created after the last export. To do this, set the "From" date to the previous export date and the "To" date to the latest day you want to include.

Only parts and events created inside this range will be included in their export files.

Options

See OnTakt Global Settings.