System Settings

⚠ Warning! System settings should never be changed unless you are completely sure of what you are doing.

Add Chain Cycle Time to SMV ✎

When enabled, the operator will get a small bonus to the operation SMV for the time the chain moves after the operator switch has been pressed.

When disabled, the operation SMV should not include chain movement, but only actual operation time.

Allow Replacement Loading ✎

When replacement loading is active (default), the system will allow additional carriers to be loaded to an orderline to make up for the faulty ones.
Rejects and second quality products will increase the target quantity of the order line.

When disabled, no more than the original quantity can be loaded, even if there are rejects or second quality products.

Api Restart Schedule ✎

It is possible to make the API automatically restart itself on a set schedule. This will occur after the daily maintenance routine has completed.

The restart will result in the system stopping for up to a minute.

Completed Order Line Retention ✎

This setting controls how many days order lines are kept after they have been completed. see Delete Completed Order Lines for more details of when an order is considered completed.

Incomplete Order Line Retention ✎

The amount of time the system will wait before deleting an incomplete order line.
If the last order line of an order is deleted, the order is also deleted along with it.

Backup Interval Minutes ✎

Interval between backups.
Can only be set in fixed intervals, ranging between each minute to daily, or disabled.

Backup Retention Days ✎

Sets how many backups should be saved.
This mainly depends on the Database Backup Interval, where the more often you perform backups the higher number of retained backups.
For instance, if Database Backup Interval is set to Daily and Database Backup Retention is set to 7 you will retain the last weeks backup files.

Buffer Carrier Arrival Alert ✎

When a buffer expects to read a carrier, but is not able to, this will trigger a UI warning notification after the specified amount of seconds have passed.

Setting this to 0 will disable the UI notification.

Buffer Matching Algorithm ✎

Decides how buffer calls should match carriers.

When an operator places a buffer call, the buffers will be searched for matching carriers. Matches can be made either across all available buffers ("Breadth"), or first inside the content of a buffer ("Depth"), or a custom search.

Breadth First

All the buffers are searched simultaneously, in the order the carriers are placed in the buffers. Matching starts with the first carrier in the first buffer and if not matched moves on to the first carrier in the second buffer and so on.
Generally this will result in more buffers being utilized, and therefor can more quickly match a carrier. Gives shorter total delivery time and is therefore a good default setting.

Example:
Available buffers:
7001: 🟢🔴🟢🔵
7002: 🔴🔴🟢
7003: 🟢🔵🔴

Placing a call for two 🟢 carriers will match 7001 and then 7003, since they are first in line for both buffers.
Placing a call for two 🔵 carriers will match 7003 first and then 7001.

Depth First

Each buffer's content will be searched for matches in turn, before searching the next buffer.
This will result in fewer buffers being utilized, but longer delivery times.

Placing a call for three 🟢 carriers will match 7001 and then 7002.
Placing a call for two 🔵 carriers will match 7001, search 7002 and match 7003.

Custom Search

It is possible to manually specify how the buffers should be searched. Selecting the Custom Search option will unlock another system setting, Buffer Matching Prio Groups

Buffer Matching Prio Groups ✎

Manually sets how buffers should be searched for matching carriers. This setting is only displayed when the buffer search algorithm is set to "Custom Search".

Each line represents a group of stations, and stations in the same group are separated with a comma character. A new line begins a new group of stations.

When placing a buffer call the system searches for matching carriers it will apply a Breadth First approach for each group. This can be useful if there are some buffers, such as high-runner buffers, that should be prioritized.

Example, if setting Buffer Matching Prio Groups to:

1001,1002
1003,1004

Available buffers:
1001: 🟢🔴🟢
1002: 🟢🔵🔴🟢
1003: 🔵🟢🔴🟢
1004: 🔴🔵🔴

Buffers 1001 and 1002 will be searched together using Breadth First. If no matches are found, 1003 and 1004 will be search together also using Breadth First.

Placing a call for three 🔴 carriers will search the first group and match 1001 and then 1002, going through all carriers first in line for both buffers.
It will then search through the second group, and match the first carrier in 1004 as it is first in line.
Placing a call for three 🔵 carriers will search the first group and match one carrier in 1002.
It will then search through the second group, and match the first carrier in 1003.

Chain Link Time ✎

Used in combination with setting Add Chain Cycle Time to SMV. This value is the number of seconds it takes for a chain link to move one position. Typical value is 0.22

Change Station Timeout ✎

The operator needs to change stations, a terminal command can be entered to keep the user in an ongoing work mode while moving to the next station.

. F1

If the operator does not arrive to the new station and logs in before this timeout has expired, the system will instead set the operator as logged out and discard the time spent in "Changing Workplace" work mode.
Value is the number of minutes that the operator has to to reach the new work place.

Change Log Retention ✎

All configuration changes in the ui and from the terminals are tracked via change logs. This setting controls how many months these logs are retained.

If there is no desire to have change logs, this can be set to 0, which will disable the functionality entirely.

Company Name ✎

Name of the company where the Eton system is installed.

Daily Maintenance Time ✎

Once a day, the system runs a daily maintenance task to perform backups and other maintenance work. These jobs can be a bit more intensive than normal operations, and it is recommended that the daily maintenance is set to a time of low activity in the system, such as a break or shift change.

Default Language ✎

The default language will be the language displayed when there is no logged in user, and will by default be assigned when new users are created. Default language translations will also be shown on terminals when there is no logged in operator.

Default Locale ✎

The locale controls how number and dates are displayed in the application. The default locale will be used when there is no logged in user, and will be assigned by default to new users.

Default Basic Terminal Message ✎

This setting controls the message displayed on terminals for ongoing operations if nothing else has been configured on the operation or operation group level.

See Operator Message for more info about the fields.

Default Extended Terminal Message ✎

Operation messages be shown on a secondary screen/tablet, see Web Terminal. This is the default message that will be displayed on that screen when nothing else is configured on operation or operation group level.

This message will also be used for upcoming features Bundle Tracking, V2 Terminal.

Default Recycle Limit ✎

This is the default value for the Recycle Limit. Applies to all operations without an override value.

Default Remember Operation ✎

This is the default Remember Operation setting for all operations. Applies to all operations without an override value.

Default Terminal Restore Time ✎

Some messages appear on terminals screen briefly. This setting controls how long such temporary messages are displayed. Value should be specified in milliseconds.

Access Token ✎

An access token is used for downloading system updates and ICU updates from the cloud. If your installation is not configured for online updates, contact Eton support to obtain an access token.

Display Bulk Factor in UI ✎

Sets if Bulk Factor should be displayed in UI. If not, it will be removed from all grids and dialogs.

Display Bundle functionality in UI ✎

Sets if [Bundle] functionality should be displayed in UI. If not, it will be removed from all grids and dialogs.

Display Notification on Inspection ✎

Sets if there should be a notification in the Notification Center if a carrier is sent for inspection.

Valid choices are currently:

• None, sends no notification
• On All, sends a notification in all cases
• On Finalize Fault, sends a notification when a fault is registered and the carrier leaves the station
• On Carrier Marked for Inspection, sends a notification when a carrier is explicitly marked for inspection using a terminal command
• On Enter Inspection Station, sends a notification not when the carrier is marked but when it arrives at the inspection station

Display Piece Rate in UI ✎

Sets if Piece Rate should be displayed in UI. If not, it will be removed from all grids and dialogs.

Display Smv in UI ✎

Sets if SMV should be displayed in UI. If not, it will be removed from all grids and dialogs. Please see SMV for more information.

Documentation Base Url ✎

Used to set which URL to contact when fetching inline help.
Used mainly when customer uses Eton Ingenious on a stand alone server without regular internet access.

Delete Completed Order Lines ✎

Order lines that have reached full quantity are considered completed by the system, and this setting will enable automatic deletion of these order lines and orders.

If the system allows Replacement Loading of faulty articles, the order line will be considered complete when the unloaded quantity reaches the target quantity - rejected - second quality.

If replacement loading is not activated, an order line is considered complete once the unload count + reject equals the target quantity.

Delete Incomplete Order Lines ✎

Order lines that have not met the completion criteria (see Delete Completed Order Lines can be removed automatically after some times has passed if this setting is enabled.

EnableSentry ✎

Enable Sentry.io which is used for logging.

Enable Server Reboot ✎

When enabled, after the daily maintenance is completed the entire server will be rebooted instead of just restarting the API. Used in combination with the Api Restart Schedule setting.

Eton Services Url ✎

This sets the port or IP the API is listening on. Typical value is

http://*:80

If the local network has been configured to reroute the eton.systems domain and there is a need to use SSL, the following setting can be used.

https://eton.systems:443

Changing this setting requires a system restart to take effect.
⚠ If this setting is incorrectly changed, it may cause the system to be unreachable. In this case, contact Eton Support.

Fault Registration Text Field ✎

When the operator uses the fault registration menu

The previously performed operations will be listed, so that the operator can find the correct operation to blame.
This setting controls if the operation id or the operation name will be shown on the terminal.

Firmware Packages ✎

This is a list of firmware packages enabled on the Firmware Update page. Access Token must be configured to access the packages.

Possible values include

• 55924-default - Regular stations
• 55929-default - Opta stations, additional line readers
• 55921-default - Regular motors

History Backup Retention Months ✎

Production data may be set to automatically expire after a certain time. This will directly affects the oldest date that reports will return data for.

Leaving this empty disables automatic removal of history data, but will slowly use up disk space.

History Database Breakpoint ✎

A detailed history of all activity in the system is saved to MongoDb databases. At fixed intervals, a new database is created to make handling the large volumes of data easier.
Altering this setting will change how many days or months of data each MongoDb database will contain.

Incentive Mode ✎

The incentive mode is used when multiple operations are completed on one button press. As there is no way to measure the operation time for each operation, the system will instead distribute the total time spent between the operations.

This setting has 3 possible values

• None - Operation time is evenly split
• SMV - Operation time is split relative to each performed operation SMV
• Piece rate - Operation time is split relative to each performed operation Piece Rate

Example:
Operator spends 8 minutes and completes two operations with one button press. First operation has SMV = 3 and second operation has SMV = 1

If incentive is set to SMV, the distribution will look like

Op. 1 = 6 minutes
Op. 2 = 2 minutes

If incentive is set to None, the distribution will look like

Op. 1 = 4 minutes
Op. 2 = 4 minutes

Interleave Buffer Matching ✎

When this setting is activated, the system will try to send out carriers on as many calls as possible, instead of fulfilling call orders in the order that they were placed.

Example 1:

Scenario: Buffer is containing 6 identical products. We have two calls for 3 pieces each, the first one to station 1001 and the second one to station 1002.

When setting is not enabled - Three carriers will be sent to 1001 and then three are sent to 1002.
When setting is enabled - Buffer will send out to both destinations. Carriers will start going out to 1002 before all carriers to 1001 have been dispatched.

Example 2:

An extra function of this setting is that if there is a routing error for 20+ seconds, the system will attempt to re-match the carrier to another call order.

Scenario: We have a buffer with 1 carrier. We have two calls for one carrier each, one to 1001 and one to 1002. 1001 is currently filled up with carriers and cannot receive any more.

When setting is not enabled - Buffer will stop and wait for 1001 to have space available.
When setting is enabled - Buffer will attempt to route the carrier to 1001 for ~20 seconds, and then look for other options. Since 1002 also requires this carrier, the carrier will instead go to 1002.

Installed Languages ✎

Sets which languages the system can be translated into. Includes English and Swedish by default, and can have any number of additional languages.

Line Auto Run ✎

When enabled, the line will automatically start when a carrier has left working position on a station connected to the line or when a carrier arrives via a bridge. The duration that the line will run for can be changed by altering the long and short runtime the motor group connected to the line.

When the line starts either automatically or from a manual start, a timer will run for the value configured as long runtime. If the system detects that the last carrier is about to be unloaded, it will alter the timer to run on the short runtime.

Log Retention Days ✎

The number of days before system logs are removed automatically.

Lowest Rail Match Percentage ✎

Minimum limit for a rail matching a certain criteria.

When routing a carrier the system tries to find the best rail within a station group. It will then will consider (depending on addressing strategy) rails that already have carriers matching that similar criteria.
The Lowest Rail Match Percentage sets a limit for what will be considered a match for those rails, and if more matching products should enter that rail.
Please note that the match percentage only sets a limit for prioritizing, it will not hinder a carrier from entering a rail. For this please see Routing Rules.

Example:
Current rail content (white is empty spaces on rail):
🟢🟢🟢🟢🔴🔴🔴🔵🔵🟣⚪⚪⚪

If lowest rail match percentage is set to 30%, carriers with same criteria will be prioritized to enter the rail:

A carrier of the following color:
🟢 ➡ 40% of carriers already on rail matches color ➡ 👍
🔴 ➡ 30% of carriers already on rail matches color ➡ 👍
🔵 ➡ 20% of carriers already on rail matches color ➡ 👎
🟣 ➡ 10% of carriers already on rail matches color ➡ 👎

MongoDb Archive Path ✎

This is the path where MongoDb will place archive files.

Mongo DB Tools Path ✎

This is the path where MongoDb Tools is installed. This is used for backups and restore of history databases, can also be used for example by Problem Reports.

Multiple Operations Unrepresentative ✎

Some stations are set up as multiple operation. Multiple operations can either be completed one per button press, or all at once with one button press.

When multiple operations are completed at once, there is no way to measure the operation time for each operation, so the system will instead distribute the total time spent relative to each operation SMV.

Example:

Operator spends 8 minutes and completes two operations with one button press. First operation has SMV = 3 and second operation has SMV = 1

In this case the operation duration will be automatically distributed as
Op. 1 = 6 minutes
Op. 2 = 2 minutes

When this setting is enabled, operations completed this way will not be included when calculating skills and efficiency for operators.

Operation Name Display Mode ✎

This controls how operations will be presented in the UI and on terminal, using operation name and/or id.

Operation Start Trigger ✎

The event that starts the operation timer can be configured

Carrier Enter Chain

Operation time starts when the carrier enters the chain, this was the default in versions previous to 1.14

Chain Movement Start

Operation time starts when the operator switch is pressed and the chain starts moving.

Chain Movement End

Operation time starts when the chain stops moving. This time is estimated based on the chain spec and the Chain Link Time setting.

Percentage Display Mode ✎

Choose how percentages on pages and in reports are displayed.

• No decimals - eg. 23%
• One decimal - eg. 22.5%
• Two decimals - eg. 22.45%
• All - eg. 22.453452%

Rebalance Points ✎

Reassigns carriers to more prioritized stations.

The rebalancing feature will actively try to re-assign carriers to stations that need them the most. Carriers will be swapped if they have the same content and this would help finishing a product sooner. This is useful when the transport distance is long.

When a carrier passes a specified point in the system a check will be made if the carrier can be used to finish an order earlier. A node will be selected as the rebalancing point. This can be any node that has a reader on the line; a station, line server or additional line reader.
Next is the rails that this rebalancing check will consider. For best effect the rails should be in close physical proximity to the selected node.

When a carrier addressed to one of the listed rails passes over the reader, the system will determine if the carrier is going to a rail with a low amount of carriers (eg. low rail load). If it is, it will continue there.
If the carrier is not addressed to that rail, it will check if there is another carrier further back on the same route (that has not yet passed the reader) that is addressed to that low load rail.

If there is a matching carrier, they will be swapped so the low load rail will be filled up earlier. The swapped carrier farther back will now go to the rail with a higher rail load.

Rebalance points are specified one per line. The full node id including ICU should be used.

Example:
Rebalance Points setting is

20101:1001,1002,1003

Which tells the system that we want to use node 101 on ICU 2 (full node id 20101) as rebalance point, and that it should rebalance carriers heading to any of the rails 1001, 1002 and 1003.

Carriers currently on main line, moving in ➡ direction:
🔵🟢🟣🟢🔴🔵🟢🟢🔴🔴🔵

1001: (empty)
1002: 🔵🟣
1003: 🟢🔴🔵

When a 🔵 carrier addressed to 1002 passes the rebalancing point if is determined that 1001 needs that carrier more. The carrier is swapped with another 🔵 carrier addressed to 1001 farther back, so 1001 gets its carrier earlier. 1002 also gets its carrier, but a little later.

Recycling Behaviour ✎

This will control how carriers are addressed when it's possible to perform the next operation on the same station. Usually this indicates a recycle, but can also be the case if the route has the same station in consecutive operations.

Default

The carrier will be addressed according to the best station determined by the addressing strategy.

Same Station

The carrier will always try to go back to the same station, if the route allows it.

Register Faults on Operation Group Id ✎

When enabled, the operator will use the operation group id instead of the operation id when registering faults on the terminal.
Make sure that routes do not contain multiple operations from the same group, or fault registration may not be possible.

Will now use the 2nd option (operation group id) for the first parameter.

Routing Message ✎

This is the text that is briefly shown when a routing has succeeded. By default, it will show the carrier that has been routed and the destination that it has been routed to.

Routing Message Duration ✎

When a carrier routing has completed, a short message is displayed on the terminal connected to that station. This sets the number of milliseconds that message is displayed.

Setup Mode Message Duration ✎

This is the time in milliseconds that confirmation messages in setup mode are displayed on terminal.

Share Usage Metrics ✎

EtonIngenious collects usage statistics of hardware and software components, to be able to give better support.
By collecting metric data Eton receives information about how much each part of the system is being used and can from that infer potential problems due to wear etc.
The metric data is summarized and anonymized before sending.

This metric collection can be switched of by setting Share Metrics Usage to false.

Shift Data Retention ✎

Number of shifts that should be retained. These are used on the Production Status page to show how production has performed the last number of shifts.

Split Workload Limit ✎

Minimum number of work load level that all stations in a station group have to reach before the system switches over to the configured addressing strategy. See Addressing Strategies for more info.

Split Workload Unit ✎

How the workload is measured. See Addressing Strategies for more info.

Station In Multiple Machine Groups ✎

Machine groups are a way to validate that the operations are done on compatible stations. If this setting is set to false, adding a station to a machine group when it is already part of a different machine group will remove it from the first machine group. This makes administration easier when changing machines.

Swap Buffer Call Carriers On Arrival ✎

When this is enabled, carriers can automatically be transferred between sequenced buffer calls.

This is done when the carrier is about to enter a bridge or a station rail, however the carrier is not the first in the sequence and we could normally not unload it.

The system then looks for carriers that are out of alignment and check if we can switch call with any of them.
If all call criterias match both carriers, we can switch between them so that the carrier we are attempting to unload now belongs to the first call, and the carrier that is out of alignment belongs to the call that we previously had.

This is used to quickly resolve the issues that can occur after a blocking call to a station somehow misses unload, for example due to rail overload.

Swap Buffer Call Carriers On Departure ✎

This will allow calling buffers to send out carriers that belong to sequenced carriers in some scenarios where it would not normally be possible.

The system will try to find carriers that are out of alignment, find the lowest sequence of those carriers and then attempt to switch the carrier we are now sending out from the buffer with the carrier we found.

If both call criterias are a match to both carriers, we can swap them.

System Time Zone ✎

The time zone that the Eton installation is located in.

Terminal Account Provider ✎

This sets the account provider to used when an operator logs in with one of the terminal commands.

Normally this should be set to "Eton Terminal Account", but can be set differently if another account provider has been activated via customer module.

When using "Eton Terminal Account", login details are stored and managed via the Eton system.

Terminal Light Mode ✎

Set the logic of how the light connected to a feeding buffer terminal should be used.

• None - API does not control the light. The light may still have some function handled by a customer integration module.
• Feeding Buffer Error - The light will be activated when there is a motor error on any of the motors connected to the feeding buffer.

UI Account Provider ✎

This setting controls what account provider should be used when logging into the web UI.

Normally this should be set to "Eton UI Account", but can be different if another account provider has been activated via customer module.

When using "Eton UI Account", login details are stored and managed via the Eton system.

Use Original Order Number ✎

When enabled, an additional field will be present on the Order administration page.
Original Order Number can be used to track external reference numbers for an order.

Work Mode Write Interval ✎

How often ongoing work modes are written to the history database. Having a shorter interval enables more fine grained reports on work modes, but also increases storage space and increases the time to run reports.