Blog

Arbin's blog

LATEST

My test stopped due to an error called “Tokenbroken”

This error indicates too much data logged at a very short period of time. Check the schedule, make sure the data log setting is appropriate. Please open the schedule and locate the Log Limit: Then check the following points: Logging interval (time between data points)Many Arbin machines can acquire data at rates of up to […]

View more about My test stopped due to an error called “Tokenbroken”

Why can’t I see the auxiliary value even though I have already mapped it?

In some cases, users may successfully configure (map) an auxiliary channel, but the corresponding auxiliary values do not appear during test execution. This issue is typically caused by missing schedule assignment or incomplete auxiliary channel configuration within the schedule. Possible Causes No schedule or an incorrect schedule is assigned to the channel Forgot to add […]

View more about Why can’t I see the auxiliary value even though I have already mapped it?

Why does my schedule stop immediately after starting?

In some situations, a schedule may stop immediately after it starts. This behavior usually occurs when certain safety conditions are not met or when required devices are not properly connected. The system automatically stops the schedule to prevent unexpected behavior, hardware damage, or unsafe operating conditions. This article provides common causes and troubleshooting steps to […]

View more about Why does my schedule stop immediately after starting?

ARBIN NEWS   VIEW ALL

INDUSTRY NEWS   VIEW ALL

Scroll to Top