Hello,
i need the some information about 2 SMD componebts mounted on the DueX 5 Board.
In more detail do i need the manufacturer, model and the parameters / specifications from the diodes D7 and D18, listed in the BOM as
Are there any replacement variants for these components, if the original parts are not available to order or too expensive?
Thank you in advance..
1.) Own a Google NestHub.
2.) Visit https://demille.github.io/url-cast-receiver/#
3.) Start with "cast session", your NestHub displays an empty page.
4.) Enter the URL of your printer and choose "location"
5.) Confirm the URL with "send"
Your printer can now been controlled by your NestHub.
Have fun...
Maybe this can be automated in any way. This first information on using your NestHub as a display should inspire more developers beside myself to look into this.
For local execution you can
I made the selection of "location" default and updated the standard URL to fit my printer, but you can alter this in the .html file very easy. Finally i replaced the direct link at the bottom to the DWC of my printer, also.
Have even more fun!
My ordered sensors just came in today from china. Even better, the new firmware is also available right now.
@dc42 Before soldering a header to the breakout board, i would love to know If the analog inputs of the sensor will be available in reprap firmware. Just like the panelDue we have available inputs for free at no additional cost (other
than you implementing the code to make then work) on our remote devices, which i already have plenty ideas of what crazy stuff we could connect to them.
So please let ne know If you also have the future of what DuetFirnware could become in mind and If the analog! inputs are/will be available via gcode.
@dc42 Okay, a LIS3DSH Sensor is ordered to connect via SPI on my Duet2wifi.
As i understand, the LIS3DSH should be also supported, because its only a more capable version of the LIS3DH. If not, there it goes to my bin of parts and 1.60€ down to the gods of tinkering. Just using the second position of this order (a true and only supported LIS3DH) then.
Just for planing things ahead, when will Version 3.3b3 be released?
I would love to add CAN-bus connectivity to my machine with Duet2 hardware. Is there yet a viable path to go for people capable of soldering and willing to tinker with their hardware?
@dc42
I saw you implementing the upcoming support for a LIS3DH (3-axis MEMS accelerometer).
As it supports SPI and IIC, my question is whether both protocols are supported by your Implementation. I am with Duet2wifi (as you probably already know) and want to get this feature working on my machine. Can i order such a sensor yet or do you plan to switch to another sensor Platform?
I would offer to test the Implementation as soon my sensor arrives (If i am to order one, which depends ob your answer).
Hello dc42,
How could i verify your argument regarding the fan output with my multimeter?
What do you think of my issue with the 12V rail? I currently have no idea how to fix this...
Maybe someone else other than me and the ultimate god of duet3d developers could take a quick look in the circuit diagramm of the Duex5 and connect my measuring results with some reason of them happening.
Or maybe you are just the kind of swarm-bee with knowledge of electronic things and the ability to point people other than you in the right direction? Stop hiding, start to participate in resolving this issue. Show me your bee-skills...
Okay,things progress...
Today one condensator of my system-fans exploded, because i ran it with a higher voltage than it was rated for.
Very loud, when standing right next to them exploding.
Now, this one fan output of my duex5 does not work anymore.
Measuring the two Sides of the Diode D15 results in 10.8v when fan should be off and 7.9 when on.
Should i take a replacement of this diode into consideration?
I shorted the 12v connector of my duex5 and now got 14v - 20v (depending on the load in the 12v rail) when the internal 12v Regulator is enabled.
How can i fix this issue?
Could a destroyed Diode D7 cause this behavior?
I solved it for the moment by deassigning the probes, doing my M585 and reassigning them again. But this cant be the final solution.
; Start Workaround for M585
M558 K1 P5 C"nil"
M558 K0 P5 C"nil"
M558 K0 P5 C"!e0stop"
M585 P0 S1 F50 Z-5.15 ; Probe BedSensor (Offset to Bed: 0.15mm)
M558 K0 P5 C"nil"
M558 K0 P5 C"!zprobe.in" H5 R0.000 A30 B0 S0.01 F200 T2000 ; Setup the Z-Probe (switch, active high)
M558 K1 P5 C"!e0stop"
G31 P1000 X25.0 Y-13.0 Z0.830 S22.0 C0 H0
; End Workaround for M585
Currently on RRF3 and DWC2 the heightmap does not get loaded when using M505 to work with multiple configurations.
When clearing probe 0 and then assigning my second probe to K0 it works, but that can only be a workaround so far.
Everytime when failing, the trigger is triggered after all allowed movement on this axis is done. Which is too late. The movement is not stopped.
But only if no G30 is executed before.
Please Help...
The old code still works:
M585 E3 L0 S1 F150 Z-5.73
This message occours after the gcode from stop.g or cancel.g has been started.
I tried to investigate the problem a little further and found that when touching probe K0 the movement of M585 stops. So this has then to be fixed in firmware, i think.
Yes, in any of them. I did an offline search over all files with Notepad++.
My only problem is, this does not work.
I configured my probes in config.g:
; Configure Inputs
; E0 - ToolHead-Offset
M581 T2 P"!e0stop" C0 ; Monitor endstop E0 for a rising edge Signal (NO - normally open Switch, active high), calling macro-file trigger2.g at any condition
; Probes
M558 K0 P5 C"!zprobe.in" H5 R0.000 A30 B0 S0.01 F200 T2000 ; Setup the Z-Probe (switch, active high)
M558 K1 P5 C"!e0stop" ; Setup the Calibration-Probe (switch, active high)
and touching the probe creates the trigger as planned. But when running the following code in bed.g, the probe will not stop the motion or trigger like normal, until its already too late.
M98 P"position_calibration_nozzle.g" ; Move to BedSensor
M208 Z-3 S1 ; Enable Movement below the PrintBed (override Z-min)
G1 Z5 F200 ; Move to defined Z-Position
M585 P1 L0 S1 F50 Z-5.15 ; Probe BedSensor (Offset to Bed: 0.15mm)
M400 ; Make sure everything has stopped
G4 P1000 ; Wait a Second
m81
G10 P0 ; Show Offsets
M114 ; Show Position