@sonderzug et al

We have been considering a SAME70 CAN-FD control board designed to use CAN-FD expansion for most functions for a long time now, but need to consider the total stock of these processors available to use before adding another product that uses them.

If we did it Pi hat is one form factor that could be used but may not be optimal.

@ctilley79 just a thought ... if you are good enough to solder on wires, maybe desoldering the existing connectors would be an option for you.

@rilot love the design and the additional display! Are you able to elaborate a bit on the wiring scheme as posted on thingiverse? Especially on what are the names referring to in the excel pic posted?

Conn LCD = connection to lcd panel
Conn sd = ?
Exp1 = ?
Exp2= ?

Would be greatly appreciated!

@jrow I know an electronics tech whose day job is fixing production errors in dense PCBs that hires out her spare time. I'd love to mod a 6HC to 50 or 60VDC.

@3mm the BMG with a pancake nema 17 (in my case a Moon's) weighted in about 290g (75g for the BMG, ~200g for the motor, plus bowden coupler, silicon hose, bowden tube, ..).

The orbiter is 135g, so less than half the weight. It however isn't the weight on the flying extruder I'm concerned about, it's the yanking of the bowden tube (in my case was ~150mm) on my 380mm bed delta that I suspect is the source for artifacts I saw.

I can run 5k acc/600jerk/no input shaping/100mms-150mms, 0.015 PA, 0.6mm retractions with the direct mounted (on a 7cm tall, petg printed stand and tilted) Orbiter V2 with almost none / negligible artifacts.

I wasn't able to do that with my flying BMG.. had to run 3k/300jerk/~70mm/0.4 PA/1.5mm retractions for worse quality than on the current direct drive solution.

@nikscha I think it could be useful for some of those things but I would caution against replacing the strain gauge as the has been tried before for Deltas with the HE280 hotend from SeeMeCNC.

The strain gauge is more accurate and has worked better than accelerometer only. It could be great combined but I wouldn't go entirely over.

@pcr I think you still should have a diode on the input right?

Looking for a single header that will power the inductive probe and accept the signal generated. As well, it should be flexible to offer a few different voltages. I thought that a diode would be required to fully satisfy all the requirements.

@rjenkinsgb maybe not everything on the 1LC is needed ...

@dc42

To be honest: Nothing will prevent me. This is my current setup. But see it like that:
3 wires for X and Y endstops
8 Wires for the two steppers
3 Wires for my enclosure temp sensor
2 Can wires (to the toolboard on the hotend
2 Power for the toolboard
= 18 Wires in total.

That can be reduced to 4 fires from the Mainboard to the gantry (the new tool board) and 4 wires forward to the toolboard on the hotend.
But this is not my only usecase, see things like the carrot feeder which need more than one stepper. And the 3HC is really a big boy for driving two nema14 plus a servo at the end.

I had the idea to bild a "poor door opening thingy" for my v2. My "brain internal" solution would need to steppers, three sensors too.
I could think about a camera moving thingy, like a gimbal which keeps the focus on the hotend. Which would need more than one servo too.

I think that there would be a lot of usecases for a "intermediate" board. The 3HC fits perfectly into the 6HC range. They are perfect if you need big beefy boards with a lot of power. But the Mini 5+ road seems to be a bit under supported here.

@o_lampe brought up the next good usecase: An IDEX printer can profit from such a board too. You can drive X and U with that board and save a lot of wiring

Do not get me wrong David, I understand fully that you can not create a board for every single usecase which somebody brings up. That is logical and can not be done by your time and by the financial impact. But see it from my site:

I buy a Mini5+ for some good reasons: The price and the almost "best" solutions for printers like a IDEX, Voron v0/2.4 etc. The steppers are fine and big enough, I can attach a toolboard or two. Wifi included. A very nice board for a fair price.

I attached the 2 driver daughter board to the Mini5+ because I need 4 steppers for Z and 2 for X-Y. I have one left. (Toolboard on the hotend)
I have now the case that I want to build something like the carrot feeder. What should I do? Use two toolboards? Use one stepper from the expansion and add an toolboard?
Or shall I use the 3HC? That is almost the price of a Mini 5+? That does not feel very right to me to be honest.

And I can not be the only one with this kind of struggle ...

Cheers, Chriss

@aprz As it stands we are not planning on supporting higher than 48V on the 1XD. If your motors need >48V then you need to use a separate supply for the 1XD. If you have a brake on the motor then it may need 24V which would work for the 1XD as well.

The 3HC is unlikely to have a change to >32V soon, but we are looking at maximum voltages for the boards that use the TMC2160 drivers to review the changes needed to go to 48V safely. Our closed loop board that uses a TMC2160 and is in beta uses a TMC 2160 and has a maximum input of 48V

@gixxerfast blinking slowly and continuously in time with the one on the main board is good, it means that it has established time sync with the main board. There is a separate green LED that indicates that the 1XD board is receiving CAN commands from the main board.

@tlas the closed loop board is about to go into the beta test phase.

It also locks you into a single type/generation of SBC.

@veng1
would be interesting to know, how good the firmware handles different (quasi onboard) drivers? Especially for input shaping.
The external toolboards have the advantage of their own CPU and FW to handle their drivers.

@erfreuterstudent
that's a premier for me too, but we'll try.
With a toolchanger you could poll the diameter of the current tool in tpost#.g by using M118 S2 P"toolnumber"
Now the arduino reads this message and sends the aquired data, but here it get's shady for me. It is easy to receive messages and display them on DWC, but reading data into a global variable is unknown to me. I tried it over I2Cport, but fell into the same dark hole...
Maybe @dc42 has a solution now?

@luke-slaboratory there is some discussion of it here https://forum.duet3d.com/topic/14441/higher-input-voltages-for-steppers

@ansonyang you'll also find that the maestro won't get new features such as input shaping going forwards so is it worth the effort?
you could just use one of the boards supported by the STM32 RRF Project https://teamgloomy.github.io/supported_boards.html#stm32-boards-with-native-support
I wouldn't bother going with an LPC board

@lee7670 said in TMC4671 expansion board:

You can totally, do that, your stepping just changes the position target.

In a test run the Due was quick enough to answer every step pulse. There is no 'piling up' of steps I could apply a PID algorythm to.
The hardware QDE is capable of reading the encoder pulses at 42MHz. Not sure about the other interrupts, though...
If you like, we can discuss it here
[\OT]

@alankilian thank you for the suggestion

@jens55 said in Protection for fan output shorts:

I understand that a minor revision is planned for the Duet2 series. If it hasn't been asked for yet, I would like to request some sort of protection on the fan outputs to prevent idiots like me from blowing the output mosfet's.

We looked into providing fan output short-circuit protection some time ago. Unfortunately, thermal fuses are too slow to provide protection. Electronic fuses for 12V circuits are readily available, but not for 24V circuits.

A related question - is the Duet3 more idiot proof? If so that would be a big bonus for me.

Yes it's more idiot-proof, for example against shorting the external +3.3V or +5V rails to a higher voltage. The fan mosfets have a higher surge current rating; however they will still fail if you short a 24V fan output. They may survive shorting a 12V fan output, but I haven't tested it.

@T3P3Tony said in Z probe connector:

Will inductive/capacitive sensors that need these high voltages not just die please (just kidding!)

We thought we had nailed with with the IO ports right now that work for a BL touch and then you go asking for VFUSED on the same port..

More seriously I can see the appeal for the specific case of a high voltage indictive probe - the down side is it makes it much easier for people to (mis)wire up something that feeds the 24V into the 3.3V, 5V etc

I purchased 2 each of 8 different inductive sensors - 2 models were rated for 5V - the other 6 models for 10V-30V.

The performance of the 5V units was decidedly inferior to the 10V-30V units.

Thus my decision to stick with the far more common 10V-30V units and my suggestion regards the connector.

The other problem with inductive sensors is there seems to be no standard output configuration.

I didn't bring this up because I don't know of an simple solution - but I'm working on one.

To begin with you have NPN or PNP outputs. Then the outputs can be NO or NC.

Now if these were done sensibly the NPN units would be open collector and pull the signal low, while the PNP units would be open emitter and pull the signal high.

Then everyone could pick a NPN unit and activate the pull-up on the Duet.

No such luck.

I had to come up with a scheme using two resistors for each model to get the signal to match the logic levels of the Duet inputs. The required values and arrangement of the resistors tended to be unique to each model sensor.

I found it very frustrating.

Here is how I ended up doing it so I could easily swap probes during testing.
fcw Inductive Probe Connection.jpg

I had to make up several different resistor assemblies and use the correct one for each probe.

Frederick

Meanwell and similar PSUs have a voltage adjustment pot, which usually provides more than 10% adjustment each way. So a 36V PSU could be turned down to 32V.

Hello! Can you please post what is m1 mmos and what pins used ? or post close photo module of both sides, need to fix fan whine on my ender 3, thanks alot!