CTserial reads comma-separated value strings from a user-specified serial port, parses individual channel values from the strings and writes the channel data to time-stamped CloudTurbine files.
java -jar CTserial.jar -h
-b <baudrate> baud rate; default = 9600
-bps <blocks_per_seg> Number of blocks per segment; specify 0 for no segments; default = 0.
-c <channel name(s)> name of channel(s) to write data to (comma-separated list)
-d <delta-time> fixed delta-time (msec) between frames; dt=0 (which is the default) to use arrival-times
-f <autoFlush> flush interval (sec) (amount of data per zipfile); default = 1.0
-h,--help Print this message
-p <serial port> port number to listen for serial packets on; default = COM1
-s <source name> name of source to write serial packets to; default = CTserial
-t <trim-Time> trim (ring-buffer loop) time (sec); trimTime=0 (which is the default) for indefinite
-time_in_str the first entry in the received CSV string is the data time; in this case, do not include the
time channel as the first entry in the specified channels list
-x,--debug debug mode
-z,--sim_mode turn on simulate mode (don't read serial port)
The “-bps” option is used to specify the number of blocks per segment. Without this option (or if you specify “-bps 0”) the segment layer is not used in the CloudTurbine folder hierarchy.
Channel names are specified using the “-c <channels name(s)>” command line flag. For instance, this may be “-c chan1,chan2,chan3”. The number of comma-separated values received on the serial port must match the number of channels which have been specified using the “-c” flag.
A simulation mode is enabled using the “-z” flag. Simulated data is produced for as many channels as have been specified via the “-c” flag. When using simulation mode, you must also specify the desired output time period using the “-d” flag. No data is read from a serial port when running in simulation mode.