Topics created by GizmotronX5000

Thanks for the tips! I was thinking I might do something like that. For the cylinder it would make sense to unwrap it and design a rectangular STL part and wrap it back onto the cylinder. Getting rid of the seam seems difficult though.

or should I being doing something similar to rotary delta with segmented motion? Is that a valid work around? I could change all axes to be linear axes, but use segmented motion instead in the constructor. Would I need to change anything else if I tried that?

I just tried this to see what might happen. I changed my kinematics class to:
MyKinematics::MyKinematics() : Kinematics(KinematicsType::myKinematics, DefaultSegmentsPerSecond, DefaultMinSegmentSize, false), numTowers(UsualNumTowers)
{
Init();
}

I took the definitions of the defaults from rotary delta kinematics, 100, and 0.2 respectively

I also changed GetMotionType to:
MotionType LinearDelta7DKinematics::GetMotionType(size_t axis) const
{
return MotionType::linear;
}

Things mostly work now, but the motion is not entirely smooth. It is definitely trying to approximate a straight line, but not quite right. As far as I can tell all of the moves do at least arrive in the correct spot.

@dc42 Awesome. I'll try that out and report back.

We are discussing it also over here:
https://forum.duet3d.com/topic/7269/duet-sometimes-really-slow-i2c-error-or/33
A suggestion is to put some resistors on the duex5 header, but I haven't tried it yet.

Yep, that was the problem. I knew it was going to be something simple I was forgetting. I added single quotes around the file names in the post-build step and it worked. Thanks for the help.

You are right, the code needs to be refactored to use the GetMotionType function.

@dc42 Thanks for looking into it! I'm happy to help test.

Unplugging wires and reseating them seems to have fixed it. Thanks!

Probably caused by an uninitialised variable.

Yes, it will be in the next 2.02beta release.