Ok, that is an explanation I can relate to, thank you for the clarity of your reply.
That is what I will do next, even though their stance in the past to others who tried to get somewhere has been less then supportive, which is unfortunate.
I always thank those who contribute to some level of understanding of what is going on, that is why I mention the facts, perceived wrongly or not, by myself, and stay as open as possible while focussing on the issue rather than on the person. This way I can learn something new, like others, and collectively find the way out. Unfortunately if the problem is random or unpredictable, it becomes hard to accept certain conclusions, for the simple fact the realworld experience does not show the explained reason every time.
But if my wording was too factual, I apologise to all on the receiving end.
Thank you hcet14, but which folk did you mean? This seems a long complicated thread about the subject matter of my error but I cannot find anybody who I might contact for it. As far as I understand this is the developpers talking to eachother about the codes but I think I should contact Cartographer who sold me my scanner. This is what is my next step even though I am not holding my breath. One question to all, does klipper accept the beacon scanner without these issues???
Thank you, I think I understood and that is what I will do next.
Thank you, I had to E-stop it everytime the error happenend because the system does not abort itself. Since after the error the toolhead thinks it is where the code sent it to, but physically is somewhere totally different, it will joyfully ram itself against the frame with the next move. So this is why you can see the webhooks request everywhere.
Sorry if my previous rebuttal sounded offish, it was totally not the intention. I read what people suggest or conclude and compare it to what I see is happenening. From my point of view, with almost no knowledge of the code behind it, I saw inconsistencies. As sineos explained this could be exactly the result of what is described in
I read this section many times now, also in the past, and I have to say it is slowly cementing itself in my head that it is always better to stay away from aftermarket hardware that do not comply with this. Maybe we should compile such a list for people so in the future they can decide what they want to buy. (Maybe it already exists but I did not know?) I did not know the Cartographer would give me such headaches. Maybe a Beacon would be better, I will investigate this.
Anyway your contributions are always appreciated, like all other’s. Unfortunately this problem is not so easy to eradicate and might never end in a nice proposition.