Dear Gene,
I just tried this locally and it seems like the number conversion is
broken in latency-test. Also there should not be a prefix like
base-period in the command line. First thought it was just the capital
"S" but it wasn't. Good news: you don't need them, please try again with
latency-test 1000000 5000000
which are your times in nanoseconds.
latency-test will open an X window to show these values. No idea why,
really, wish it would not.
Best,
Steffen
$ latency-test --help
Usage:
latency-test [base-period [servo-period]]
or:
latency-test period - # for single thread
or:
latency-test -h | --help # (this text)
Defaults: base-period=25000nS servo-period=1000000nS
Equivalently: base-period=25µs servo-period=1ms
Times may be specified with suffix "s", "ms", "us" "µs", or "ns"
Times without a suffix and less than 1000 are taken to be in us;
other times without a suffix are taken to be in ns
On 31.01.22 11:35, gene heskett wrote:
Greetings all;
both my build (on buster armhf) and the buildbot version of 2.9-pre are
failing: terminal output from my build:
===================
pi@rpi4:/media/pi/workspace $ latency-test period -
/usr/bin/latency-test: line 26: [: period: integer expression expected
Note: Using POSIX realtime
HAL: ERROR: thread 'slow' not found
lat.hal:3: addf failed
Note: Using POSIX realtime
===================
terminal output of buildbot version:
===================
pi@rpi4:/media/pi/workspace $ latency-test period -
/usr/bin/latency-test: line 26: [: period: integer expression expected
Note: Using POSIX realtime
HAL: ERROR: thread 'slow' not found
lat.hal:3: addf failed
Note: Using POSIX realtime
===================
It has been this way for a bit.
Because on my pi, I have two threads, a 1ms thread for the linuxcnc
control stuff, and a 200 hz, 5 millisecond for the hand controls, it
would be informative if the period syntax also included the ability to
trace/measure this slower thread too but that implied syntax also fails
=============================
pi@rpi4:/media/pi/workspace $ latency-test base-period=1mS servo-
period=5mS
/usr/bin/latency-test: line 26: [: base-period=1mS: integer expression
expected
awk: cmd. line:1: BEGIN { printf "%.0f\n", (base-period=1mS); }
awk: cmd. line:1: ^ syntax error
awk: cmd. line:1: BEGIN { printf "%.0f\n", (base-period=1mS); }
awk: cmd. line:1: ^ syntax
error
/usr/bin/latency-test: line 26: [: servo-period=5mS: integer expression
expected
awk: cmd. line:1: BEGIN { printf "%.0f\n", (servo-period=5mS); }
awk: cmd. line:1: ^ syntax error
awk: cmd. line:1: BEGIN { printf "%.0f\n", (servo-period=5mS); }
awk: cmd. line:1: ^ syntax
error
/usr/bin/latency-test: line 72: [: : integer expression expected
/usr/bin/latency-test: line 73: [: : integer expression expected
/usr/bin/latency-test: line 31: [: : integer expression expected
/usr/bin/latency-test: line 32: [: : integer expression expected
/usr/bin/latency-test: line 33: [: : integer expression expected
/usr/bin/latency-test: line 34: [: : integer expression expected
/usr/bin/latency-test: line 31: [: : integer expression expected
/usr/bin/latency-test: line 32: [: : integer expression expected
/usr/bin/latency-test: line 33: [: : integer expression expected
/usr/bin/latency-test: line 34: [: : integer expression expected
/usr/bin/latency-test: line 77: [: -eq: unary operator expected
Note: Using POSIX realtime
HAL: ERROR: thread 'fast' not found
lat.hal:3: addf failed
Note: Using POSIX realtime
=============================
The --help shows both upper and lowercase s's being used but both work as
above.
The wintel versions also exit with exactly the same msg.
Thanks all.
Cheers, Gene Heskett.
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
