And I also found the bug, that the CALIB_DATA_LENGTH value shouldn't be fixed to 46.
According to the spec sheet, the response data for calibration request (=write(fdc, "p", 1);) is described as text string like
32.800,32.815,32.835,1653.801,1634.816,1636.136
. So the length should be treated as variable (in my case, that was 43, and caused infinite waiting)
This would be more smarter way, compared to https://github.com/tork-a/dynpick_driver/pull/44 I think ...
And I also found the bug, that the
CALIB_DATA_LENGTHvalue shouldn't be fixed to 46. According to the spec sheet, the response data for calibration request (=write(fdc, "p", 1);) is described as text string like. So the length should be treated as variable (in my case, that was 43, and caused infinite waiting)