Scanning Sensor Mount for a Roto with Toolboard

[DeadNewbie]

I must be going mad, the Roto product page has a image with a mount for the scanning sensor.

is there an STL already available, just checked the roto github, and just the simple spacer stl is on there?

Please can someone point me in the right direction. as my Roto and Toolboard arrive in a few days.

Thanks.

[j.pickens]

@DeadNewbie Yes, this. I have not found anything either. Might have to fire up OpenScad and roll my own.

[T3P3Tony]

@j-pickens @DeadNewbie

I have added the experimental design I used here:

https://github.com/Duet3D/Duet3-RotoToolboard/tree/master/mechanical

Note its not guaranteed to set the coil to the optimal height so may need some modifications.

[DeadNewbie]

@T3P3Tony

Thanks Tony, i downloaded this today, but I wont be able to test for a couple of days, I managed(stupid schoolboy error) killed my Roto board trying to unjam my roto extruder without powering down, I now have a very hot SAME51 Doh!!!

I would replace it, but I dont have a Atmel ICE to reprogram it. and a new board is cheaper(arriving tomorrow from E3D).

I will let you know how the print and sensor goes.

regards

Michael

[DeadNewbie]

@DeadNewbie

And My New board Arrives, and i have issues with it.

it keeps giving me can time out errors, even though m122 and everything else seems to work, but each time I try to configure a fan I get

Error in start-up file macro line 122: CAN response timeout: board 20, req type 6019, RID 11

got some more testing to do, but it looks like it is DOA.

[jay_s_uk]

@DeadNewbie what CAN cable are you using for it? a moulded end one or a soldered/crimped on?

[DeadNewbie]

@jay_s_uk

Hi Thanks for replying, yes its a Moulded cable, found the issue though.

in my school boy error moment when I killed my first Roto Board, I also killed my super pinda and roto 3 wire fan.

it looks like during the initialisation M950/M106 because the tach output from the fan was dead it gave the error, a replacement fan arrives this morning so I will be able to confirm it later.

all in all its was a very costly error.

regards