Control a Nortek AS Paradopp product (e.g., a Vector) See http://www.cybermato.com/projects/vectorcontrol for latest version and other information. Usage: vectorControl.pl [options] commandspec(s) Options: -verbose Describe what vectorControl is doing -debug Used for debugging vectorControl -commdev Specify device to use for communications, or "none" (default is usually /dev/ttyUSB0 if it exists, else /dev/ttyS0) -bps BITRATE Specify bit rate to use (e.g., 9600, 19200, 38400, 57600, 115200, etc.; default is 9600); assumes that the device is already set to that bit rate -set_default_bps BITRATE Send a command at the -bps bit rate to change to BITRATE, and tell the device to make that the new default bit rate. vectorControl will then exit, ignoring any further commands. For example, use: -bps 19200 -set_default_bps 9600 if the device is currently operating at 19200 bps but you want it to default to 9600 bps. -set_bps BITRATE Like -set_default_bps, but don't make it the default - it will apply only until the next power down -format Wipe out all data (though not configuration information) currently stored on the device. Will not work unless you precede it with the --really-please-delete-all-the-data-on-the-device parameter (seriously). -skipsleep[=N] Say how long we would have slept but really sleep only N seconds (default 5) - useful (only) for testing/debugging -nowait Don't wait for commands to complete - continue immediately -noexec Don't actually execute any "exec" commands -notreally Same as "-commdev none -skipsleep -noexec"; useful for testing your vectorControl scripts Commandspec(s): any one or more of the following in any order: -do -reset (immediate version of "-do reset") -abort (immediate version of "-do abort") -power_down (immediate version of "-do power_down") -break (immediate version of "-do break") Command: any of the following: reset Send a sequence that should get control no matter what abort Send a sequence that should stop data collection and prepare the device for further commands power_down Tell the device to power down; use break to wake it up break Send break flush Discard any leftover input; implied by abort and reset command_mode Tell the device to expect commands; should not normally be needed, as it is implied by reset and abort (above) read_config TYPE FILE where TYPE is one of: head hardware deployment all Read the specified config info from the device and write it to FILE configure FILE Send the deployment config file FILE to the device. This should be a 512-byte *.pcf file (NOT a .dep file!) generated by running 'Vector.exe -cu' and saving the deployment file. read_clock Display the device's idea of the current date & time; note that the date is shown in European format (day/month/year) set_clock Set the device's idea of the current date & time to what the PC thinks is the current date & time (you ARE using NTP, aren't you?) battery_voltage Show the current voltage of the internal battery, in millivolts get_id Show the device's identification of itself inquiry Show the device's answer regarding its current state list_data Show the list of 'files' of recorded data currently stored on the device download_data NAME [DEST_FILE] download_data INDEX [DEST_FILE] Download data from the file with name NAME or index INDEX (either as shown by list_data) into DEST_FILE. If DEST_FILE is not specified, the name will be the name of the file on the device, with .vec appended, and a date-time stamp appended as well if necessary to avoid a collision with an existing file; e.g., if the file on the device is foo, then the default DEST_FILE is foo.vec or foo.vec.080122-2119 (at 21:19 on 22 January 2008). data_file FILE Specify FILE as the file to which collected data (see collect_data and record_data, below) should be appended. If you want to erase any data already in the file, use "exec rm FILE" first. collect_data TIME [TIME...] collect_data until ABSTIME collect_data NUM samples record_data TIME [TIME...] record_data until ABSTIME record_data NUM samples record_data_quietly TIME [TIME...] record_data_quietly until ABSTIME collect_data tells the device to send the data to the serial port only (device command ST). record_data (device command SR) does the same but also records to the device's onboard memory. record_data_quietly (device command SD) records to the device's onboard memory but does not output to the serial port, and so no data is written to the data file. In the collect_data and record_data commands, the data sent to the serial port is stored in the data file (see data_file command, above). For each command, three forms are available: measuring until a specified amount of time (e.g., 3 minutes) has passed; measuring until an absolute time is reached; measuring for a specified number of samples (which should be equivalent to a specified amount of time, except that one or the other may be more intuitive, depending on the situation). The exception is record_data_quietly, which is only time-based, because with no data coming from the device, there is no reliable way to know when the desired number of samples have been taken. See the sleep command, below, for the syntax of the TIME and ABSTIME parameters. Note that if you specify a TIME or ABSTIME, the effect is to stop after the first data packet is received following the specified time; thus, the actual time may be longer than you requested. sleep TIME [TIME...] Sleep for TIME, where TIME is one or more of: Wd W days Xh X hours Ym Y minutes Zs Z seconds ex. "sleep 20m" or "sleep 1h 37m 29s" or "sleep 7d" sleep until ABSTIME Sleep until the specified absolute time, where ABSTIME is in one of the following forms: YYYY-MM-DD HH:MM:SS YYYY-MM-DD HH:MM:SS am YYYY-MM-DD HH:MM:SS pm DD-MM-YYYY HH:MM:SS DD-MM-YYYY HH:MM:SS am DD-MM-YYYY HH:MM:SS pm YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS am YYYY/MM/DD HH:MM:SS pm DD/MM/YYYY HH:MM:SS DD/MM/YYYY HH:MM:SS am DD/MM/YYYY HH:MM:SS pm HH:MM:SS HH:MM:SS am HH:MM:SS pm ex. "sleep until 2004/06/14 13:02:51" or "sleep until 1:03 pm" *** IMPORTANT NOTES: *** * Dates are in the European format: (day first followed by month followed by year, or year first followed by month followed by day), NOT the US format (month first followed by day followed by year). Putting the year first (followed by month and then day) is the safest way to minimize confusion. * If no date is specified, then either the current or next day is assumed, as follows: If the time specified has already passed for the current day, then it is assumed to refer to the next day; otherwise, the current day is assumed. * You may use a 24-hour clock (00:00 - 23:59) OR am/pm. Specify a time like "14:02 pm" at your own risk. include FILE Read and execute commands from FILE and then continue send CMD Send literal CMD to the device directly with no interpretation or modification ex. "send PD" exec UNIXCMD Execute literal UNIXCMD by passing it to the system shell ex. "exec dvgrab -frames 100000000000000000000000001"