FSR Hardware Bed Leveling

[spiderx1]

It does not appear as if S3D supports hardware bed leveling with FSRs.
I inserted a G29 code in the scripts for start and it does complete that but it does not appear as if it is being used.
The head parks to the side and on print start lowers the bed then slides across the bed to the center then begins the print.
The head is touching the bed despite having a Z offset of .5.
I tried the bed leveling wizard but it starts off the build plate despite the correct size being in the program.
I have sent several request for tech support but get no answer. Yes I checked the spam.

[KeyboardWarrior]

It does not appear as if S3D supports hardware bed leveling with FSRs.
I inserted a G29 code in the scripts for start and it does complete that but it does not appear as if it is being used.
The head parks to the side and on print start lowers the bed then slides across the bed to the center then begins the print.
The head is touching the bed despite having a Z offset of .5.
I tried the bed leveling wizard but it starts off the build plate despite the correct size being in the program.
I have sent several request for tech support but get no answer. Yes I checked the spam.

Their support is pretty good about getting back to me when I've submitted tickets. It may be possible they haven't gotten your requests. Have you emailed [email protected] ? Also, what is the FSR? I'm not familiar with what printer that FSR would stand for?

[spiderx1]

Yep, emailed direct and thru support on website. Not a peep. FSR is a force sensor, as the tip touches the bed the FSR is triggered and the tip retracts, takes samples thru out the bed and inputs bed leveling info. Seems S3D wants u to adjust the bed vs accepting information to be used by the printer, even manual input using the paper method. Any info on bed leveling and correct G Code input on Z offset would be appreciated.

[KC_703]

FSR - Force Sensitive Resistor. Uses the nozzle to taps for bed autoleveling.

Have you checked that the G29 is configured properly in you controller firmware. What's the behavior when you manually send the G29 command under the "Communications" Tab in the Machine Control Panel?

[spiderx1]

The G29 seems to work fine, goes thru the motions but I am not happy with the results. So I just wanted to do a paper level.
The Leveling Wizard wants to adjust the be up and down. My bed does not adjust and it starts way off the bed, even when the size of the bed
has been reduced. Still no answer from tech, that I know of anyway.

[ndillane]

I implemented Auto bed levelling with an inductance sensor and had a lot of issues getting it working.
After G29 routine my printer started to print way off the bed.
This is how I sorted it
See here:
http://www.3dprintingforum.org/threads/ ... DRAG-K8200

In brief :
Run G29 through terminal.
Then type M114 to see where the printer thinks it is - you may see what I saw which is a difference between head is Versus where it thinks it is.
I simply added this after G29 in start G-code
G92 X0 Y200 ; ***** ADDED TO TELL HEAD WHERE IT ACTUALLY IS *****
i.e. I told the head where it actually was versus where it thought it was
This fixed my issue
Hope it helps
tks
Noel

[DaveDownUnder]

Hi All

Thought I would work through the Forum first before going to support.

I have a similar problem with my Haldron OrdBot. It uses the basic microswitch on a servo arm to do the sensing for bed levelling, and sins starting to use S3D I have not been able to make it function correctly. th G29 command works fine when I use 2 other brands of freeware for my slicing, but for some reason when S3D is in control it gets totally ignored and had resulted in many failed prints so far .

Suggestions / ideas greatly accepted as I want to get this functioning before I start using S3D with my new Delta printer

[CompoundCarl]

You just need to have the proper commands in your starting script. That's all. There's no other magic. The software just sends those commands to the printer.

So if it's working in one software, but not in another, then you must have different commands in the starting script. I would double-check that.