AMX RPMLoader Uživatelský manuál Strana 3

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 7
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 2
What’s New in X-Series Controllers
3
What’s New in X-Series Controllers
Serial, IR and AxLink port diagnostics
When a string is sent to a serial port or an IR pulse to an IR port, the X-Series controllers can detect and report if the port
being used is in a fault condition. The controllers can also detect certain fault conditions on the AxLink bus. The
following fault conditions are recognized:
The serial cable is not connected
The Serial pin is connected to another pin
The IR bud is not connected
The IR bud is wired backwards
One or both AxLink bus data pins are shorted to power or ground
On the first attempt to use a port that is in a fault condition, the controller will do the following:
Quickly flash the front panel LED of the port being used 10 times
Generate an ONERROR data event in NetLinx
Report the error to any Duet Module that has claimed the port
Report the error to RMS if the controller is connected to an RMS server
Set an error flag for that port
The status of the error flag can be queried using the GET FAULT NetLinx command, which will result in a DATA
EVENT where the return status can be parsed.
If the fault condition persists, subsequent attempts to use the same port will only result in the quick flashing of the front
panel LED. The ONERROR event and the reporting to a Duet Module or RMS only occur on the first attempt after
booting or after the fault status is cleared. This prevents a flood of redundant error messages when a faulted port is used
continuously.
The fault status is cleared on a successful transmission over the port and can be cleared manually using the CLEAR
FAULT NetLinx command.
For serial and IR ports, an error condition is only checked at the time the port is used; so unused serial and IR ports will
not generate errors. AxLink bus errors are checked at boot time.
AxLink power measurement and control
IMPORTANT: The NX-Series controllers can NOT be powered via the AxLink port. The +12V pin on the AxLink
connectors are designed only for voltage output. Do NOT connect +12V from a power supply or the NXA-PDU
to the +12V pin on the AxLink connectors, or you may permanently damage the NX controller and/or the
power supply.
The AxLink ports on X-Series controller support a new NetLinx command to turn on and off +12V power output on the
port.
‘AXPWRON [LOWER/UPPER]’ and ‘AXPWROFF [LOWER/UPPER]’ will turn on and off (respectively) +12V
power on the AxLink port.
This messages is always sent to port 1 of the 5001 control device and return status will come from the same port.
The NX-3200 and NX-4200 both have two AxLink connections. These are two connection points for the same AxLink
bus. All AxLink devices connected to the controller must have unique AxLink device numbers even if they are attached
to different AxLink connection points on the controller.
While it is one AxLink bus, the power on these two AxLink connections is controlled independently.
Case Sensitive file system
Unlike the NI-Series controllers, all file names on the X-Series controllers are case sensitive. This includes all user files
created or used within NetLinx or Java code.
If you have legacy code that uses files, it is important that you verify that every reference to each file is consistent with
regard to case.
If your legacy code generates an error when accessing a file, it is likely due to inconsistent use of case in the filename.
Zobrazit stránku 2
1 2 3 4 5 6 7

Komentáře k této Příručce

Žádné komentáře