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

HighFreq

@dc42 thank you for your help, i am out of office now, will test everything tomorrow and will send you files.

dc42

@highfreq tomorrow is a public holiday in UK because of the Queen's funeral; however I may be online some of the time.

HighFreq

@dc42 I am trying updating firmware from web interface, it says i am running sbc and update only if adviced from developers i click yes but m115 command always shows old version.

Is there another way to update if running trough raspberry?

HighFreq

The video shows only one of the z axis during a G30 command, please turn on audio with phases description.

https://share.icloud.com/photos/06cU8ELrfs-zCSDhG1GmE0kaw

We are really at a loss now, we do not know where to look, if we configure our X axis as Z (it uses a different motor driver) probing works as expected with first touch than back than second touch than back. Using 1HCL it never works, not in open nor in closed loop. It is probably a configuration problem on our side but we do not know where to look.

One other thing, if we issue a G1 Z20 F200 G30 , he G30 is ignored, machine only execute the G1, if we issue two G1 commands on same line it executes them.

HighFreq

@dc42 I think we understood where the problem is. Between first and second touch of the probe the axis goes back to whee the G30 started.
As i understand after first touch should go back by the amount set in the dive, instead it goes back more or less where the g30 started, so if i start a g30 200mm above bed, when it touches the bed the first time it goes back to 200mm above and it starts the second touch.

Basicly i think there is a bug on how it handles backup between first ad second touch when in closed loop.

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?

JoergS5

This post is deleted!

HighFreq

@joergs5 would you mind let the thread follow what the real problem is and not a simple answer i gave to the developer that used that commands in his tests?

JoergS5

This post is deleted!

HighFreq

@dc42 can you give us any help please? we are pretty much at a loss.

thanks.

HighFreq

@dc42 the problem we have looks very much like

https://forum.duet3d.com/topic/27248/3-4-rc1-1xd-probe-problem-after-update

Is there any chance you reintroduced the bug in following releases?

HighFreq

@dc42 we tested the firmware in the thread i mentioned but it does exactly the same. It keeps jumping back after first touch.

We have been trying pretty much everything in the last days, a sign of life on your side would e nice

As it is now is unusable, i am wondering if it is us or simply nobody uses multi z axis on 1HCL yet.

HighFreq

@dc42 @Phaedrux we attached an external driver to drive one of the z axis, if we drive it directly from the 6XD using step and dir the axis works with no problems, if we drive the external driver using a 1XD (the 1XD gives step dir commands) trough canbus than the problem shows up again.

It looks like there is a problem when using canbus.

Please let us know if we are going to get any help/attention or not because the machine can't be operated at the moment and we need to know how to solve.

thank you very very much.

p.s. we can do whatever test needed to give you as much informations as possible.

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.