Bug with the firmware make for MKS Robin Pro aka STM32F103ZET6

Basic Information:

Printer Model: JG Maker Artist-D
MCU / Printerboard: MKS Robin Pro
klippy.log (721.8 KB)
In the event the printer.cfg helps:
printer.cfg (9.1 KB)

Describe your issue:

In an effort to not share everything all over again, here is the link to my Discord post. It also has a link to the #mks-boards channel for the same issue someone else is having as well with the firmware for another MKS Robin E3 STM32F103ZET6.

The jest is that I made my firmware.bin "Exactly like shown on this site Klipper-for-MKS-Boards/MKS Robin Pro V1.x/Image/MKS Robin Pro V1 setting.png at main · makerbase-mks/Klipper-for-MKS-Boards · GitHub, and my firmware would not work.

It would act like it did, but it would not work. I downloaded their firmware that was made using the exact same menuconfig settings and that *.bin file worked. So I am going to suggest their might be a bug with the make flash for MKS STM32F103.

I made firmware for my BTT SKR Pro v1.2, EBB42, and it worked without issue.

When I could not figure it out for the first few hours I decided to reimage my pi and start over from scratch, just incase. It still had issues.

All I have to do is configure my IDEX, and I should be up and running. The display came alive once klipper was able to connect to it.

I could find no other topics on this subject. If you fix a bug, or need me to test anything for you, please do not hesitate to ask.

Thank you,
/retnel

I’m not sure what you are reporting here:

  1. The klippy.log shows that your firmware is up and running and Klipper host is able to connect
  2. The log shows a `MCU ‘mcu’ shutdown: ADC out of range error

Right, what I am reporting is in the link to the discord post. make menuconfig and make flash do not produce a bin file that does not work. I downloaded a preconfigured bin file from the site listed and it worked, the ADC issue was resolved due to a misconfiguration of a pin only on extruder.

The “issue” is the firmware building. Because I can not build a working bin file, I have to use what worked from: Klipper-for-MKS-Boards/MKS Robin Pro V1.x at main · makerbase-mks/Klipper-for-MKS-Boards · GitHub , as previously listed.

Since I was not able to make the firmware myself, I could not configure the GPIO at startup to !PA14 which I understand is the pin for klipper to send the reset to when restarting firmware. I have to reset the firmware, and also press the reset button on the display or I will get mcu connection errors.

Additionally; I was configuring for [dual_carriage]. No matter what I do neither X will move. The enable pins work, I assume the direction pins work, but they do not step at all. I can hook up my O-Scope to monitor the pins if need be. For a sanity check I removed the [dual_carriage] and configured for one x. It still engages, but does not move.

For another sanity check I swapped the stepper_y with stepper_x and the Y stage moves when it is configured in stepper_x, but y does not move configured under the stepper_x.

For another sanity check I enabled [homing_override] after I swapped the stepper_x and stepper_y back. I then sent G28 Y0 Z0 and Y homed, then Z homed with the bltouch as configured.

So I have verified that it only has issues in X. For the MKS Robin Pro in IDEX, stepper_x is X on the board, and dual_carriage is E2 on the board. I have a couple of these all running marlin and I used pins_MKS_ROBIN_PRO.h from Marlin 2.1.2.1 to configure correctly.

For my last sanity check, I put Marlin back on the board and homing works without issue. So at this point I do not know if it is an issue with the firmware I had to download, or if there is some configuration blackhole that is not producing an error until I try to home and get “7:42 AM
No trigger on x after full movement”

As motioned, I removed all traces of dual_carriage, and used X pins, and E2 pins, neither move at all, but they both enable the stepper motors. So I know it is not the hardware.

For all I know I am fighting a different issue with the firmware I downloaded? I did not ask for help, or assume a bug until I did my due diligence. Something is a miss. I am only having this issue with the MKS Robin Pro board. I think I have a decent handle on this configuring stuff.

So please read what I wrote. I am not just turning buttons and yelling. Something is not right.

Most recent klippy.log
klippy.log (5.1 MB)

minimalist printer.cfg
printer (1).cfg (8.9 KB)

If you stopped at the klippy.log, then you did not have the means to understand what I was reporting.

From original post:
" Describe your issue:

In an effort to not share everything all over again, here is the link to my Discord post. It also has a link to the #mks-boards channel for the same issue someone else is having as well with the firmware for another MKS Robin E3 STM32F103ZET6."

Thank you for your help with the real issue as described,
/retnel

Did you follow:

I overlooked that, I will try it again that way and let you know what happend.

Thank you,
/retnel

Your a wizard @Sineos.

Thank you, that will be hours in lessons not soon forgotten. Not a big deal, I learned sooo much along the way.

The stepper_x issue persist. Not sure why.

Should the motherboard also reboot when I do a firmware restart? I added the inverted !PA14 J-Tag pin as I read on the net. Just becasue I read it, and others said it work, does not mean it is why.

Klipper reports: ERROR

Failed automated reset of MCU ‘mcu’
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer

If I trigger with finger.

image

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.