Posts made by ThePigSlayer

Thanks for the correction hendricks.

You can setup macros but you will also need to edit the retract and deploy system files as those are what m402 and m401 call.

Anyways, here is my bed.g file, which I call by just clicking the auto bed compensation button, or G32.

M557 X50:150 Y50:150 S25    ; Define grid

T0                          ; Select tool 0
G91 			    ; Relative mode   
G1 Z10 F150		    ; Make sure everything clears the bed                     

; ------------ Home Z ---------------------

G90                         ; Absolute mode
G1 X110.5 Y72 Z6 F4000      ; Home at center of bed, my offsets are X-10.5 and Y28
M401                        ; Deploy probe
G30                         ; Home Z-axis

;----------- Mesh Level ------------------

G29                         ; Start mesh level
M374                        ; Save results, but this might not be necessary 
M402                        ; Retract probe 

G1 X20 Y20 Z10 F3000        ; Dock position

You should really take a look at the 3030 Haribo. I used the basic frame design and from there did my own thing, and now I have a really good printer that I learnt so much from. I've become really confident with CAD design among other skills, but it did take a decent amount of time.

If you have the spare time, even an hour or less per day, I would highly recommend building a 3030 Haribo or at least using the design as a starting point. The MK2 stock frame is garbage anyways and the wait time is ridiculous.

I agree with Sniffle, using the bl touch for homing is great and if your bl touch works (just test deploy and retract) then there isnt really much of a reason to use a endstop over the probe for homing.

Also you can use m400 and m401 (double check) to retract and deploy the probe.

Last thing I am not sure if most people do it differently, but I use my bed.g file and I fill it with my mesh leveling code, well it homes first in the center and then does the mesh leveling. I can copy it if you want

that worked! thank you so much

do you know the reason why?

Hi,

So I have run out of ideas, I cant get M98 to work. Macro file name is simply "test", so I thought M98 Ptest.g would work, but nope, haven't gotten it or the many variations I have tried to work, including turning off "covert all gcodes to capitals". I also tried to specify the internal SD card with P0 but that didn't work either.

I also took out my microSD card, and reformatted it, made sure I had the correct folder structure (https://duet3d.com/wiki/SD_card_folder_structure)…. its still not working.

Does anyone have any ideas? I had it working fine previously, so I have no idea how to fix this.

Thanks in advance for any help!

Hi guys,

I am not sure if this is posted somewhere or common knowledge (searched but couldn't find anything), anyways I found a beautiful model of the Duet Wifi on grabcad, and I just wanted to let others know as it's been quite useful for a printer I'm designing.

Here's the link!

Im glad I could provide some useful information!

Prusa was trying to work together with someone from the original slic3r, but apparently that slowed development too much so he created his own branch. Recently the original slic3r has been getting updates, but I still found it was crashing too often, and the Prusa edition has some cool features like variable layer height and is updated more frequently.

dc42, I had the same problem, loved slic3r but the constant crashing led me to s3d. I tried the Prusa edition a few months ago, and I have been using it ever since (I use both slic3r and s3d now) without a single crash.

It's becoming embarrassing what s3d lacks, I really wish they would start releasing major updates again.

Toshi, you should probably decrease your trigger height. 3.15 is an awfully big trigger height, and since your dive height is only 5 (in m558), your z axis only goes up from 3.15 to 5mm, which is too short of a z-lift after each probe, which makes the probe report that it is already trigger before the travel move.

Your BL touch pin (the very tip) should be 2mm above the tip of your nozzle when retracted, which gives most people a trigger height of around 1.5mm. Your dive height of 5mm is normal, so either you need adjust your mount so you can lower your trigger height (by mounting the probe higher), or you miscalculated your trigger height. 3.15mm would be dangerously close to the height of the nozzle, and could catch during prints, so I think that it is more likely that you made a mistake when calculating the trigger height.

If I am printing something which has small holes that need to be close to the exact model dimension, I switch over to the Prusa edition of Slic3r.

Slic3r has a speed setting called "small perimeters" and basically any small hole (radius less than 6.5mm) will use whatever speed I set, which is usually 10-15mm/sec, and then I can keep my outline speed high and not have to ruin my print times, or find work arounds like above.

I like s3d, but I wouldn't pay 140 dollars for it. It lacks too many basic features, so I find myself having to switch between slicers every now and then.

I didn't use my microwave during the print, otherwise I would have connected the two. Also I believe it is the Duet because I don't ever have any issues with the connection dropping on other devices. I was gaming and my girlfriend was watching netflix during my last print and neither of us noticed any connectivity issues or lag. The printer is in the same room as me btw.

I will try to restart the router if it happens again, but hopefully it doesn't! I am about to start another 5-6 hour print so I will post if I experience another loss of connection.

Thanks for the help guys.

Thanks for the help dc42.

Unfortunately now its occurring almost every print. It just happened again 4 hours into a 6 hour print.

Any idea what could be causing this?

The print is coming off my PEI sheet so I need to cancel it. Is it safe to shut off power with the steppers moving? I remember reading that a sudden change in current to the motors can damage the board.

Hey guys,

I started up a pretty long print and I cant connect to the interface anymore. When I go into my router's setting my printer is not on the client list so I am assuming my only option is to restart the board, which I obviously can't do before the print is finished.

I also had this happen to me once before on older firmware. Has anyone else had this happen mid print? I just want to try and figure out if my router is causing the issue or the board. Or if anyone knows how to fix this without restarting the board let me know!

Thanks

maybe im blind but I dont see anything that mentions breaking a lead for 3.3v?

@Syko_Symatic:

So I will take the 5v and Gnd from the expansion port (pin 1 & 2) also taking the Servo pin from the same source (pin 8 (heater 3)).

Now when wiring the bltouch black and white wires into the DuetWifi Z- probe pins do they go to 3.3v and Gnd or Z- probe in and GND?

Also is it OK to crimp the resistor in with the pin connectors?

Z probe in and gnd. Be sure to use probe type 5 in M558. Also I dont see any problem crimping the resistor in the pin connector, as long as they are connected properly across. It might be easier to strip some insulation further up the wire though and put a bit of solder, but either or should work.

–---

And (In)Sanity here is my probing files, I have been using G30 S-1 to probe the single spot, the centre of my bed. For the G32 probe (auto bed compensation) my bed.g file contains this:

M98 Pdeployprobe.g
; Probe the bed at 5 points
G30 P0 X25 Y15 H0 Z-99999
G30 P1 X25 Y175 H0 Z-99999
G30 P2 X185 Y175 H0 Z-99999
G30 P3 X185 Y15 H0 Z-99999
G30 P4 X100 Y100 H0 Z-99999 S
M98 Pretractprobe.g

My mesh leveling macro is as follows:

G91
G1 Z6 F200
G90
M98 Pdeployprobe.g
G29 S2
M557 X20:180 Y20:180 S40
G29
M98 Pretractprobe.g

I have contacted Antclabs, but if anyone has any other suggestions please let me know! Thanks

I probed the same spot 20 times and I ended up getting a standard deviation of 0.054.

Hopefully we can get this solved, I am losing hope though lol.

EDIT: Thanks for the input dc42. I dropped the probing speed to 100. I had already tried that with bad results, but this time I got a standard deviation of 0.026.
I will lower the speed again.

I dropped the speed again to 50. Standard deviation is 0.032.

Any other ideas?

Yep my printer is pretty solid and prints consistently. I took it apart to make sure nothing got loose, tightened a few things, didn't help sadly. I am still getting deviations of 0.5mm maximum.

The grid is pretty random, I can upload the map if you want but I dont think it will help much.

I actually didnt get any docs with my BLTouch,, although it looked legit. I got it from spool3d.com. I modelled my own mount, and the distance from probe (retracted) to tip of nozzle is just 1.61mm. I read a distance of 2mm is optimal, so I don't think my mount height is causing any issues. Honestly at this point im thinking the probe is defective.

Thanks a lot for the help, I really appreciate it.

I remember I used to have a config override file but after updating a few times it seems to have disappeared. Is this a problem?

I tried a lower trigger value but haven't had any better results. I also decreased my Z acceleration as it was set pretty high. Also ironically shortly after I posted, I set up a macro for grid compensation. The probe points produce different values each time.

Any other suggestions? Thanks a lot for the help. I read your previous post about M401/2, but just forgot to change it, thanks though!

I have set my BL Touch up, but I am having a lot of repeatability issues that I am hoping someone could help me with. I have followed all the instructions in this thread as best as I could. I am using the resistor, plugging into the z probe pins, pin 1 and 2 on the expansion, and heater3 pin. I have tried changing the trigger value a bit which didnt do anything. All my connections seem fine as they are crimped and the resistor is soldered.

Here are the results (just the Z coordinate) from four 5-point auto bed compensations that I did in a row, without the heated bed or anything turned on.

[ 0.000] [-0.190] [0.425] [0.112] [0.158]
[ 0.082] [-0.170] [0.540] [0.503] [0.285]
[ 0.010] [-0.522] [0.780] [0.635] [0.293]
[-0.122] [-0.637] [0.322] [0.115] [0.197]

As you can see there is a big difference between each new probe sequence. Here are some relevant config files and my bed file.

; BL Touch
M558 P5 X0 Y0 Z1 H4 F450 T4000
G31 P25 X36 Y0 Z1.5

; Auto Bed Compensation
M561
M98 Pdeployprobe.g
; Probe the bed at 5 points
G30 P0 X15 Y15 H0 Z-99999
G30 P1 X15 Y175 H0 Z-99999
G30 P2 X185 Y175 H0 Z-99999
G30 P3 X185 Y15 H0 Z-99999
G30 P4 X100 Y100 H0 Z-99999 S
M98 Pretractprobe.g

Thanks in advance for any help.