@dc42 I will re-test, but I did reboot after changing the parameter each time. I also increased T, which did make a difference (max speed was even lower).
I reduced the parameter for X and Y only, since the Z-Axis seemed to be ok.
Update: With both axes set to T1, the the max speed was still limited. Compared to previous tests using just a square with only x or y movement at any given time, this was a figure 8. M122 now appears to show incomplete moves:
=== Platform ===
Last reset 00:03:56 ago, cause: software
Last software reset at 2018-10-19 14:48, reason: User, spinning module GCodes, available RAM 6816 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 37.9, current 38.2, max 38.7
Supply voltage: min 11.8, current 11.9, max 12.1, under voltage events: 0, over voltage events: 0
Driver 0: open-load-A open-load-B, SG min/max 0/14
Driver 1: open-load-A open-load-B, SG min/max 0/12
Driver 2: standstill, SG min/max not available
Driver 3: ok, SG min/max 0/395
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest loop: 646.41ms; fastest: 0.08ms
=== Move ===
Hiccups: 1243034, StepErrors: 0, LaErrors: 0, FreeDm: 174, MinFreeDm 150, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 1237, completed moves: 1215
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Not sure where to go from here. Our servo drive manual states that the drives are updated at a rate of 1kHz, but there is no mention of a microsteps/sec limit . The Rep-Rap wiki shows an "extended" configuration for the parameter T, like: Taa:bb:cc:dd in which 'minimum step pulse' and 'minimum step interval' can be configured. Is this a way forward?
Thanks!