AVIDdirector-M2M ™ Technical Reference Guide
Table of Contents AVIDdirector-M2M™ Technical Reference Guide .............................................................................................. 3 Overview.................................................................................................................................................... 3 Features..................................................................................................................................................... 3 Hardware Design...................
AVIDdirector-M2M™ Technical Reference Guide AVIDdirector-M2M™ Technical Reference Guide Overview AVIDdirector-M2M is a dedicated wireless telemetry communication device that is capable of being installed in an industrial environment, to provide communications with a variety of equipment. AVIDdirector-M2M is designed to operate over any carrier’s network through different replaceable radio cards.
AVIDdirector-M2M™ Technical Reference Guide 4. 8 MB of Flash memory for program and persistent data storage, and 8 MB of DRAM memory. Of the 8 MB RAM, up to 6 MB is used for the Java heap, though up to 7 MB may be allocated. Java executables may be any size up to the amount of RAM or Flash installed. 5. Comes with the M2M Application Framework (M2MApp) preinstalled to implement on-terminal behaviors as configured by an M2MXML portal.
AVIDdirector-M2M™ Technical Reference Guide Hardware Design The device contains two processors: an Imsys Cjip Java processor and a Cypress Microsystems PSoC (System On a Chip). The Cjip handles the application and network functions and the PSoC the hardware interfacing.
AVIDdirector-M2M™ Technical Reference Guide The Imsys Cjip processor is unique in that it implements the Java instruction set as its native machine code, avoiding the performance penalty normally associated with Java interpreters and allowing real-time, deterministic behavior needed by embedded applications. The processor includes IEEE 454 floating-point acceleration. The Cjip processor offers far more functionality than traditional J2ME based devices by allowing: a.
AVIDdirector-M2M™ Technical Reference Guide • GPS: Sony 85ma, US GlobalSat 75ma We have seen with the GPRS and CDMA radios connected and turned on but without an active data connection they add an average of 40 to 60 ma to the normal standby current drain of the AVIDdirector (i.e. Idling current is about 105-125 ma for a GPRS radio with a data connection but no data transfer). The Cypress CY8C29866 is the top model in the Cypress product line, operating at 24 Mhz. with 32K of Flash and 2K of RAM.
AVIDdirector-M2M™ Technical Reference Guide involved and transient voltages from motors or relays. The PSoC processor allows the outputs to be configured as either active source/active sink, or having the source and sink operate independently. HVC devices are powered by either the main device supply voltage, (Vsupply – 16 VDC max) or external voltage (Vrail) of no more than 30 VDC. This determines the maximum voltage, which can be supplied or controlled (synced).
AVIDdirector-M2M™ Technical Reference Guide PSoC, RAM, Flash and all other components are available in Industrial temperature (–40oC to +85oC) versions, which would allow the device to operate at these temperatures with a suitable modem. The case is constructed from rugged polystyrene plastic. It is not water or dust tight but should not allow contaminants to enter with normal use. WatchDog Timer Technical Notes Release: 1.6.
AVIDdirector-M2M™ Technical Reference Guide resets. If the WatchDogTimer thread doesn't call "SNAP.feedWatchdog()" then a hardware reset of the AVIDirector is performed without a logging notification - this means that the WatchDogTimer cannot run and the system will spontaneously reboot itself. The WatchDogTimer maintains a list (Java Hashtable) of threads it is monitoring. Each thread must implement the Java interface "WatchDogMonitoredClass" to identify that it will implement the WatchDogTimer contract.
AVIDdirector-M2M™ Technical Reference Guide 2. Communicator. A Communicator is instantiated for each Radio class in the system. It performs the interface between the M2MXML packets the calling the appropriate method for the radio to send and receive messages. When a message is sent, the Communicator ensures the Radio has sent the message correctly or tracks retry attempts by the Radio. Each Communicator has a queue of 25 outgoing and incoming messages.
AVIDdirector-M2M™ Technical Reference Guide M2M Application Framework Software Design AVIDdirector-M2M comes complete with AVIDWireless’ M2M Application Framework (M2MApp) to facilitate rapid development and deployment of M2M and Telemetry applications. It provides far more power than the J2ME Midlet environment since it provides most of the communication, device and system management functions that a developer would normally have to write and test.
AVIDdirector-M2M™ Technical Reference Guide currently not implemented via the existing M2MApp. A developer needs to program in Java and will need a basic understanding of the M2MApp APIs in order to write an M2Mlet. M2MApp is the main program running on the device. It controls the execution of the IODevices, the communication devices (Radios), any user written application (M2Mlet), parsing and generation of M2MXML messages to and from the M2MXML server / portal.
AVIDdirector-M2M™ Technical Reference Guide The user M2Mlet inherits from the abstract class com.avidwireless.AVIDdirector.M2Mlet and implements the start (AVIDdirectorMain adApp) and stop(). All M2MXML messages not addressed to a particular transducer are directed towards the M2Mlet and methods corresponding to each M2MXML message are called depending on the M2MXML message received. The user M2Mlet can override each of these methods if they wish to.
AVIDdirector-M2M™ Technical Reference Guide § receiveDataString(). This will return a String from the Radio, which is normally a M2MXML string. § receiveDataString(int timeout). Like receiveDataString() except it will return a null if it times out without receiving a M2MXML string from the radio. § receiveDataByteArray(byte[] buffer, int offset, int length). Allows receiving binary data from the radio. § receiveDataByteArray(byte[] buffer, int offset, int length, int timeout).
AVIDdirector-M2M™ Technical Reference Guide .NUM_AVG_READINGS Number of reading to average over to get a reading .M2MXML_ADDRESS The M2MXML address for this device. Defaults to the device name (the prefix name before the .CLASSNAME.) This can be a comma separated list of different M2MXML address this will respond to. The first name is used when we send a percept reading. .REPORT_AT Absolute time(s) as a set of comma delimited strings in the form of "hhmmss" that we will report the readings.
AVIDdirector-M2M™ Technical Reference Guide .MATCH_TIMESTAMPS true|false. Defaults to false but if set true then the all NMEA sentences must have the same time stamp or we won't send their data to the portal. This ensures accurate GPS data for position, altitude, speed and direction. .UPDATE_RTC_TIME true|false. Defaults to true to update the AVIDdirector RTC with the GPS timestamp. .UPDATE_RTC_TIME_INTERVAL How often to ensure the AVIDdirector RTC is updated? Defaults to once a day. .
AVIDdirector-M2M™ Technical Reference Guide be set via either the M2MApp.ini file or over the air using M2MXML SetConfiguration portal commands are: § § KeyName.SERIAL_PORT = serial2 TempTrack. This device has two Analog to Digital converter inputs that are accessed by sending an ASCII ‘G’ character to the serial port and it returns a two character strings with the values from 0.0 to 999.9 This is best used as a sample of a user written IODriver class.
AVIDdirector-M2M™ Technical Reference Guide Through M2MXML the user can program on device behavior such as trigger limits, sensor deadzones, polling modes, scheduled execution, and I/O control. This means that for many M2M applications no embedded device programming is required and all device behavior and operation can be specified by M2MXML commands sent over-the-air (OTA) to the device.
AVIDdirector-M2M™ Technical Reference Guide .ANALOG_ABSOLUTE_HIGH=dd.dd Sets absolute high value for the analog input to report a reading to the portal. For Analog In. .ANALOG_ABSOLUTE_LOW=dd.dd Sets absolute low value for the analog input to report a reading to the portal. For Analog In. .ANALOG_DEADBAND_HIGH=dd.dd Sets delta high value for the analog input to report a reading to the portal. For Analog In. .ANALOG_DEADBAND_LOW=dd.
AVIDdirector-M2M™ Technical Reference Guide override of a config file entry. There can be multiple -C config=nnn -C config2=mmm -C config3=xxx entered on the same line. M2MApp.ini.default # Config File: M2MApp.ini Updated: 10/22/2008 9:59:12PM # M2MApp M2MApp Ver:2.0.0(Build:2008102101)[57.10.19.7.10.50.15.39.12] # # Master M2MApp.ini file. This contains all IODEvices, Radios and standard M2Mlets. # Most of them have the .LOAD=false to prevent them from loading. The M2MApp.
AVIDdirector-M2M™ Technical Reference Guide MODBUS_M2MLET.MODBUS_START_ADDRESS=800101 # Names of the Floating values we are reading MODBUS_M2MLET.MODBUS_NAMES=MOD1.AI1,MOD1.AI2 MODBUS_M2MLET.MODBUS_FLOATING=true # Starting address for digital discrete registers we are reading MODBUS_M2MLET.MODBUS_START_ADDRESS1=100001 # Names of the Digital values we are reading MODBUS_M2MLET.MODBUS_NAMES1=MOD1.DI48,MOD1.DI87 # Starting address for floating analog 32 bit registers we are reading # MODBUS_M2MLET.
AVIDdirector-M2M™ Technical Reference Guide M2MIODEVICE.LOADALL=false # ##### IODEVICES ##### # # NMEA GPS Receiver to load GPS.CLASSNAME=com.avidwireless.avidirector.iodevice.GPS_NMEA_Receiver GPS.LOAD=false GPS.SERIAL_PORT=serial1 GPS.MAPSERIALPORT=GPS GPS.RDD_PWR_ON=true GPS.SERIAL_PORT_BAUD_RATE=4800 GPS.SERIAL_PORT_TIMEOUT=5000 GPS.SONY=false GPS.USGLOBALSAT=true GPS.ENHANCED_GPS=true GPS.SPEED_UNITS=MPH # Send GPS readings once every 8 hours unless we are moving GPS.POLLTIME=28800000 GPS.
AVIDdirector-M2M™ Technical Reference Guide SMARTSEN.SERIAL_PORT_BAUD_RATE=19200 SMARTSEN.SERIAL_PORT_TIMEOUT=10000 # Individual AVIDSmartSensors are identified with a name and the _SNUM trailer specifying the address. # Parameters for the device names are .SEND, .MIN, .MAX, .THRESHOLD, .THRESHOLD2, .DELTA, # .DELTA2, .FACTOR, .FACTOR2, .OFFSET, .OFFSET2, .IODEVICE_READING_PROCESSOR_CLASS. # Next is an example for a magnetic sensor 'DOOR' at E9DE0A00 # SMARTSEN.DOOR_SNUM=E9DE0A00 # DOOR.
AVIDdirector-M2M™ Technical Reference Guide MT_CDMA.SERIAL_PORT=serial3 MT_CDMA.SERIAL_PORT_BAUDRATE=57600 MT_CDMA.SERIAL_PORT_TIMEOUT=3000 MT_CDMA.CONNECTION_TYPE=TCPIP MT_CDMA.KEEP_CONNECTION_UP=false #MT_CDMA.PPP_DNS_PRIMARY=205.166.226.38 # CDMA Specific Information MT_CDMA.CARRIER= MT_CDMA.PPP_USERNAME= MT_CDMA.PPP_PASSWORD= MT_CDMA.PPP_AUTHENTICATION=PAP MT_CDMA.PPP_HANGTIME=10000 # M2MXML Portal Information MT_CDMA.SERVER_IP_ADDRESS=aviddashboard.com MT_CDMA.SERVER_PORT=8088 MT_CDMA.
AVIDdirector-M2M™ Technical Reference Guide BOOMER3.LOAD=false BOOMER3.SERIAL_PORT=serial3 BOOMER3.SERIAL_PORT_BAUDRATE=9600 # Maximum time to send a message BOOMER3.MAX_RETRY_COUNT=3 BOOMER3.MAX_QUEUE_SIZE=100 BOOMER3.MAX_FATAL_ERRORS=10 # Mobitex Specific network information BOOMER3.MOBITEX_GATEWAY_ADDRESS=103087 BOOMER3.MOBITEX_GATEWAY_HPID=137 BOOMER3.ENCRYPT_MPAK = false # # Lantronix XPORT PPP Ethernet adapter XPORT.CLASSNAME=com.avidwireless.radio.XPort XPORT.LOAD=false XPORT.
AVIDdirector-M2M™ Technical Reference Guide # Information for Dynamic DNS lookup WIPORT.DYNDNS_AUTOUPDATE=N WIPORT.DYNDNS_HOSTNAME=demo1.avidm2m.com WIPORT.DYNDNS_USERNAME= WIPORT.DYNDNS_PASSWORD= WIPORT.DYNDNS_DNS_TYPE=custom # # Local Ethernet adapter ETHERNET.CLASSNAME=com.avidwireless.radio.Ethernet ETHERNET.LOAD=false ETHERNET.MAX_RETRY_COUNT=3 ETHERNET.MAX_QUEUE_SIZE=100 ETHERNET.MAX_FATAL_ERRORS=10 # M2MXML Portal Information ETHERNET.SERVER_IP_ADDRESS=aviddashboard.com ETHERNET.
AVIDdirector-M2M™ Technical Reference Guide M2Mapp.ini This file is used to over-ride the parameters set in the M2Mapp.ini.default # Config File: M2MApp.ini Updated: 10/22/2008 9:59:12PM # M2MApp M2MApp Ver:2.0.0(Build:2008102101)[57.10.19.7.10.50.15.39.12] # # User specific loading of files SYSTEM.DEVICE_UUID= SYSTEM.DEBUG=1 ß- Use this to set a different debug level DEMO_M2MLET.LOAD=true M2MIODEVICE.LOADALL=true # M2MIODEVICE.POLLTIME=20000 # GPS.LOAD=false ß- You would set this = true to turn on GPS GPS.
AVIDdirector-M2M™ Technical Reference Guide Appendix 1 – AVIDdirector Model 100 (see Appendix 9 for Model 200) Pin and I/O Definitions External Connector Pin Definitions AVIDdirector-M2M model 100 board has a Phoenix 5.08mm model1757349 for the 12 position GPIO and 1757242 for the 2 position power connector.
AVIDdirector-M2M™ Technical Reference Guide Debug / Expansion Connector This is a 24-position 2mm header (Samtec TMM-112-01-L-D-SM-P or Sullins 122MAMS), Pin V Range 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 3.3 V 3.3 V 3.3 V 3.3 V 3.3 V 3.3 V 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL 5V TTL Features Imsys JTAG Imsys JTAG Imsys JTAG Imsys JTAG Imsys JTAG Ground Ground Imsys JTAG + 3.3V + 3.
AVIDdirector-M2M™ Technical Reference Guide Radio Connector This is a 24-position 2mm socket, Samtec part number SMM-112-02-S-D-P. Pin Function In/Out PSoC Port +5VDC Power (2.5 Amp max) 1 +5VDC Power (2.5 Amp max) 2 OUT Radio power on signal (1=on) Cjip Port D 5 3 +5VDC Power (2.5 Amp max) 4 OUT /Radio reset (0=reset). Momentary Cjip Port D 4 5 IN /Ring Indicator (0=ring) R 5.7 6 IN /Radio1 serial CTS P 5.3 7 2 OUT I C SLC clock signal P 1.7 8 OUT /Radio1 serial RTS P 5.
AVIDdirector-M2M™ Technical Reference Guide Appendix 2 - AVIDdirector-M2M Digital and Serial I/O Schematics Figure 5.
AVIDdirector-M2M™ Technical Reference Guide Figure 6.
AVIDdirector-M2M™ Technical Reference Guide Serial Port Pin Assignments: Serial 1 – RS-232 DB-9 Connector Pin I/O Function 1 IN DCD-Data Carrier Detect 2 IN RX-Received Data 3 OUT TX-Transmitted Data 4 OUT DTR-Data Terminal Ready 5 Ground 6 IN DSR-Data Set Ready 7 OUT RTS-Return to Send 8 IN 9 CTS-Clear to Send +5V at 250 ma Serial 2 – TTL Serial on RJ-12 Connector February 5, 2009 Pin I/O Function 1 IN CTS-Clear to Send 2 IN RX-Received Data 3 +5V at 250 ma 4 Grou
AVIDdirector-M2M™ Technical Reference Guide Appendix 3 - AVIDdirector-M2M PSoC Pin Assignments Figure 7.
AVIDdirector-M2M™ Technical Reference Guide Appendix 4 – Sample M2Mlet for Simulation Board This is the Demo M2Mlet that is used with the AVIDdirector-M2M Simulation board. The Simulation board has the following port assignments: Pin M2MXML Address Function 1 TTL1.AIN Potentiometer provides 0 to +5V reading (0 to 4095) 2 TTL2.AOUT Light bulb glows in proportion to value of 0 to 63 3 TTL3.DOUT Green LED 1=Turn LED on 4 TTL4.DOUT Red LED 1=Turn LED on 5 TTL5.
AVIDdirector-M2M™ Technical Reference Guide import import import import java.io.InputStream; java.io.IOException; java.util.Hashtable; java.util.Enumeration; /** * Demo_M2Mlet *
* This handles the on device hardware IO for the AVIDdirector-M2M device * using the simulation board. *
* This is for device initiated or monitored hardware. You have to create a * class that implements M2Mlet methods.
AVIDdirector-M2M™ Technical Reference Guide /** * Starts the M2Mlet for the Simulator board. This creates any initial devices and * sets them to defined states. * * @param adApp Inistance of the AVIDdirectorMain application */ public final boolean start (AVIDdirectorMain adApp){ final String NAME = "Demo_M2Mlet.start"; started = false; this.app = adApp; try { // boolean find out if we are in debug mode boolean debugMode = Logger.
AVIDdirector-M2M™ Technical Reference Guide " for the toggle switch and trigger on either"); sensors[2].setDigitalInput(); // have it send a percept reading on either trigger sensors[2].setTriggerValueGoesLow(true); sensors[2].setTriggerValueGoesHigh(true); // TTL2 is the light bulb lamp = app.getM2M_IODeviceForAddress(M2M_IODevice.TTL2); if (debugMode) Logger.debugln(NAME,"Setting up "+lamp.getDeviceAddress()+ " as analog output for the lamp"); lamp.
AVIDdirector-M2M™ Technical Reference Guide boolean retFlag; // return status of a command boolean triggerResponse; // set true if there is a change of value int ttl1Value = -1, ttl3Value = -1, ttl4Value =-1; boolean isDebug = Logger.isDebug(); // cache the debug value while(threadRunning && demoM2mletEnabled) { isDebug = Logger.isDebug(); // update the debug value in case it changed // go through the sensors and send a new reading if it changed for (int device=0; device < sensors.
AVIDdirector-M2M™ Technical Reference Guide getDeviceAddress(), value,PerceptRequest.PERCEPT_TYPE_BIT, null ); app.sendMessageToPortal(perceptMessage); } } catch (InvalidHardwareOperationException ihoe) { Logger.log(NAME,sensors[device].getDeviceName()+ " InvalidHardwareOperationException:"+ihoe.getMessage()); } catch (IllegalHardwareAddressException ihae) { Logger.log(NAME,sensors[device].getDeviceName()+ " IllegalHardwareAddressException:"+ihae.getMessage()); } catch (NullPointerException npe) { Logger.
AVIDdirector-M2M™ Technical Reference Guide returnStatus = true; } return returnStatus; } /** * Stops the currently executing Demo_M2Mlet. * This will try to do any cleanup possible * */ public final void stop() { final String NAME = "Demo_M2Mlet.stop"; if (app!= null) Logger.log(NAME,"Stopping"); threadRunning = false; sensors = null; lamp = null; greenLed = null; redLed = null; sensors = null; thread = null; // release ourselves if (app!= null) Logger.
AVIDdirector-M2M™ Technical Reference Guide Appendix 5 - M2MXML TM Version 1.0 Specification See M2MXML Documentation Included. Appendix 6 – Sample M2MApp.ini Configuration File The M2MApp’s initial behavior is determined by the configuration loaded via the M2MApp.ini file. This is a Java properties file that specifies property names and their corresponding values. The Property names have the format SYSTEM.
AVIDdirector-M2M™ Technical Reference Guide # SensorLogic Portal Device UID number for this device SL.DEVICE_UID=8C71EA041A5741F48A87B314FF02501A # # System Settings SYSTEM.DEBUG=0 SYSTEM.LOGGING=0 SYSTEM.OPTIONS=0 # Level below which we do a GC SYSTEM.GC_WATERMARK = 100000 SYSTEM.GC_RUN_INTERVAL=3600 # # # M2Mlet application class to load M2MLET.CLASSNAME=com.avidwireless.AVIDdirector.Demo_M2Mlet # # # M2M On device address overriding the default ones TTL1.M2MXML_ADDRESS=TTL1.AIN TTL1.IOTYPE=AIN TTL1.
AVIDdirector-M2M™ Technical Reference Guide #SIRIT_READER.CLASSNAME=com.avidwireless.AVIDdirector.iodevice.SiritRFIDReader #SIRIT_READER.M2MXML_ADDRESS=RFIDTAG #SIRIT_READER.SERIAL_PORT=serial2 #SIRIT_READER.TAGTYPE=ISO #SIRIT_READER.POLLTIME=200 #SIRIT_READER.
AVIDdirector-M2M™ Technical Reference Guide Appendix 7 – Upgrading the M2M Java Firmware Locate the CD included in the SDK, and then locate the directory “SNAPDev_Files” which contains the files needed to reload the device. You may also download the files from the AVIDdirector web site where you will find the latest firmware update. The zip file contains three files with a .snp extension. You will need to remove the cover of the AVIDdirector-M2M device before attaching the debug pod.
AVIDdirector-M2M™ Technical Reference Guide When you are in the SNAP Loader program press "l" (the L key) and it will bring up a directory dialog box. Select each of the files located in the SnapDev Files directory IN THIS ORDER. AVIDM2M_Baseconfig_x_x_x.snp AVIDM2M_Snaplib_x_x_x.snp AVIDM2M_AVID_Files_x.x.x.snp ß Load this one first ß Load 2nd ß Load last. Contains AVIDdirector-M2M files x_x_x specifies the current release numbers. After each load your display should have messages similar to this.
AVIDdirector-M2M™ Technical Reference Guide Appendix 8 – Reprogramming the PSoC Firmware The following procedure is used to reprogram the PSoC Firmware. NOTE: ONLY DO THIS IF ADVISED BY AVIDWIRELESS TECHNICAL SUPPORT. IF THIS FAILS OR IS INTERRUPTED THEN YOU WILL HAVE TO SEND YOUR DEVICE BACK TO AVIDWIRELESS FOR FACTORY REPROGRAMMING UNLESS YOU HAVE AN IMSYS DEVELOPER TRACE ADAPTER. 1.
AVIDdirector-M2M™ Technical Reference Guide DO NOT INTERRUPT programming the device or it may corrupt the PSoC Flash and require sending your unit back to the factory for reprogramming. During programming the SYSTEM STATUS light will indicate the progress. It will rapidly blink RED during Flash programming and rapidly blink GREEN when verifying the programming. When done, if successful it will blink GREEN twice or if unsuccessful it blinks the error code using the RED LED three times.
AVIDdirector-M2M™ Technical Reference Guide Appendix 9 – Model 200 TTL Ports and DB-37 Expansion I/O Connector The following is a definition of the Model 200's I/O Expansion Connector. It brings out the console TTL (Serial0), RS-232 (Serial1), TTL Serial that was used for the RJ-12 on the Model 100 (Serial2), and TTL1 to TTL18. TTL7 to TTL18 where used for the HVC1 to HVC4 lines on the Model 100.
AVIDdirector-M2M™ Technical Reference Guide 23 TTL21, TX2 P0_5 Analog Input/Out, Digital In/Out, Serial2 TX Out 24 TTL23, RTS2 P0_7 Analog Input, Digital In/Out, Serial2 RTS Out 25 I2C_SCL P1_7 I2C Serial Clock, Digital In/Out 26 I2C_SDA P1_5 I2C Serial Data, Digital In/Out 27 TTL15 P6_4 Digital In/Out 28 TTL16 P6_5 Digital In/Out 29 TTL17 P6_6 Digital In/Out 30 TTL18 P6_7 Digital In/Out 31 DCD1_232 P3_6 Serial1 RS-232 DCD In 32 DSR1_232 P3_5 Serial1 RS-232 DSR In 33
AVIDdirector-M2M™ Technical Reference Guide I/O Expansion board: The I/O Expansion board brings the TTL I/O ports from the DB37 connector to Phoenix connectors. Below is a list of features and functionality it makes available: 1) It provides access to TTL ports 1 through 23, Gnd and V+. 2) Access to Serial2 is available through TTL20-TTL23. 3) I2C is also available on J5.
AVIDdirector-M2M™ Technical Reference Guide 4) The Connectors are marked with the TTL numbers on the board. 5) There is an optional reset switch also available through the I/O Expansion board. 6) The JP1 jumper setting inside the AVIDdirector can allow for +5V regulated voltage or line voltage (+12V) on port TTL20.
AVIDdirector-M2M™ Technical Reference Guide Appendix 10 – AVIDdirector Jumper Settings The jumper settings on the AVIDdirector main board vary between revisions. Please check your AVIDdirector's revision letter to correspond the correct jumper settings. The 3rd letter of the serial number indicates the revision. Example, A0C17QC00014 is a Revision C board. In the descriptions, Vin refers to the input voltage to the AVIDdirector, which is between 8 to 18 VDC and normally 12 VDC.
AVIDdirector-M2M™ Technical Reference Guide Rev D: JP1 is the DB37 pin 20 jumper that supplies the VRail output voltage with maximum current of 0.5A. JP1 1-2 connects VRail to Vin (nominally 12VDC), JP1 2-3 connects VRail to +5V. JP2 connect to DB-9 pin 9 to supply voltage at 0.5A (peak 2A) JP2 1-2 provides Vin on pin 9. JP2 2-3 provides +5V on pin 9. Rev F: JP1 is the DB37 pin 20 jumper that supplies the VRail output voltage with maximum current of 2A.