Latest Marlin bugfix-1.1.x branch for PI3 Pro B

[mediaklan]

Forget it, my bad, I put the conf on an untirely unrelated wrong folder ! Verifying the compil works as it should, now ready to some mods...
The question remains though : was it made with the GT2560 board in mind ? Am i gonna have some problem with the ramps 1.4 ?

[NiklasO]

Yes, it's for GT2560.
Confirm the pins in the pins_RAMPS.h, pins_RAMPS_13.h or pins_RAMPS_OLD.h.
Change

Code: Select all

#ifndef MOTHERBOARD
  #define MOTHERBOARD BOARD_ULTIMAKER
#endif

to fit your setup.

[mediaklan]

Ah I was unsure about the pins, I'm gonna check with my working config. Thanks a lot NiklasO !
PS : last thing before I stop annoying you. There is a very interesting line about FIX_MOUNTED_PROBE, which I'm planning to use (I own both an inductive sensor and the BLTouch, but this one is gonna be a little tough to mount on my extruder right now). On the configuration.h, I comment BLTouch and uncomment FIX_MOUNTED_PROBE and that's it for the configuration.h right ? (I already know which pin and port to use in pins.h for my sensor).
This topic should be a sticky one. It's a gem.

[NiklasO]

Yes, and look at Z_ENDSTOP_SERVO_NR, Z_SERVO_ANGLES and the "R/C SERVO support" part towards the end of Configuration.h

[mediaklan]

I've got everything - almost - done with Marlin RCBugFix, but I'm dealing with a lot of strange behaviors. One of them concern the lcd menu : there's a big time gap, a delay, between the lcd menu and the response from the printer. But I can't really determine where it comes from since a lot of settings have moved to another files. Anyone experiencing this on Marlin RCBugFix ?

[NiklasO]

I've got everything - almost - done with Marlin RCBugFix, but I'm dealing with a lot of strange behaviors. One of them concern the lcd menu : there's a big time gap, a delay, between the lcd menu and the response from the printer. But I can't really determine where it comes from since a lot of settings have moved to another files. Anyone experiencing this on Marlin RCBugFix ?

Do you use the standard "reprap discount"-one? The full graphic version is quite slow but the developers works on that.
I have not had any problems with the stadard LCD-type except one bug present right now in the RCBugFix-branch. All menu items disappears if hotend > 0 degrees. It could be fixed by now. https://github.com/MarlinFirmware/Marlin/issues/5616

[mediaklan]

Yes, the standard "reprap discount"-one. I think I didn't need to change that since I'm guessing we have the same LCD. As it is, it's not really the LCD menu which has an issue, it's the very slow response from the printer. There's a 2 seconds lag for each command I turn on from the LCD Menu (which can rapidly turn into mistakes and errors). No such problem with the old firmware : the printer reacts immediatly.

[NiklasO]

Yes, the standard "reprap discount"-one. I think I didn't need to change that since I'm guessing we have the same LCD. As it is, it's not really the LCD menu which has an issue, it's the very slow response from the printer. There's a 2 seconds lag for each command I turn on from the LCD Menu (which can rapidly turn into mistakes and errors). No such problem with the old firmware : the printer reacts immediatly.

No, you don't need to change it. I have personally changed to the full graphic one but my config is for the standard 2004 lcd.
I have tried with the standard lcd and I can't reproduce your problem. Sorry!

[mediaklan]

Still, thanks for your kind answer NiklasO. For now, I've given up the latest Marlin (too many issues) and switched back to the good old stable marlin 1.0.2 (or something like that). And with it, at least I have some results : I am now able to get the 3DTouch to answer M280 commands (using CuteCom in Linux). There's one thing that drove me entirely crazy for the past few days : with the ramps 1.4, there is sometimes not enough amperage to get the 3DTouch working. So you need to put a jumper on the board (which I didn't have at the time) to ensure sufficient power before trying anything else. I've spent HOURS trying to determine WHY the 3DTouch was lacking power, so here's the picture if anyone with a ramps 1.4 is getting nervous :
. . . . .

. . . . .
Now I need to understand how the 3DTouch is supposed to work because right now, it's the printer that is getting crazy each time I'm homing or trying G29. Needless to say I wouldn't have been that close to get this whole painful thing to work without your help, NiklasO. Thanks. Again ^^.

[Tizzy]

First off, much thanks for all efforts, well appreciated!!

Query: will this firmware and the latest config.h work as-is for the dual extruder on the pro-C as well? I'm relatively new to this and have been (and am still) struggling a bit to find the correct offsets for both the extruders so they can work in unison, so am a little worried about replacing my working firmware and adding the 3dtouch when it seems I'm making progress with the stock firmware (without the 3dtouch though so need to get it fixed anyways)...