Posts made by planeguy

Self-designed with inspiration from Bill Steele's work, the Printrbelt, and Zechy's build. I'm working on writing some stuff up but nothing yet. I wasn't even sure if was gonna work!

@phaedrux said in the worst corexz conveyor belt printer i've ever built:

That's cool. I'd love to see it in action.

i put together a vidjeo of that print: https://youtu.be/4sQmJCS3lQg

since then I figured out a good chunk of my issues were due to not properly setting the conveyor belt steps/mm.

It's the worst 3d printer i've ever built and designed. It's the first one, so there's that. A slanted-conveyor-belt-bed dealie.

I wanted a proper z-probe down to the bed, so I set the duet to CoreXZ and set the conveyor as the Y axis. Blackbelt Cura will do the an angled slices and the whole conveyor-belt thing really well, but it assumes the bed is Z. I uses the post-processor in Cura to swap all the Ys and Zs in the G-code and it worked mostly!

There's definitely some adjustment to do: Z is a little out of wack, leaning hard towards the front of the machine, and there's no on-board print cooling (hence the old case fan in the back). Honestly I was worried I was just going to get spaghetti instead of a kind-of-successful-conveyor-belt-stunt-print (the calicat's hollow inside).

Thanks to the forum members who helped me out by replying to my idiotposting or just helping out others and popping up in searches!

Quick reply for the next person who searches

So I figured out I had too many connectors between the probe and the board... probably too much resistance? Anyway a direct connection fixed the problem. Working probe > nice wires any day.

Del

Sorry for the bump, but I've been farting around with it over the weekend. Mostly, what should the duet WiFi show when there is no z-probe plugged in? It's hovering around 250 which seems off for something that isn't plugged in.

Anyway thanks again,
Del

Hi all, I've got weird issue I dunno what to do about. I just cleaned up the wiring on my new printer, but now DC42's IR sensor is giving strange values. It hovers around 130 and drops to 90-ish when triggered. The light blinks 4 times on boot as expected.

Any thoughts?

Thanks,
Del

@vj said in fans on different voltages:

@supraguy said in fans on different voltages:

@vj said in fans on different voltages:

If you use different outputs on the same powersupply, does it give the 12V supply a common ground with Vin?

Yes, I will have a common ground point, since the converter doesn't isolate its output ground.

Good to know! Euhm... out of curiosity... the powersupply also does not isolate its different outputs?

(the more I learn, the more I think I will go with the option of a DC-DC converter connected to the fan output, and PWM fans with the PWM control cable connected to FAN- of the desired fan output; no using an SSR)

Been searching this fan stuff and just wondering if this turned out as planned?

I'm just plugged into the computer via USB right now. More importantly the fallback method 1 worked and got up to 2.0! 2.02 worked fine via the "usual" method after that. Thanks so much @Phaedrux !

No luck on 1.21 or 2.0 using your previous technique

Software Information
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20 (2017-12-23)
WiFi Server Version: 1.22
Web Interface Version: 1.22.6
Web Interface by Christian Hammacher
Licensed under the terms of the GPL v3

6:41:56 PM
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (14 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4S4-6JKDA-3SD6T-K3SHW
Static ram used: 15448
Dynamic ram used: 99320
Recycled dynamic ram: 4016
Stack ram used: 1392 current, 4376 maximum
Never used ram: 7912
Last reset 01:23:39 ago, cause: software
Last software reset details not available
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 24.0, current 29.7, max 29.9
Supply voltage: min 1.6, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2019-02-05 18:41:55
Cache data hit count 4294967295
Slowest main loop (seconds): 0.022647; fastest: 0.000034
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.22
WiFi MAC address ec:fa:bc:0b:fa:34
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 27232
WiFi IP address 192.168.2.97
WiFi signal strength -52dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket states: 0 2 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

@Phaedrux I tried your procedure and it did the same thing: prompt for update, do something? then come back as 1.20. Is an older duet wifi incompatible, perhaps? I can't tell from here.

Hi guys, I'm having trouble upgrading my duet wifi. It's been sitting around for a year-ish as I get the rest of the machine ready, so I'm just now getting around to it. I was able to upgrade from 1.19 to 1.20, but now whenever I upload a firmware, it takes it, asks if I want to install, then seems to do something, but when it all comes back it's still at 1.20. Any tips?

Thanks,
Del