I figured it out. I was poking around and saw that somebody else had an issue with the electrolytic capacitor and how it had lifted off the board. I re-soldered the capacitor down onto the board and thought I fixed it. It seemed to work, but once the board heated up from the residual heat I was still having issues.

I decided to look at the IR LED's through my phone camera, and only one was lighting up. As I pressed on the unlit LED, it lit up. I re-soldered the unlit LED, and now they both light up, and the LED doesn't lift off the broken solder joint as the board heats up.

If anybody else out there has issues with their boards and wants to check that the LED is working, look through your phone camera in the dark. It should show up as a pink/purple light on the screen.

I figured it out. It's crashing the head on the X-axis due to the probe point for the leadscrew being slightly off. I just need to adjust that.

@Phaedrux Added M558 with just the H parameter to my G29 macro and now it works perfectly. Thank you.

@T3P3Tony None of the resellers in the USA have the 6HC in stock, nevermind there is about a 20 dollar markup through them.

@DIY-O-Sphere Okay, this is what ended up working.

; Heaters
; Bed
M308 S0 P"e6temp" Y"thermistor" T100000 R4700 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H7 C"!exp.heater7" T0                           ; create bed heater output on exp.heater7 and map it to sensor 0
M307 H7 A223.1 C298.7 D1.2 V22.8 B0            ; Disable bang-bang mode for the bed heater and set PWM limit
M140 H7
M143 H7 S80                                   ; set temperature limit for heater 0 to 80C

The naming conventions for pins and thermistor inputs, as well as having the number offset for them seems like an oversight.

@mrehorstdmd @zapta @mendenmh @mwolter @arhi I just replaced the Igus bushings with the LM16UU I ordered. No more issues. Now I have no idea what to do with all these Igus bushings I have.

Hi all.

I have been using the differential IR probe for a while now and it has been working flawlessly. However, it has started to act up and I am not sure why. I changed my nozzle out to a bondtech CHT nozzle, re-adjusted the z offset, and now I have issues where the IR probe will not trigger. I re-ran a Z calibration to be sure, and I had some odd readings. With the heated bed off I was getting consistent readings between 1.55 and 1.56mm. I then turned the heated bed on, and as the temperature of the bed climbed, the z offset started to decrease. At 120C the z offset was reading 0.95, and I was getting some instances where the bed was crashing into the nozzle after the probe failed to trigger. I now have issues with printing because the probe will not trigger before it hits the nozzle. I have some pictures showing that the probe is definitely not too far away from the nozzle. I removed the probe and looked for physical damage on it and have found none. This issue was happening on RRF 3.2.2 and 3.3 (I updated in case maybe it was a bug).

The heated bed is a high temp e3d heated bed with borosilicate glass. I have placed a piece of matte black paper between the glass and the heated bed.

Could it be noise on the electronics? I've had issues with that before. Maybe I can change the mode of the IR sensor.

Any ideas on what the issue would be? I would like to continue using this probe.

Yeah, definitely my Z-axis. I ran some prints and changed my pause and resume to not lift Z and the indentation is gone. Looks like I need to get some pillow block bearings for the leadscrews and new couplers.

@wilriker Would help if we knew exactly what was going on.

Also, if all is he looking to do is change power at the heater block he can change the PWM duty cycle and get the same results. If he's looking to increase power draw on a FET or something then he would need some power resistors.

@tekkydave Yep, mine is fake as shit. Looks like I need to get some better ones.

Hi all,

I'm trying to speed up my homing on my printer for coarse homing. From other posts https://forum.duet3d.com/post/41795 I see that I can accomplish this by issuing an M122 command. However, when issuing the M122 command, I do not see the information I am looking for.

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.02 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3S0-7JKD6-3SN6K-1UMRA
Used output buffers: 3 of 40 (29 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 98448 of which 12 recycled
Never used RAM 95684, free system stack 129 words
Tasks: NETWORK(ready,29.6%,236) ETHERNET(notifyWait,0.2%,443) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,259) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,8.4%,57) MAIN(running,61.8%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:14:52 ago, cause: power up
Last software reset at 2023-02-05 19:51, reason: User, GCodes spinning, available RAM 94964, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 129
MCU temperature: min 49.0, current 50.4, max 51.1
Supply voltage: min 25.7, current 25.8, max 25.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.3, max 12.6, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/186/186, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 40, reads 36565, writes 2 timeouts 0
Driver 1: standstill, SG min 0, mspos 392, reads 36562, writes 5 timeouts 0
Driver 2: standstill, SG min 0, mspos 776, reads 36562, writes 5 timeouts 0
Driver 3: standstill, SG min 0, mspos 1000, reads 36562, writes 5 timeouts 0
Driver 4: standstill, SG min 0, mspos 792, reads 36562, writes 5 timeouts 0
Driver 5: standstill, SG min 0, mspos 872, reads 36565, writes 2 timeouts 0
Date/time: 2023-02-07 22:02:08
Slowest loop: 4.58ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 38, maxWait 75851ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 106, completed 106, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no filament
=== CAN ===
Messages queued 4700, received 10691, lost 0, boc 0
Longest wait 3ms for reply type 6037, peak Tx sync delay 6, free buffers 50 (min 49), ts 2576/2576/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 3.68ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8
= Ethernet =
State: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
= WiFi =
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

Is there a different command I need to issue? I searched the docs and could not find anything related to the MaxReps field, and I tried different P parameters with M122 to no avail.

Thank you

Hi all,

I'm trying to set up the macro files in this thread Re: Single Macro for filament handling?.

I am using a simple filament switch. The issue I am having is the object model sensors.filamentMonitors[0].filamentPresent returns a null value when querying it with M409. If I query sensors.filamentMonitors[0].status I receive either "ok" or "noFilament". The issue is, I can't use this in the if statement. Is there something I am doing wrong here? I thought the filamentPresent key would work correctly, or is that only for the laser filament monitor or the rotating magnet filament monitor?

Thank you

@OwenD So what options are there for something that is as light and compact as a linear rail, but is actually straight? Trying to find straightness tolerances online for even basic stuff like aluminum extrusion has been a headache.

@JoergS5 The bed is isloated. The swiss clips are removed, the glass on top of the aluminum is 'floating'. The only force acting to deform the bed is the force of the microswitch on the euclid probe, which is negligible.

I've already determined that the rail is the biggest issue. I can slide a 0.1mm piece of paper underneath it with ease when I have it on a piece of ground granite. The thing is like a see saw. But apparently that is OKAY according to everybody I have talked to, because there 'isn't a tolerance' for straightness. So again, my original question, why does everybody use linear rails if they are as straight as a wet noodle.

@gloomyandy The wire loom on the old machine is stiffer than the new machine. The air tube is a cpap tube, it is extremely flexible. The CAN wire going to the head is a continuous flex IGUS CAN wire made for these applications. It's very flexible. The power wires are also silicone fine braid wires. I HIGHLY doubt it is the wires. I have tried repositioning them all over the place, and the heatmap doesn't change.

@mrehorstdmd I've run calibration after calibration. The layout of the heatmap is identical every time. The max deviations may vary by 0.005mm run to run, but I believe that is within acceptable error ranges to rule out the leadscrews.

For getting the bedframe to not fight itself, the screws were all loosely inserted into the bed frame, the frame was 4 point leveled, and then certain screws were torqued, bed was 4 point leveled again, and remaining screws were torqued.

The 4 small screws holding the bed to the frame are what is provided by e3d to mount the bed, and they are not tightened, as e3d says to leave them loose for the bed to float.

The reason I am using 4 points is to specifically eliminate any skew in the bed. I don't believe a kinematic mount will be beneficial here, especially seeing as I have no way of currently making one that would be able to withstand the max 250c temperature of the bed.

This is also a very similar mounting system that I have on my older machine, which once again is producing better results. The way I have measure each machine, the bed will not affect the results.

@moth4017 Do you have a post about it that you can link? If not you should make one and post some pictures of your setup.

@moth4017 I'm not sure if that would fix your issue. What exactly is the issue you are having?

@Tinchus Are you talking about these tolerances?

What I was told, is that the tolerance of width N and height H has no effect on the straightness of the rail, at least for the MGN series rails. There are some rails that are wide enough that there is a straightness tolerance, but everything I have been told is that there is no tolerance for straightness, and that there won't be any guaranteed straightness.

This is one response I received.

"So typically single bolt hole row linear guides do not have a straightness tolerance. The rails do have a dimensional tolerance which is typically +/-0.0002" or so for width and height. The reason for this is that at any significant length (ie 10x the rail width or so), the straightness of the rail installation is determined by the accuracy of the mounting surface or mounting procedure. It is a bit like asking the straightness of a piece of wet noodle. It can certainly be made straight, but it just depends on how it is aligned or what it is sitting on.

For super high accuracy applications, you would want to follow the procedure in the catalog where you machine a grooved shoulder that the rail sits within. You clamp the rail to the machined edge and then tighten down the bolts. This ensure the rail matches the straightness of the machined edge. In practice, very few installations do this especially with the MG series rails. Instead, you would use a precision ground parallel or some other straight edge and tighten the bolt holes sequentially while clamping the rail to the straight edge. Even then, this is uncommon. Many users just loosely thread the bolts in,push the rail fully against the bolts while tightening without any straight edge at all. This does get you straight enough for many applications. What are you aiming for on straightness and over what span?"

This is the response I received from a different company.

"Linear rails get their straightness from what they are mounted to. Linear rails should ideally be mounted against a reference edge, see here:

https://www.tuli-shop.com/blog/the-do-s-and-don-ts-of-linear-rail-alignment.html

Though some 3D printer designers don’t heed that, resulting in the alignment needing to be done manually.

The +/-0.023mm refers to something different than straightness. If the rail is mounting on a perfectly flat surface, the position of the carriage would be expected to deviate only 0.023mm in any direction while being slid along the rail. It is a measurement of the machining accuracy of the height of the rail. Some more reading here:

https://www.linearmotiontips.com/how-to-choose-linear-guide-accuracy/

guide rails tend to conform to the surface on which they’re mounted. In order to realize the full benefits of a higher accuracy linear guide, the mounting surface should be machined at least to the same standard as the guide."

I'm not saying you're wrong, but I have people telling me conflicting things, so I can't make heads or tails of it. I know there is a tolerance somewhere, or these rails would be shaped like a piece of wet spaghetti.

@mrehorstdmd Here's the old machine. Probably has 3k hours on it with no real maintenance to the motion platform besides oiling and cleaning up debris/dust.

Here's the new machine. Probably about 10 hours on it.

@dc42 I think it was just the toolboard. That toolboard was being warrantied for an accelerometer issue. I replaced it with a new tool board and it works fine. Is there a way to add this information to the warranty form I filled out?

@o_lampe no, but the numbers are there, and the crap machine has about half the deviation.

@T3P3Tony is mounted on 20x20 aluminum extrusion.

@mrehorstdmd I'll post those up when I get a chance.

@Tinchus see, that's exactly opposite of what two resellers have told me so far. Both of them have said that there's no tolerance for straightness on the rail, and that it's meant to conform to the reference surface. I know that's bullshit, because there HAS to be a manufacturing tolerance, even if it is just a general tolerance. So short of getting something specifically machined, it seems that I'm SOL.