Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Tighter Hangprinter Compatibility #186
I updated the Hangprinter kinematics using the equation derived here:
The now enormous HangprinterKinematics::Configure method should probably be split up, so that FORMAT_STRING_LENGTH can come back down to 256.
One suggestion is to move 'R' (spoolRadii), 'G' (motorGearTeeth), 'H' (spoolGearTeeth), and 'J' (fullStepsPerRevolution) parameters to M92, as they could be used to calculate stepsPerMm on other types of kinematics as well.
Hi David! Tony has notified me that you're away. I hope you have a wonderful holiday. My own starts on Monday.
When you're back, don't hesitate to throw things around if I've gone against code norms, principles, or best practices. I have relatively little experience with C++ and object oriented code.
Posting my todo here in case you get curious when I'm away and unavailable:
The i2c usage in itself creates a wish-list
or maybe better
Gcodes that should be forwarded to external drivers via i2c:
The Mechaduino-side variables are called
The Hangprinter code (excluding the Mechaduino related code) has been tested and works. See Michael Delay's post here: https://www.facebook.com/groups/hangprinter/permalink/428191971024301/
Hi @dc42 I'm working on how to move the Hangprinters individual axes (G1 S1 and G1 S2).
I've noticed that they always call
With default anchor positions, the values
Both of the above problems leads to
Does RRF have a mechanism for storing and retrieving machine state, or should I go for trying to avoid touching counters by wrapping the lines where they are incremented? In Marlin I used
I will get around these problems of you don't have the time to help me, but your input would be very valuable. Thanks.
Hi @dc42 . I've done my first attempts at talking to the second ODrive via SERIAL_WIFI_DEVICE (the tx/rx on the EPS_COMMS header), but I'm not able to establish the connection.
So I read in the schematics and found a note: "J34 not populated in production boards".