1HCL probing problem with ***video***

HighFreq

@dc42 @Phaedrux We scoped step output of G30 and it is way different if direct on a 6XD board or on a 1XD board driven by canbus.

The two step sould be exactly the same but they are not, when scoped on a 6XD it is clean and G30 works, if scoped on a 1XD right after the first touch there is a ton of rubbish.

Maybe is not rubbish and is there for a canbus timing reason but if devs don't help us out we can't go any further.

I am wondering how other users manage G30 using canbus connected boards, maybe nobody using 1HCL because it does not work at the moment.

I am very very surprised devs do not come back to us for a blocking problem like this and can't even reproduce it.

HighFreq

@dc42 @Phaedrux Please please please let us know if there is a solution to our problem, if you are working on it. We are at a dead point, don't know what else to try to have it working, no matter what we do 1HCL just refuse to behave decently on a G30 command and we do not know how to proceed.

Phaedrux

I'll see if DC42 can take a closer look again.

HighFreq

@phaedrux excuse me if i asked many times but the thing does not work, seeing if the dev can take a closer look is a bit less than what i expected since i have 4 x 1HCL useless on my machine and desperately seeking for help since 5 days ago.

The units DO NOT work on G30 no matter what we try.

Very sorry to hear this, i was expecting a bit more cohoperation on your side, since the boards do not work an ultimately i am spending my time to iron out a problem you have on your boards and it sounds like i am being an annoying problem to you.

I sent you all the files and tests you asked and you disapperead, did you take a look at the video? Why does it do that on a G30 using a 1HCL and works ok if i drive it direct with step and direction from the 6XD?

We went above and beyond what we should and took time to analyze it with scope (wich you said you would ahve done before disappereing) and posted our results, but having no answer whatsoever is very frustrating.

I am very surprised you can't replicate the problem since using an 1HCL board on a z axis and running a G30 command does the problem each time.

...the sound of silence....

Phaedrux

I'm sorry you're frustrated. You're not being ignored. As you've seen in your other thread on the Z brake we've even provided a customized firmware build for you to test. Things take time, thank you for your patience.

HighFreq

@phaedrux we appreciate, thank you.

will wait.

dc42

@highfreq said in 1HCL probing problem with ***video***:

In open loop it works it seems but between first and second touch it emits a beeping sound, maybe it would go back like in closed loop but being in open it skips steps and looks like it works?

I was thinking about this problem just now and came to the same conclusion myself, before I read your post. I was about to ask you whether there was an odd noise after the probe triggers when in open loop mode.

I will review the main board code tomorrow afternoon to work out what might be happening.

HighFreq

@dc42 great thanks.

If you need us to make any test just ask, we will be glad to help.

dc42

@highfreq please confirm that the video you posted uses this Z probe configuration that was in the config.g file you posted earlier:

M558 Z P5 K0 C"io1.in" H5 F20:20 T100 ; definizione probe Z

dc42

@HighFreq please can yo test whether the following works around the problem:

In your M584 command add a 5th Z motor assigned to a spare driver on the main board. I suggest you set the timing for that driver to T0:0:0:0 in a M569 command for that driver. You don't actually need to connect anything to that driver output.

HighFreq

@dc42 hello good morning.

Now the probing works, it doesn't jump anymore but endstops on the 4 phisical axis do not work anymore, probably because the fake axis configuration is not complete. If i remove the fake axis homing works as expected.

Our machine does z homing on top of the machine with 4 endstop switches.

HighFreq

@dc42 are you still going to get a look at it this afternoon?

T3P3Tony

@highfreq thanks for confirming that the work around fixed the problem. It gives an indication of what will need to be fixed in firmware so the work around is not needed.

HighFreq

@t3p3tony Just to make sure you understood, the workaround fixed a problem but created another so it is not usable, we are waiting for a firmware fix to be able to use the machine again.
Sometimes my english is not the best

jay_s_uk

@highfreq could you switch from using endstops to using the probe to home Z?

HighFreq

@jay_s_uk no, we can't, our z axis is made of 4 screw phisical axis so we need to home all of them individually. At least that is how the machine is designed to work so we would much prefer to use it that way.

jay_s_uk

@highfreq why? homez using the probe and then use the built in bed levelling to get them positioned correctly.
My voron has 4 z motors but none of them have endstops...

HighFreq

@jay_s_uk at least at the moment it is not possible, 1HCL has a little bug and sometimes one of the axis drops during power on, so it would not be possible do as you describe.

jay_s_uk

@highfreq one of mine always drops. i don't see why it wouldn't work unless your bed is so overly constrained that it can't move when one motor is out of sync with the others

HighFreq

@jay_s_uk we would prefer to have the bug solved and we want the machine to be able to home on the end stops because we need it in our layout.