Hi Matt
you got some unexpected sequences in the log.
Please send the machine.xml
_Mark
--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/34e3b1e6-5a89-412d-8e9d-0944748f678dn%40googlegroups.com.
Hi Matt
you got a Smoothie firmware that is not in Grbl mode. This is the historical default for OpenPnP, i.e. OK.
OpenPnP actually supports both modes, which it detects by the X-GRBL_MODE variable in the firmware detection, yours is at 0 =off:
But you seem tho have manually set a HOME_COMMAND
to $H which is the
Grbl mode dialect. Maybe that was inherited from when you had a
different firmware.
OpenPnP Issues & Solutions will only propose a HOME_COMMAND if it is empty, because those tend to be highly machine dependent. Set it to empty, press Apply:
Then use Issues & Solutions to propose the proper HOME_COMMAND. Accept it:
I'm not entirely sure this will already solve the reported
problem. But let's take it one step at a time.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/31d6be8d-15b9-41f5-977a-99fa8d356081n%40googlegroups.com.
Hi Matt
the only thing that remains strange are these:
You've set your driver to Full 3rd Order Control. Unfortunately,
Smoothie does not provide that. you probably meant
Simulated3rdOrderControl:
But I cannot see how this would explain the error. Still: please
set to ModeratedConstantAcceleration for now.
Also strange is this sequence:
2022-09-12 16:20:18.768
GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] <<
Smoothie
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.769 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.770 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.770 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:18.770 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:20:21.769 GcodeDriver DEBUG: [serial://ttyACM0]
>> G21 ; Set millimeters mode, 10000
A ton of "ok"s`? But why? It sort of points to a serial comm
problem.
However, the sequence in the log does not point to a comm
problem, the M400 is confirmed.
2022-09-12 16:31:05.599 Scripting TRACE:
Scripting.on Camera.BeforeSettle
2022-09-12 16:31:05.599 GcodeDriver DEBUG: [serial://ttyACM0]
>> M400 ; Wait for moves to complete before returning,
10000
2022-09-12 16:31:05.600 GcodeDriver$ReaderThread TRACE:
[serial://ttyACM0] << ok
2022-09-12 16:31:05.600 GcodeDriver TRACE: [serial://ttyACM0]
confirmed M400
2022-09-12 16:31:15.600 Scripting TRACE: Scripting.on
Camera.AfterSettle
2022-09-12 16:31:15.601 MessageBoxes DEBUG: Error:
java.lang.Exception: Timed out waiting for move to complete.
The fixing of the homing command was all done in one session. I'm
not sure how, but maybe there was still some "strangeness"
lingering from using $H in the same session.
Please exit OpenPnP, reset/unpower Smoothie, and retry.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/253d1414-449b-4d56-aa14-ec1b215af811n%40googlegroups.com.