@psike you shouldn't need to set your Z position if you set the endstop location correctly.

@marioys97 you might want to search for "PWM to 4-20mA converter" and adapt the designs you find for 0-85mA.

The E3D PT1000 cartridge arrived, I installed it, and the printer prints well, as it did before. I can sleep better now. Definitely worth the money.

@phaedrux said in Toolboard 1.1 - Driver not present:

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

Done. Thanks

Hi everyone.
After making suggested changes everything is working correctly now. Thanks a lot 🙂

@phaedrux have now! Just remembered I saw the log messages before, but maybe it was somewhere ephemeral.

@rjenkinsgb ah I did not know that. I thought a OTG adapter would be something like a crossover ethernet cable. And with that one it doesn't matter which device sits on either end as long as there is a crossover (and even this isn't always necessary nowadays).

I will try it then with the otg Adapter on the phone and a standard micro b cable in the duet and report back.

EDIT: works

Now I only need to find wiring that fits my space constraints 😉

@dc42

On a duet2 running RRF 2.x the board would reboot after an estop trigger without issuing a M999.

I think my current approach using the reset input on the duet3 should work. And I also don't see all of the driver errors like I do with m112.

If I was to upgrade an duet2 to RRF3.3 with a duet expansion how would I reset the board via an external input? If memory serves the reset pins on the duet2 are in the 50 pin.

@o_lampe
Sure that's what I will do in case it'S the only possibility.

But to have a nicer cable management it would be good to have one pair from the PSU to the mini and one from the mini going to the strip

@fcwilt Frederick, thank you great site.

@jay_s_uk thanks

@o_lampe hugely thank you so much!
that worked...i was just confused regarding the 3.3 v pin because on the TB6600 there is only 5v pin but somehow that worked without any problems; tbh that mini breakout board is the real lifesaver.

@rushmere3d Oh good tip. Under experimental settings on cura I had experiemental bridge settings enabled. Those then have fan speeds and flow rates for fan settings. I just adjusted them to something more resonable as the 100% fan speed is really loud.
now looking at it, the settings are pretty interesting now that I look at them and after playing with it I found bridge settings make a huge difference.

Link to the settings description:
https://community.ultimaker.com/topic/22195-introducing-the-experimental-bridging-settings/

@e4d

You would need to measure the actual position of the shaft and the commanded position of the shaft to see the lack of torque during microstepping.

From the Faulhaber site:

What Does It Mean? The consequence is that if the load torque plus the motor’s friction and detent torque is greater than the incremental torque of a microstep, successive microsteps will have to be realized until the accumulated torque exceeds the load torque plus the motor’s friction and detent torque. Simply stated, taking a microstep does not mean the motor will actually move. In summary, although Microstepping gives the designer more resolution, improved accuracy is not realized. Reduction in mechanical and electromagnetically induced noise is, however, a real benefit.

@taconite a couple of notes regarding your post:

The internal circuit of the input looks like this, with no connection to ground.

8811d975-4183-4a84-a65c-041d8c838c5c-image.png

Since the input is pulled down, you want to connect your opto coupler between the input and ground and use the inversion symbol "!" if needed. (You could still have an external pullup resistor if the internal 10K is too high for your purpose, if this an issue, you can ask here).

e8edb431-4447-4588-9b03-23c173a71eca-image.png

BTW, if you would use a duet 3 board, you may be able to drop the opto coupler all together since some of the input are can get higher voltages.

Can you tell where the whine is coming from?
Can you show a photo of the wiring and the BLtouch?
What version is the BLTouch specifically?

@demodemo M950 S0 for first, M950 S1 for second, where S is the servo number. Make separate deploy and retract Gcode files for each probe and servo; use deployprobe0.g and retractprobe0.g for probe 0, deployprobe1.g and retractprobe1.g for probe 1. Deploy and retract macros should reference the respective servo for each probe.

Ian

@dc42 More learning. Thanks!

@dc42 Thanks for the info.

Just signed up with DWC, very nice interface. Now I can continue with the next step, installing the electronics and connecting.

It's amazing how quickly help is provided. I really appreciate it.