Posts made by tjschweizer

Hi, I'm just checking if there are plans to release to the KiCad files for the Duet 3. I've seen some discussion about waiting until the Duet 3 officially released, and was curious if/when that is still happening.

In the GCODE terminal type:

"M303 H1 S200"

Then when finished type

"M500"

This is something I've been wanting for my printer for a long time - a manual jog box.

The Panel Due and/or LCD works great for general movements and stuff, but when I'm calibrating my bed or adjusting babysteps or something, it would be extremely useful to have something with tactile feedback for moving without having to look at a screen.

Something like this:

I'm not sure what the easiest way to go about interfacing it would be - probably using SPI - but it wouldn't take me too long to design up a PCB for one of these. If support for something like this gets added to the firmware, I solemnly swear that I am up to no good I'll design one and post the schematics and stuff on github.

Unfortunately the valve has a stem that doesn't travel vertically when turned (it has a "non-rising valve stem" - first valve I've ever seen like it), and it is a 10 turn valve. Without some sort of feedback - stall detection or pot - I have no way of knowing when the valve is actually closed.

Thanks! I think that will be a pretty good option, didn't even think of stall detection. I would have to drop the current to that stepper way down to have a stall at a reasonable torque - I'm using 3D printed gears on a smooth shaft (no flat on it, although I probably could add one…).

That could eliminate the potentiometer entirely though. This seems like the best option. Thanks again!

So this is a pretty obscure use case, but on my printer I have made a stepper driven air valve that is also connected to a potentiometer to determine the position of the valve. This valve is connected to the building's compressed air supply (I made my own Berd-Air tube for part cooling)

As it currently stands, I think the easiest way to set this up would be to make a separate board with an ATTiny, read the output PWM from the Duet, and control the stepper with a separate A4988 board or something - reading the potentiometer with the ATTiny.

I was just wondering if there was some way I could do this natively on the Duet Ethernet that I am missing.

Thanks!

Yeah, I got some flux in the SD card socket and now it is a little sticky. I should've pulled the card out, probably would have helped. Lived and learned.

So the internet connection is perfect now. I get normal 1Mb/s upload, AJAX errors all but disappeared, and the MOSFETs work great.

I'm not sure if anyone else needs to switch to/from Wifi/Ethernet, but if you do and aren't comfortable soldering on this board let me know and we can work something out.

I was having issues with my Duet Wifi on a University network - something about the way the traffic was routed caused me to get upload speeds around 18 kb/s. So I purchased the Ethernet daughterboard from Think3dPrint3d - they were super helpful, and it was cheaper than I expected.

Anyways, here's some pictures from the conversion. I also replaced 2 of the fan MOSFETs that I blew a long time ago. Between ordering these parts and receiving them, I blew my last MOSFET, so my Fan 3 won't work. Ah well.

Duet Wifi, Ethernet daughterboard, and MOSFETs.

My whole setup.

First I removed the bulk of the solder from the Wifi chip with desoldering braid. I absolutely love the MG Chemicals stuff.

I then heated the board up from the bottom right below the Wifi chip so I could remove it.

Removed any remaining solder on the pads and cleaned it up with an acid brush and rubbing alcohol.

Pre-tinning the holes.

A nice desoldering gun makes everything easier.

For some reason the headers that the Ethernet daughterboard came with don't fit. I pulled those out and replaced them with my own.

Fits great, just soldered it in and it works perfectly. Now the MOSFETs…

First, remove the old MOSFETs using desoldering braid.

Some solder paste

New MOSFETs in place

Done!

Ah. Well the chip is the same exact thing shown here:
https://www.adafruit.com/product/2471

And based on what I kind find showing the different versions (and the KiCad schematic on Github) - I believe it is an ESP12.
The schematic says ESP-12E

Mine has the ESP8266

Just sent an email, thanks!

Off topic, but can I ask where you learned so much about ARM development?

I have gone through your code quite a bit, and how you managed to integrate ASF with Eclipse I don't think I'll ever understand. Do you have any books that you would recommend?

I've seen it mentioned a few times on the forums, but I was just wondering if there is an option yet to purchase the ethernet daughterboard. I want to convert my Duet Wifi to a ethernet version. I have a hot air gun and do quite a bit of reflow work, so it shouldn't be too bad.

I'm just wondering if the offsets set in bed.g are used at all in the heightmap, if there is some sort of interpolation going on.

According to the instructions for calibrating a Delta printer, the Z-offset used in the config.g file is the trigger height at 0,0 - and the heights in bed.g are relative to that trigger height.

However, if there is a spot on my bed that has a larger trigger height, is this compensated for when doing the mesh grid?

Thanks everyone for the info. I tried a new micro sd card, and that didn't help. I then setup Octoprint on an rpi3, plugged that into the duet via USB, and my file upload to the rpi3 is extremely fast.

Conclusion: there is something either by the Universities network or the Duet's wifi firmware causing issues with uploading to the Duet.

Now I have Octoprint setup, which I wanted anyways for the webcam streaming. The only problem is I liked DWC more than the Octoprint interface.

Is there any method of transferring files from the RPI3 running Octoprint to the Duet over USB? That'd be clunky, but if possible then I could use the DWC for everything but uploading files.

Also out of curiosity, are there plans to sell the Duet Ethernet's daughter board as a standalone? I've seen mention of that on the forums, but I couldn't find anything in the shop. I might just buy the W5500 and make my own circuit in the meantime.

So I've been having a super slow file upload to my Duet Wifi (on a Rostock Max V3). I hit around 20 kB/s, and I'm on a gigabit network.

A little background info: I am on a University network, and the printer has a hostname so I can just type (example.example.edu) and load the DWC. My computer is hooked up via ethernet. When I ping the hostname or manually find the IP address of the printer and ping that, I get less than a millisecond with no lost packets.

However, when I upload files the speed starts around 1MB/s, and instantly drops to 20 kB/s. I installed Wireshark and noticed a lot of TCP errors during upload. I have tried from multiple computers and multiple browsers.

Here is a link to a wireshark capture that I sanitized with TraceWrangler

https://drive.google.com/file/d/0B8Bk7dfLGbNTS1JjV0lYMllrTGc/view?usp=sharing

That is filtered to only the communication between my printer and my computer. Right when the capture starts is when I first open the DWC in the browser.
I attempt to upload a file around the 57.2s mark.

Also here is the output of M122:
M122
=== Diagnostics ===
Used output buffers: 4 of 32 (8 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08D6M-91AST-L23S4-7JTD8-3S86Q-1PXXK
Static ram used: 21176
Dynamic ram used: 96040
Recycled dynamic ram: 1568
Stack ram used: 1304 current, 5928 maximum
Never used ram: 6360
Last reset 00:31:42 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 3224 bytes (slot 3)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 46.4ms
MCU temperature: min 20.2, current 27.8, max 28.6
Supply voltage: min 14.7, current 14.8, max 15.0, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-09-19 09:32:29
Slowest main loop (seconds): 0.047592; fastest: 0.000000
=== 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 heater = 0, chamber heater = -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
WiFi firmware version 1.19.2
WiFi MAC address xx:xx:xx:xx:xx
WiFi Vcc 3.15, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39176
WiFi IP address xx.xx.xxx.xxx
WiFi signal strength -61dBm
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)