Posts made by greecher

Which version did you download? You may have to go to 1.19 before 1.20, and there was specific instructions on the wiki for that step. 1.19 to 1.20 was easier after.

another upvote for feature, toggling back and forth works, but kinda sucks.

Don't get me wrong, I love that there is a very active development going, and that some great new features are being added, but it does look like when I look over the messages about attempts issues etc that there is a basic issue of interplay differences between the wifi firmware and main firmware that looks just plain ugly. To whit, it seems like that for every alpha/beta release, the instructions are tweaked just a bit, or have to be retried several times to get it to stick. When it does go to final release, it will be greatly dependent upon what previous release you are coming from on what dead chicken waving procedure you will need to do to get it to work. I do know we are working with advanced hardware that is arguably the best around, but this part just looks plain awful.

I had the opening issue of just purchasing one out of the box from filamentum that had old firmware versions that where seemingly 6 months old. Having to go through the procedure of making sure I waved my hands just right to get it to go right, and also did an upgrade to 1.19beta4 thru a couple of alpha/betas, but i fear for my sanity in trying to track down the correct set of hand waving techniques based upon where I was coming from, especially if you decide to skip some along the path.

Are there plans to make sure that the path is always the same no matter where you are coming from, as I would think the less daring would decide to only hop from major version to major version, and would expect that the transition should always be a smooth one. Yes you may require that they cannot skip major versions, ie 1.18 to 1.20 must have 1.19 major release in middle, but having to go thru the alpha/beta's as a requirement would be verboten. The software for the advanced hardware should be taking care of the headaches to make sure that no matter where you started, you can successfully get to the end point of a standard release, and the procedure should be the same every single time.
#endgrump

DC42,
man you do a bang up job, thanks for the info, put it in will try it out.

dave

DocTrucker, thanks for the info, I'll be trying some 2mm ones first, but am saving that link back for even finer.

dave

Cool on loggging, have 1.20 installed, how do you enable logging tho.

Would sure be nice to have a log of canceled and finished prints, for records, but also performance differences. Can’t really count on web interface to be up the whole time to snag it manually. As it is post printing, shouldn’t be a performance drag to write a lot of the print status items to a log.

What effect is a finer pitched lead screw offer to the issue.

doh, thank you for your patience with dolt users like me sometimes, totally misread where to look.

here is my current install:
Software Information
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20beta4 (2017-10-28)
WiFi Server Version: 1.20beta2
Web Interface Version: 1.19.3
Web Interface by Christian Hammacher
Licensed under the terms of the GPL v3
Dark theme kindly provided by Fotomas

and here is a picture of the tools menu
https://imgur.com/a/tqw8y

So I think i have the latest everything, including the DuetWebControl 1.19.3, still no extra menu…

no such tabs exist, maybe its because of the alpha version of web server 1.20alpha1 which was a requirement of the firmware beta.

I got around to adding a fan to my cpu enclosure, and went to check cpu temp, but noticed it has gone missing from the Machine Properties page. I haven't jumped ship to the second beta because of noted issues for corexy, was wondering if this was oversight, me just not knowing where to look etc.

Donald had the right of it, my version was 1.15c, upgraded to 1.17, and shows up as expected, so dc42, great work. Thanks both for quick reply

I thought latest as I updated it all just a few weeks ago, but I'll double check.

Can you do this? Only seen where you can move, but no baby stepping like web interface.

I've had the occasional problem with this also, but for me, I put them mostly on the duet misbehaving, or me,as it only seemed to happen when I turned on the machine, and a clean power cycle cleaned it up. I really haven't had an issue since I finished up my wiring, and I've never seen it fault through multiple prints.

Dc42, yeah, that's what I figured I had to do, thanks for Reply!

Djdemon, as for why, I would like to have octoprint control the power to machine and accessories, again I know I can do it from duet, but show me your timelapse configurations and webcam integration… Can you configure slic3r to also send Gcode files directly to printer? It also goes well with 2 other setups on marlin/OctoPrint I already run, and those features I really love.

I seem to have a problem with duet and octoprint pairing, that being that the duet wants to be powered off of the octoprint usb connection. Can I suppress the duet from trying to run off of the usb power? I am confused about the 5V internal jumper being of help here, so haven't tried that yet.

Would that change for a 24v setup? I did get them working on z/e1, but may look at better ones anyways.

So i'm finishing up the wiring on my corexy, and all is going well except when I tried to run the dual Z motor setup, as only 1 motor will turn at a time, with the other one stalling. I can start the other turning by giving a little assist, but then the other one stalls, only one will turn, the other just stalls. I have validate that they turn in the same direction (still may need to reverse them later with S1/S0 motor setup). I have tried running the motor current up from the default 800ma up to 1.6amp, with the thinking being maybe not enough current, but this didn't help. I also did a full pin swapping around, partially to make them turn in the same direction, but also to see if it had an effect on getting both to turn. As a reference, X/Y work with no issue (haven't hooked up E0 yet).

Motor Specs:
Step angle: 1.8 deg (200 steps per rev)
Number of phase: 2
Rotor inertia: 57gcm^2
Mass: 0.3kg
Resolution in full step mode: 0.04mm per step
Rated Voltage: 12V
Rated Current: 0.48A
Resistance per phase: 25Ohm +/- 10%
Inductance per phase: 50mH +/- 20%
Holding torque: 420mNm
Thrust (full step mode): 8kg (at 300pps)

my config.g (just top portion):
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Fri Sep 22 2017 16:10:34 GMT-0700 (US Mountain Standard Time)

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like marlin output

M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X290 Y300 Z350 S0 ; Set axis maxima

; Endstops
M574 Z0 S0 ; Define active low and unused microswitches
M574 X1 Y1 S1 ; Define active high microswitches
M307 H3 A-1 C-1 D-1
M558 P5 X0 Y0 Z1 H5 F100 T2000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:185 Y15:205 S20 ; Define mesh grid

; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z4000 E420 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X30000 Y30000 Z180 E1200 ; Set maximum speeds (mm/min)
M201 X2000 Y2000 Z250 E250 ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout