Echo is a sophisticated reader and debugging command line tool alternative to PolySync Studio's Trace plugin. PolySync Echo was created to easily see which message types are on the PolySync bus, and to get immediate feedback regarding what data is on the bus.
Echo can quickly become a debug tool for determining what kind of information a given sensor is producing in addition to the ability to view message contents generically.
A future release will include enumerations of all active messages on the bus; for now, Echo is a helpful debugging tool that can be used by explicitly defining message types to look for on the bus.
Here's a link to the source code.
To see a full list of available options when starting PolySync Echo you can run Echo's help page:
$ polysync-echo -h
Echo Message Types on the Bus
The default behaviour for Echo is to print the message names of messages available on the PolySync bus. Press CTRL+C to end.
Did you notice a few errors upon Ctrl+C? That's because the terminal application cannot keep up with the rate that Echo is requesting to print to the terminal.
To see a list of just a few types of the messages on the bus, filter by message type using -f option and supplying a message type name.
Running this command will filter for diagnostic trace messages:
$ polysync-echo -f ps_diagnostic_trace_msg
There may be an overwhelming amount of information on terminal; if so, print out only the headers for each message for a more succinct report using -H option:
$ polysync-echo -f ps_diagnostic_trace_msg -H
We can also filter multiple messages at a time:
$ polysync-echo -f ps_diagnostic_trace_msg -f ps_radar_targets_msg
Echo can be specified to run for a supplied duration of seconds:
$ polysync-echo -t 5 -H
Echo Write to FIle
Echo can also write all output to a file by supplying the `-o` flag. Data will also be printed to the terminal.
$ polysync-echo -f ps_diagnostic_trace_msg -o /tmp/ps_runtime_diagnostic_output.txt