Topics created by Robocop

If you're confident in the position at startup you can trick the firmware into thinking the axis are homed by forcing a position with G92 X# Y# Z#

Or you could define a homing move using G1 H1 for the towers using an endstop that is purposely misconfigured to appear as already triggered at the start of the move by inverting the signal pin. If that makes sense?

@Robocop said in Command finished acknowledgement:

dc42 The M555 command seems to work, but behaves in a strange way. For example, if I send a G0 X10, it will reply with "Z_move_comp"..... and then "ok"..... why Z?

Because that's what nanoDLP expects.

Stepper motors are current driver, it is the work of the stepper-driver chip to chop the power-supply voltage so the current is at it adjusted value. When it is at it adjusted value the voltage on the stepper motor will be to at the proper value too.

The touch screen is resistive, which is better than capacitive when you need to be sure to hit the right button because you can use the tip of your fingernail oir a stylus to get extra precision. The main drawback of resistive touch panels is that they don't support multi-touch.

To use PanelDue in portrait mode, you would need to redesign the screen layouts. The low level display driver module can handle any screen orientation.

The code is open source, it's at https://github.com/dc42/panelDueFirmware. There is no additional documentation.