Topics created by Steve Lynch

@steve-lynch I have removed you from my Rude User and Hit lists. 🤣

Its cool, glad it helped you.

Laters,

Paul

@steve-lynch Sorry if this is going over old ground, but what does your sensor currently report? Send M591 D# when it is running.

Ironing, I think, extrudes tiny amounts of filament, so maybe there is some movement between the magnetic sensor and the extruder, so maybe these small movements are not being picked up?

Ian

@Steve-Lynch said in 3 point leveling not cutting it in the first pass.:

Anyhow, when I do a “true level”, , I have to throw a round bubble level in the bed to get it close before it’ll complete. Otherwise I get one corner that doesn’t trigger the BL touch.

Increase the dive height, that's the M558 H parameter.

Thanks man! I'm on 3.1, so I guess It'll just work then. 🙂

@bearer Well, thanks a million! I'm all upgraded now... I'm still looking.... I'll not stop trying, But I really appreciate you helping me out!

@Phaedrux

old values, and new values posted above.

DueX boards are currently being manufactured, so they should be available again soon.

That did it! Thanks man!

well, it is now! 🙂

I have escalated this issue to DC42. Hopefully he can chime in on what is happening.

https://forum.duet3d.com/topic/18100/dc42-please-read

After playing, I think I have figured it out... As long as the proper location of the pivot point is set in the config.g, then the Bed.G is ok to merely be "close enough".

Hey Danal, Thanks a ton! I'm back up... I had to step the wifi server version back, then I could connect again. Sometimes it's really nice to have a second set of eyes... The Ol' brain shuts off when I'm under pressure. I really sincerely appreciate you sparing me the obligatory lectures, and just saying "Dude! Do this!" I'll be sure to do my homework before hopping firmware versions again... Cheers!

@Steve-Lynch said in New Magnetic filament sensor from Filastruder misbehaving...:

What I was referring to was the fact that no calibration data at all was being reported.

You have to run part of a print from SD card to get calibration data. Manual extrusion isn't enough because it doesn't include retractions, which are important when calibrating.

@zapta said in Print timer horribly inaccurate:

@steve-lynch said in Print timer horribly inaccurate:

You were correct... about 30 minutes in, it had dropped down to 2 hours or so... thanks

The more you wait the more accurate it is.

When the 3 figures converge, it is accurate. Before then, the estimate based on filament usage is usually the most accurate, although on the first few layers it is unduly pessimistic because the first layer is usually printed more slowly. But the simulation gives an accurate time, unless you change the speed factor or the machine parameters during the print.

@steve-lynch said in When defining mesh bed leveling area, Which is the Reference?:

When defining the mesh bed leveling area, do you set the coordinates based on the position of the nozzle? or the position of the Probe?

The coordinates are the area you want the probe to go.

So like if my nozzle is at X40, and My probe is -40 offset in the config, do I need to go to X50 to make the probe probe at 10? or does the software automatically know where to go based on my nozzle's current position?

The software takes account of the Z probe offset when placing the print head for probing. So if your probing area starts at X10 then the firmware will place the nozzle at X50 to put the probe there.

aww shucks 😄

@steve-lynch Got me stumped at the moment. When you apply power the first thing it does is read config.g and carry out each command in sequence.

Ref the config-overide, no you don't need it. It's there to simulate writing to eeprom that some people like to do. Personally I hate it because sooner or later it will bite you by having configuration settings in two different places. So if you have a config.g with an M501 at the end of it, then once the firmware has read and acted on all the commands in config.g, it will go on to read and act on whatever is in config-override.g. So as log as there aren't any setting in the override file that don't also exist in config.g, then you can delete the override file and the M501 command that calls it.

Edit - we were typing at the same time so I didn't see your last comment. That's kind of crazy.

@steve-lynch

Do what DC said but ....you've defined the axes minima and maxima reversed for X and Y.

"; Axis Limits
M208 X300 Y300 Z0 S1 ; Set axis minima
M208 X0 Y0 Z400 S0 ; Set axis maxima
"

The minima should be 0 and the maxima 300 for X and Y (your Z is OK).

To clarify your questions. End stop high end means the far end of the axis, low end is min. That is defined by "nnn" after the axis name (0 means no end stop, 1 means at the low end of the axis, 2 means at the high end of the axis). But don't get this confused with "active high" and "active low". That's the "S" parameter which, if you are using simple switches will be either 1 or 0 depending on if you've wired them normally closed or normally open.

Yes, if the motors haven't been re-mapped using M584 then the default is that X is P0, Y is P1, Z is P2, the first extruder (E0) is P3 the second extruder (E1) is P4. (and yes, it can be confusing).

I don't see any M915 commands in any of the files you have posted. Have you tuned the M915 stall detection threshold? https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing#Section_Configuring_sensorless_homing