Triangellab Euclid: Shutdown due to expected probe state to be stowed but is deployed (0)
Hello friends. I have installed the Euclid from Triangellab and can't get homing to work.
Every time I get this error message.
The cables are connected correctly to my TB EBB42.
The light on the Euclid is red. As soon as I press the trigger by hand, the light goes off and on.
I have checked the cables several times, they are connected correctly and work.
I therefore assume that everything is wired correctly.
However, I always get this error message.
My aim when homing was for the servo motor to extend the pick-up and the tool head to pick up the Euclid. And vice versa, of course.
Because it also produces errors when I already have the Euclid on it. (by hand 😉 )
I have attached my configuration files.
Please help, as I'm going crazy
24 Replies
I tried again and this came as result on the console:
just because the light goes on and off doesn't mean the switch is wired correctly. You could also have the switch logic inverted thus it thinks it is triggered when it isn't
Why have you copy pasted (and modified?) all of the stowable probe macros?
and why do you have a Euclid.cfg at all?
you only need this:
Put that in printer.cfg and delete Euclid.cfg.
Then manually put your euclid on the toolhead and verify that your wiring and probe pin config is correct by running
QUERY_ENDSTOPS. When the button is pressed and you run QUERY_ENDSTOPS it should report TRIGGERED, similarly when it's not pressed it should report open. When you take the euclid back off it should report TRIGGERED again.
Your pin config looks correct, so you're back to checking the wiring. Check your soldering too, if it's self assembled.After I triggered the Euclid manually it started working. And sometimes it happens again. I don't understand that.
Its deploying and stowing the probe perfectly. But sometimes it's getting this Error !
After I triggered the Euclid manually it started working. And sometimes it happens again. I don't understand that.That's a loose connection, bad wiring or solder job 🙂
Hi Mikl,
I bought it from TriAngelLabs and I checked the soldering if there is any cold soldering connection. But everything is pretty well. I suggest that the problem could accurse according the magnetism field or coding error, but I'm not sure.
I run euclid myself, it works fine 🙂
My intention was to make a carrier with brush. So I designed my own one and copied the script from Voron.
But my coordinated was different it was not working because the scripts in RatOS doesn't support a carrier with brush.
I was forced to modify everything to get it so fare working.
As I worth, the homing is working so fare. But sometimes I get the error.
I modified my design again, because or maybe during the pic-up of the probe the trigger gets in contact with the brush.
But now I have the problem that if i go in Z-Tilt It moves crazy routines.
I don't know what I'm doing wrong.
Maybe you could check and show me my fault in my scripts?
Here you see the videos in the German Support Ticket:
https://cdn.discordapp.com/attachments/1256582550181249055/1256582551468769402/IMG_1741.mov?ex=6681f3f2&is=6680a272&hm=a3c2c2bf727ab0daeee41d6d0ee23fe054cd804a3cdf9abc7b2bbae9c54794f4&
As I worth, the homing is working so fare. But sometimes I get the error.If you suspect your modifications, try the unmodified RatOS implementation and just set the coordinates for the dock. well that video shows x/y motion issue. It doesn't sound like stepper skipping, more like pulleys not being tightened. Your belts are incorrectly attached at the front of the toolhead, this will cause non-linear motion.
Yes, will shorten the belt after commissioning is finished successfully.
I suppose that the error accurse according the coordinates, which are placed in the config file.
I thing it's doing something wrong. Maybe coordinates are not handled absolutely and the movement is relative. But I'm not so fare to find the mistake.
No the video is showing a mechanical problem, if your grub screws on the motor pulley's were sufficiently tightened the motors would've likely skipped instead. If you're doing those moves at higher accels / speeds than you have current for, that's what happens. It can also be caused by binding in the motion system etc.
i'm guessing you didn't enable performance mode yet
So if you're doing high accel / velocity moves, this happens
I have enabled HPM at the configuration.
But I have reduced the speed in the script for deploying end stowing the probe. The speed is reduced for both at 50% of the regulare speed.
HPM?
reducing velocity isn't enough if you're running at super high accels for some reason and don't have enough power
High Performance Mode
We don't have such a thing. There's a "Performance Mode", i'm guess that's the one you're referring to?
Yes, sorry.🙈
Screen from my motor settings.
right this is plenty of torque for most things. So we're back to "check your pulleys" 🙂
I guess you are right. I will check the pulleys. Could it be also the power-supply?
Because I got several times communication lost.
I would assume those are unrelated
I can see a problem with the Left Pully. It's running uncircular. I'm working on that.
But I handled to get a bed mesh. Unfortunately I run in the next competition.
As you can see on the picture I have a pick in the middle of the left side. On all four corners I have a tolerance less than 0.1mm. But on the pick I have 0.35mm. I would like to as you first before I spend time and get it worst than before. Would would you do to get this completion solved?
As you can see on the picture I have a pick in the middle of the left side. On all four corners I have a tolerance less than 0.1mm. But on the pick I have 0.35mm. I would like to as you first before I spend time and get it worst than before. Would would you do to get this completion solved?
That looks like you tightened the left rail from both sides towards the middle. Loosen that rail, tighten from one end to the other and use very light torque (no more than 1Nm)