Setup issues

32 views
Skip to first unread message

Henrik Olsson

unread,
Sep 14, 2025, 9:51:20 PM (6 days ago) Sep 14
to OpenPnP
Hello,
After years and years on the back-burner I'm in the process of rebuilding my machine. A lot has happened with openPnP since I last used it - very cool.

* Fresh install of OpenPnP v2.4
* Smoothieboard updated with Marks firmware from Feb.15 2021
* GCodeAsyncDriver
* AdvancedMotionPlanner

Trying to follow instructions here:

together with the Issues and Solutions system but they contradict each other so it's a little bit confusing. As an example, instructions above says to set the GET_POSITION_COMMAND to M114 but Issues and Solutions says to delete it - which is it?

I can connect/enable and I can home the machine but I can't for the life of me get it to jog with the jog buttons in OpenPnP. The DROs in OpenPnP changes but the machine doesn't move. Using the G-code console I can move it, no problems.

I have enabled the Log G-code option and I can see in those logs that it does not produce and G-code for actually moving the machine. I can't figure out why.

As per instructions on Marks wiki (linked above) I have the MOVE_TO_COMMAND set to:
{Acceleration:M204 S%.2f} G1 {X:X%.4f} {Y:Y%.4f} {Z:Z%.4f} {A:A%.4f}{B:B%.4f} {FeedRate:F%.2f} ; move to target

But instead of moving it produces M-command to actuate the top light. Running Issues and Solutions says the above command is obsolete and wants me to delete it.

I'm confused :-)

Any pointers? Thanks!

Henrik Olsson

unread,
Sep 15, 2025, 1:32:18 PM (5 days ago) Sep 15
to OpenPnP
Allright, slightly embarressed I write back to let you know I figured it out.
The Axes did not have a driver assigned to them duh... I must have not pressed Apply on each axis when assigning the driver yesterday. Now I have motion and can continue with the setup.

I'm sure I'll be back with other questions as I get further into it. Thanks!

/Henrik.

Reply all
Reply to author
Forward
0 new messages