STM32 with reprap firmware and driver select

[Sahiru Hettiarachchi]

Hi,

As my pnp has 9 axes I moved to STM32 using rep-rap firmware.

I am using teamgloomy.github.io

But I cannot home the machine from openpnp. I added M564 S0 H0 so I can move without homing. It worked but still I cannot home. When I press home it give me this error "Serial://com6 timeout waiting  for response to G28;Home all axes" Any ideas?

I found these two articles
https://github.com/openpnp/openpnp/wiki/Duet3D-Openpnp-Example
https://duet3d.dozuki.com/Wiki/Using_RepRapFirmware_with_OpenPnP

Currently I am using the config file generated from the configurator at teamgloomy.github.io/Configurator
But those two links show a different type of approach. For each axis do I need separate homez.g , homea.g , homeb.g , homeu.g files?

Also should I use the Gcodedriver or the GcodeAsyncDriver?

For now I have been able to successfully connect to openPNP, Connect to DWC and  clone Y axis to E0 because I have two motors for Y axis.

Other than that I am very stuck

[Sahiru Hettiarachchi]

Also openpnp does not seem to like the firmware. I think this would be fine as the axes moved and openpnp works even with generic gcode drivers. I initially selected the "Assume generic gcode driver..(as I remember it was like this)" but it detected this.

[mark maker]

Thanks for reporting this.

I realized the code currently checks for "Duet" instead of "RepRapFirmware" in the firmware name. For reference, the Duet reports like this:

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC 

I chose "Duet" due to my confusion with the "other" RepRap, which I think has its own firmware somewhere:

https://reprap.org/wiki/RepRap

I'm still unsure, if firmware tag "RepRapFirmware" actually positively identifying the modern https://github.com/Duet3D/RepRapFirmware firmware (and derived), but I will change it.

In the meantime, generic G-code should be mostly fine, there is just an axis config check that is extra. Please send the machine.xml and a log at trace level.

_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/c2937bb1-a432-4526-8acf-9a1fa574581bn%40googlegroups.com.

[dc42]

Yes it does; although you might also with to check that the FIRMWARE_VERSION starts with "3." to avoid possible compatibility issues with older versions.

[mark maker]

> Also openpnp does not seem to like the firmware.

This is now addressed in the testing version (allow some minutes to deploy).

Some details here:

https://github.com/openpnp/openpnp/pull/1515

_Mark

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/84ac891e-eae2-e069-7c52-cb831ac47b88%40makr.zone.

[Sahiru Hettiarachchi]

Hi Mark,

Thank you for the consideration.

For the axes not working I could figure it out. It was wrong axis letters in the config.g file in the controller. Now all the axes are moving and I am having a custom PCB to tidy up the wire mess.

Thanks