{"id":37978,"date":"2023-07-21T11:21:18","date_gmt":"2023-07-21T10:21:18","guid":{"rendered":"https:\/\/photonics.laser2000.co.uk\/?p=37978"},"modified":"2023-07-21T11:21:18","modified_gmt":"2023-07-21T10:21:18","slug":"zaber-controller-feature-autodetect","status":"publish","type":"post","link":"https:\/\/stagingphotonics.laser2000.co.uk\/?p=37978","title":{"rendered":"Zaber Controller feature: AutoDetect"},"content":{"rendered":"\n

Zaber controllers can support a wide variety of peripherals (i.e. motion control solutions with motor and mechanics, but excluding the driver and controller), including rotary and linear models, stepper and direct-drive motors, different encoder and limit sensor types, and a range of motor rated currents. Each peripheral needs to be controlled differently to achieve high performance and also to avoid damage. For instance, if the controller mistakenly supplied 3 Amps to a small motor rated for 0.5 Amps, it would certainly overheat the windings and damage the motor. To ensure situations like this are avoided, and to make set-up as easy as possible, all new Zaber controllers and peripherals have a feature called AutoDetect. Peripherals with AutoDetect contain electronics that can uniquely identify the specific model. Controllers with AutoDetect can automatically identify a connected peripheral, adjust configuration settings appropriately, and drive the peripheral safely. When driving peripherals without AutoDetect (including legacy peripherals and non-Zaber peripherals), the controller can still help prevent misconfiguration.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"AutoDetect
AutoDetect peripherals have a chip inside that allows Zaber controllers to identify them and configure settings automatically.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n
\n\n\n\n
<\/div>\n\n\n\n

Peripheral detection and activation<\/h3>\n\n\n\n

In the context of a Zaber controller and peripheral, “activation” refers to all the steps a controller performs to configure one of its axes to safely drive a particular peripheral. Note that controllers may have one or more axes and each may be activated independently. When a controller axis is “active” (i.e. has been “activated”) the controller will accept motion commands for the axis and attempt to drive the connected peripheral using the currently configured settings, such as hold current and running current. When a controller axis is “inactive” (i.e. has been “deactivated”) the controller will reject motion commands for that axis with the reason INACTIVE and will not apply any current to a connected peripheral.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"Peripheral
In most cases, AutoDetect peripherals will activate automatically when plugged in. This LHM peripheral has been activated.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Controllers with the AutoDetect feature constantly monitor each of their axes to detect whether a peripheral is connected. When there is no peripheral connected to an axis, the controller will automatically deactivate that axis (i.e. disable the driver, present the FZ (Peripheral Inactive) warning flag, and reject motion commands with the reason INACTIVE). When the controller detects that a peripheral has been connected to an axis, the controller will first determine if it is safe to activate the axis (i.e. update relevant settings, enable the driver, and begin accepting motion commands). The activation process differs depending on whether the peripheral also has the AutoDetect feature or not.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"Peripheral
This AutoDetect peripheral has an inactive fault, likely due to being unplugged. The axis will reject motion commands until it has been activated.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n
\n\n\n\n
<\/div>\n\n\n\n

Peripherals with AutoDetect<\/h3>\n\n\n\n

AutoDetect peripherals contain an on-board memory chip with identifying information such as the peripheral ID, serial number, and sometimes other data. Their product names always end with the letter “A”. When an AutoDetect peripheral is connected to an AutoDetect-capable controller, the controller reads the peripheral ID.<\/p>\n\n\n\n

The controller will automatically activate the axis the peripheral is connected to under the following conditions:<\/p>\n\n\n\n