Recent Posts

Pages: [1] 2 3 ... 10
1
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.5
« Last post by inaudible101 on June 01, 2020, 09:35:48 PM »
Superb, glad you sorted it.  Yes, for others you can use the M851 Xxx Yxx Zxx to set the offset for the BLTouch and then do a M500 to save it to the eeprom, then a M503 to check it's been saved.

So....
M851 X20 Y-3 Z-1.52   
M500

I know you've already done this, but posted for others :-)

Good news and happy printing....

Steve

Hi!
I've been a long time lurker. I've been using the last few iterations of your firmware. I just replaced my cooling solution with a new option and used the commands you provided above, but when I use the touch screen to set the z offset it seems to still use your old x and y offsets for the bltouch. I have tried restarting the printer and clearing the eeprom and resetting the x y but I have the same results. I can confirm that the x and y are updated to the values I need using your command above or M851.

Thank you and I look forward to the next update!
2
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.5
« Last post by SilentSnake on June 01, 2020, 08:48:40 AM »
I found a serious bug! Try following:
- Switch on Printer
- Tools --> Level
- Select Level Point "One"
- Go back in Menu an proceed to Submenu "Move"
- Move Nozzle 0.1mm up
From now on, be careful:
- Go back to Level and choose Point "Two"

Result: The printer does not go to origin, but crashes over the right end of the x axis and the pushes the nozzel directly into the bed. Full force, the rattles and makes a horrible noise ...
3
Pretend Prusa Firmware / Re: Artillery X1 v4 TFT seems to not be communicating
« Last post by zaf on May 31, 2020, 09:42:10 PM »
I've got the opposite problem, I can work the printer from the TFT, but USB is not working. Octoprint doesn't detect any serial devices showing up when I plug it in. Any ideas what could be going wrong?
4
Pretend Prusa Firmware / Original MK3s with Marlin FW possible ?
« Last post by Manux on May 30, 2020, 03:01:46 PM »
Hi

I want to flash marlin to my original MK3s.

The reason is: I want to use a volcano hotend and i installed it successfully. However the pinda does not find the bed. And it a hit and miss sometimes it gets found. Sometimes it does not get found. This happens without changing anything on the printer. So basicly ist ist just unreliable.... I installed a mod so i dont have to mess with the frimware and can use the whole space of the printer. So its not that i did forget to change the fw...

So i want to flash marlin and basicly just use it as it is. without plugging anything in or out. As marlin can use pinda sensors this should be possible i think....

However i understand that it is not that easy and i probably have to modify firmware and so on. My main hope is that marlin will be easier to configure than sifting throough the prusa source (What i do right now and i understand very little...).

My wish would be that the pinda can be used with marlin and it just works for the most part. I know that some things like filament sensors will probaly not work but i am prepared to sacrifice that.

So basicly im asking, can i just run marlin 2.0.x on the einsy with the prusa mk3s and change very little on the wireing if possible nothing and just get the pinda work reliably ?

What do i have to modify in Marlin 2.0 to get it running ?

Backround:

It is unreliable with the bed find because i installed a mod for the volcano wich puts the bed lower so to spreak because the rods go higher and there is a Contant in the source code who defines how far the pinda will search for the bed if it is not in that range the printer will kill itself and even after i changed that part of the firmware it does not work reliably.

To make it work reliably it should just: "Go down till endstop is found" while now it is: "Go down to find endstop but max 1mm or 10mm if position is not known"

Even after i changed the code the finding of the pinda is not reliable.

If we could fix that code it would also work but i have low hopes on that.

So basicly i want to try out marlin with pinda and then if that does not work i want to install a bl touch and make it work with mk3s and marlin. This will need support from the community here because im no coder by trade and some things are not clear all the way.

Here are the relevant code snippets:

Code: [Select]
// Go down until endstop is hit
const float Z_CALIBRATION_THRESHOLD = 40.f;
if (!find_bed_induction_sensor_point_z((has_z && mesh_point > 0) ? z0 - Z_CALIBRATION_THRESHOLD : -45.f, nProbeRetry)) { //if we have data from z calibration max allowed difference is 1mm for each point, if we dont have data max difference is 10mm from initial point
printf_P(_T(MSG_BED_LEVELING_FAILED_POINT_LOW));
break;
}
if (init_z_bckp - current_position[Z_AXIS] < 0.1f) { //broken cable or initial Z coordinate too low. Go to MESH_HOME_Z_SEARCH and repeat last step (z-probe) again to distinguish between these two cases.
printf_P(PSTR("Another attempt! Current Z position: %f\n"), current_position[Z_AXIS]);
current_position[Z_AXIS] = MESH_HOME_Z_SEARCH;
plan_buffer_line_curposXYZE(Z_LIFT_FEEDRATE, active_extruder);
st_synchronize();

if (!find_bed_induction_sensor_point_z((has_z && mesh_point > 0) ? z0 - Z_CALIBRATION_THRESHOLD : -45.f, nProbeRetry)) { //if we have data from z calibration max allowed difference is 1mm for each point, if we dont have data max difference is 10mm from initial point
printf_P(_T(MSG_BED_LEVELING_FAILED_POINT_LOW));
break;
}
if (MESH_HOME_Z_SEARCH - current_position[Z_AXIS] < 0.1f) {
printf_P(PSTR("Bed leveling failed. Sensor disconnected or cable broken.\n"));
break;
}
}
if (has_z && fabs(z0 - current_position[Z_AXIS]) > Z_CALIBRATION_THRESHOLD) { //if we have data from z calibration, max. allowed difference is 1mm for each point
printf_P(PSTR("Bed leveling failed. Sensor triggered too high.\n"));
break;
}

40.f; was originally 1.f
-45.f was originally -10.f

Here is the link for the volcano mod: https://www.thingiverse.com/thing:2989361

Ok i hope i made my case and hope for a lot of contributions :-)

5
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.5
« Last post by spuds1 on May 30, 2020, 01:07:48 PM »
Hey. Just wanted to say this is a fantastic mod that keeps the look of the printer stock. Just one issue for me. I use octoprint to stream gcode. Is there a way to get babysteps on the touch screen while using octoprint?
6
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.5
« Last post by CJS on May 30, 2020, 11:47:46 AM »
And it works - fantastic - thanks a lot  ;D

Please one remark: can you added in one of  the next versions the PLA-Preheating-Function in "more" - there is space for one more icon  ::)  and I miss it very much ...

Thanks for all - you explained it in such a way, that an old man whose mother tongue is not english understood and implemented it - respect!
7
Pretend Prusa Firmware / Re: Wagster Mod 1.5 for Artillery Genius
« Last post by linsenpago on May 27, 2020, 10:30:53 AM »
I now printing the first object with the new firmware and with well tuned settings out of cura... and it turns out awful.. :-(

Did i miss something or is there so much different to the stock firmware?
8
Pretend Prusa Firmware / Wagster Mod 1.5 for Artillery Genius
« Last post by linsenpago on May 27, 2020, 09:42:49 AM »
Hi!

I installed today your firmware out of version 1.5 so that i can use my BLtouch.

But now i have a lot of busy entries on the terminal of octoprint... it looks like this:

Recv:  T:215.36 /220.00 B:79.54 /80.00 @:52 B@:9 W:9
Recv: echo:busy: processing
Recv:  T:214.69 /220.00 B:79.56 /80.00 @:58 B@:8 W:9
Recv:  T:214.53 /220.00 B:79.47 /80.00 @:59 B@:13
Recv:  T:214.53 /220.00 B:79.47 /80.00 @:59 B@:13 W:9
Recv: echo:busy: processing
Recv:  T:214.61 /220.00 B:79.56 /80.00 @:57 B@:9 W:9
Recv:  T:214.38 /220.00 B:79.55 /80.00 @:60 B@:10
Recv:  T:214.38 /220.00 B:79.55 /80.00 @:60 B@:10 W:9
Recv: echo:busy: processing
Recv:  T:214.53 /220.00 B:79.55 /80.00 @:59 B@:11 W:9
Recv:  T:215.00 /220.00 B:79.58 /80.00 @:55 B@:10
Recv:  T:215.00 /220.00 B:79.58 /80.00 @:55 B@:10 W:9
Recv: echo:busy: processing
Recv:  T:215.68 /220.00 B:79.62 /80.00 @:50 B@:9 W:9


do you have any ideas why this is now happening?

I also see that the movement of the printhead is not so smooth as before... it stutters...

Any ideas?

greetings,
Alexander
9
Pretend Prusa Firmware / Re: What does the BLTouch Reset Really do?
« Last post by CdRsKuLL on May 27, 2020, 02:50:30 AM »
Strangely enough I have to reset the probe every once and a while or on a new G28 it will go halfway down and then pretend it makes contact then stop. No clue how it gets confused but the reset concept is what had me put it into custom commands (octoprint) so I could tap it as a safety measure before a print. I dunno if its dumbos magic feather or not at this point but.. lol!

Well if it works :-) it's good enough,  handy to know also for others.   thanks for posting.
10
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.5
« Last post by BaronVonPrints on May 26, 2020, 08:25:10 PM »
No that's correct.  It only shows open when the probe is down.  When the probe is retracted it shows triggers. :-)  It drops the probe always for homing, once homed it doesn't need it again and remains up.



Wondeful! Thank you so much for the help!!!!
Pages: [1] 2 3 ... 10