So... here's a little request: Can we have a free space display on the various file listings? The SD card I have in there isn't large, but it's fairly large by gcode file standards --- but still not unlimited. Would be nice to have a little indication of usage.
Best posts made by zBeeble
-
Free space display?
-
RE: Opinions on "FYSETC" ... politely, please.
@nightowl actually... I was considering that my take on e3d's tool changer might have one of the tools being a dremel like device --- for cutting and buffing... but right now it's just a thought.
-
RE: Moving a Z on a duet wifi
Thank-you for your patience. I believe I have resolved the issue... with a combination of your thoughts and my experimentation (as it should be). For posterity, here's wazzup.
BACKGROUND
The printer in question was built (originally) mid-2014 ... and with Chinese electronics. It was noisy and it ran hot. It's largely a Mendel from reprap.org ... combining some of the Prussia Mendel with some ideas from the Reprap-Pro Mendel and some custom changes suggested by the helpful fellow who printed the initial printed pieces for me (among them, a fine herringbone main gear set).
This I upgraded ~2016 or so --- the duet2wifi was a "new thing" when I did this, if that helps nail down the timeframe. I swapped the Chinese electronics for the duet2wifi, I added a heated and magnetic bed and I made minor improvements in the geometry.
This printer eventually choked on some filament and I didn't get around to fixing it until just recently. I have been collecting supplies to make something with the e3d tool changer (but different), but I haven't started assembly yet.
THIS ITERATION
So I started this iteration to improve a few things... one of the most major: add a BLTouch to the system. I ended up learning first that I had some really sub-optimal motors in play --- that only took 0.4A of max current (for X, Y and E0). I replaced these with 1.5A motors. Seriously, the documentation about selecting motors is good (although I found utube about parallel and serial that seemed to explain that better) ... but I'm relatively sure it wasn't available when I first did this.
After the upgrades, I found the print occasionally getting out of square. The pair of Z-axis motors were 2.4A beasts --- and so I hadn't replaced them in the first go round, but motors are pretty cheap ... so I ordered some more of the 1.5A ones. Then my Z-Axis problems got worse.
THE SCALE PROBLEM
So... here-we-are. The problem. Have you guessed yet? I think Phaedrux was dancing around it above. The original pair of Z-Axis motors were 0.9 degree motors. It would seem it is much harder to drive these fast. This is why the motor multiplier was 5104. I discovered this because after configuring my new motors to move more slowly, my "test cube" was 20x20x40 (and having trouble with layer adhesion).
Of course lightbulbs immediately lit (I didn't actually finish printing the cube --- I got to around 50% --- where it was 20cm-ish high ... and noted that it was only 50% finished and stopped the print). I cleared the bed and reached for the caliper --- 10 cm of commanded movement ... 20 cm of actual movement. Hrmmm.
This is the point I realized the situation. So I changed the multiplier to 2552 and adjusted the speed of that axis to 300mm/min (150 was working for the old config, so it made sense. 180 wasn't). I re-printed my test-cube. (If anyone's curious, with a nod to Star Trek's "Transport Test Cube", I have a 20mm cube that I use for testing the printer).
-
RE: The printing channel... or what to do with a webcam.
@jay_s_uk I have to say, my mind is kinda blown on what this can do. I suppose I'm off on this rabbit hole today.
-
RE: Free space display?
@droftarts thank-you, but ... it's a pretty obvious thing to include in the web control thing --- which is where I posted this.
-
RE: Filament sensor debouncing?
@zBeeble So... after some time, I finally did run out of filament, and that, then, verified both branches ... "This works" ...
-
RE: Filament sensor debouncing?
@OwenD Just got verification that this works (at least to sense the filament not running out).
... I increased it to 100ms to be pessimistic, but that would be correct... the printer is still (for a little while) in filament. It should run out for real (testing the other branch) before this print is through.
Latest posts made by zBeeble
-
RE: Clarifying BigTree Filament Sensor Connection.
@stuartofmt This, based on the filament position w.r.t. the header, agrees with what I have been referencing.
If I had V and GND swapped, would that kill the BigTree? What do you guys who understand the circuit diagram expect?
I did also try the e1stop --- no change there.
-
RE: Clarifying BigTree Filament Sensor Connection.
M115 says this:
m115 FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2022-11-30 19:36:12
And M591 d0:
m591 d0 Pulse-type filament monitor on pin e1stop, enabled, sensitivity 7.000mm/pulse, allowed movement 0% to 125%, check every 22.0mm, no data received
I've set the config to have a lower bound of 0 for this test. Effectively not stopping. This reading was taken after 200mm of extrusion.
-
Clarifying BigTree Filament Sensor Connection.
I got a BigTree Filament sensor v1 in a clearance sale. I finally got around to connecting it after making modifications to my custom printer to mount it. There are other articles on this forum and elsewhere about. I'm going to summarize what I know before I ask my question.
The BigTree sensor is a pulse sensor using holes in a wheel that turns with filament movement and this turning is sensed optically. Elsewhere you can find people figuring out the electronics. The unit (as stock) is apparently capable of quadrature (that is: sensing direction as well as distance. I don't know how to connect that bit). The sensor creates one pulse every 7 mm. An example config line is:
M591 D0 P7 C"e0stop" L7 R75:125 E22 S1
which means:
- M591: configure a filament sensor
- D0: on extruder 0
- P7: of type pulse
- C"e0stop": on the pins for e0stop
- R75:125: with a sensitivity of 25% of requested length
- E22: sampled every 22mm
- S1: enabled for SDCard prints
Now... the 4 pin header on the unit is (from nearer the business end to further):
- Ground
- Signal A
- Signal B
- Vss
... where the provided cable only connects Signal A. I think comparing A to B is the quadrature.
The connector on the duet 2 (e0 or e1) is:
- Stop
- V3.3
- Gnd
Now... I think that I erroneously connected signal to V3.3 for some time (hours).
Is this board dead from that? I'm not getting signal. Can I order parts and fix? Is my config incorrect? Let's put a bow on this for the future.
-
RE: The printing channel... or what to do with a webcam.
@jay_s_uk I have to say, my mind is kinda blown on what this can do. I suppose I'm off on this rabbit hole today.
-
RE: The printing channel... or what to do with a webcam.
@jay_s_uk so... you're saying that the duet is mounted into an SBC --- via serial or whatever the wifi/ethernet connect to?
-
The printing channel... or what to do with a webcam.
So... I have a duet2wifi. Love it. I also have a number of raspberry flavoured pis. One of them has the PI camera on it. I would like to have automated time-lapse of the printer running ... partially to identify what set off the pile of spaghetti I sometimes find.
I see there's a plugin --- motion webcam plugin --- but I'm a little on the back foot trying to figure out ... Does it do what I want? How do I install it?
What would I like? Ideally a time-lapse stored for each print. What is minimal --- I suppose the default is just putting the camera in motion mode.
-
RE: Bug: layer time graph starts at 2.
@Phaedrux sure. Note that this happens with multiple different files, but the particular one printing above is the 2nd include.
... hrm... at least one of my files is too big. Here's nextcloud links:
The config.g:
https://nextcloud.towernet.ca/s/nRAsmqJQYECKxQS
This is the file that was printing in the above pictures.
-
RE: Bug: layer time graph starts at 2.
@Phaedrux OK. Did the upgrade. No change. I took a pick at layer 2 (so showing layer one on the graph) and then at 3, 4, 5 and 6. You can imagine the rest. If it gets to 30, clicking on the "show all" link shows it from 1, but otherwise it's from 2.
-
RE: Bug: layer time graph starts at 2.
@Phaedrux Thx. Seems the most major changes have been 3.4.1 to .2 ... sigh. I dislike change.
-
RE: Bug: layer time graph starts at 2.
@Phaedrux urg. Where's the changelog again? I'm so change adverse ... urg.