Posts made by Shotfire

@alankilian Switched over to a Linux machine running POP_OS and it flashed ok, shows V4 for the version

@alankilian I'm on Windows 10 so I'm not sure how to reproduce what your getting from Linux, on Windows it does show it as a 32kb file

Not sure, I was just following the command line in the WiKi

My sensor is on version 2 and I'm trying to update to version 3
Using latest github download 44a
And, since it successfully erased the chip it won't work at all now
Probably something simple I'm missing but when I try to update the firmware I get this error with or without the ":e" at the end
V1.7 sensor , Adafruit USBtinyISP

***avrdude -p t44 -c usbtiny -U flash:w:FilamentSensor.elf

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e9207
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "FilamentSensor.elf"
avrdude: input file FilamentSensor.elf auto detected as invalid format
avrdude: invalid input file format: -1
avrdude: write to file 'FilamentSensor.elf' failed

avrdude: safemode: Fuses OK

avrdude done. Thank you.***

@dc42 Thanks I will try that.

I've upgraded to 3.0
Duet Wifi 2,

Have everything working, at least I think, except for my Precision Piezo Z-Probe.
X and Y are homing correctly
Z probe is acting odd.

Old Code - that worked fine:
M558 P8 R0.4 H5 I1 F1200 T6000

New Code - Not Working
M558 P8 C"^zprobe.in" R0.04 H5 F1200 T6000

The Dashboard shows Z-Probe "1000" when I tap on it, it immediately goes to "0" then back to "1000"
If I remove the Invert Character "^" the dashboard right after connecting shows "1000".
When I tap on it, it will go to "0" and stays there for about 10 seconds and then goes back to "1000"

Any Ideas?

Thanks DC, Changing Z Jerk to 100 fixed it

Is there anything else in my config that you see that might be a problem now or in the future, maybe something is borderline and is working now but could cause a problem when printing something other than the simple box I'm doing now?

Thanks

DC,
What settings would you suggest for Acc & Jerk?
Thanks

I have a Cartesian printer. There is a very slight multiple hesitations on the X and Y axis, extruder appears ok but is hard to see. At speeds less than 20mm/sec its really hard to visually see but can be seen as a little bit of extra extrusion causing a slight bulge in a long straight run where its building the wall of a box. At speeds above, lets say around 40mm/s to 100mm/s the hesitation is easily seen visually and heard, and can be felt by placing your finger on the carriages as they are moving. It only occurs when using "Bed Mesh Compensation". Works fine with "No Bed Compensation" and with "Auto Bed Compensation"

https://youtu.be/t_yAEmRh_ig

; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;

; General preferences
T0 ; Select first tool
M111 S0 ; Debugging off
G21 ; Work in millimeters
G90 ; Send absolute coordinates…
M82 ; Absolute Extruder moves (Cura)
M555 P1 ; Set firmware compatibility to look like RepRapFirmare

; Axis - Config
M208 X0 Y0 Z0 S1 ; Set axis minimum
M208 X281 Y143 Z140 S0 ; Set axis maximum

; End-stops
M574 X2 Y2 Z0 S0 ; Define active low and unused micro switches
M558 P1 X0 Y0 Z1 H3 F200 T6000 ; Set Z probe type to un-modulated, the axes for which it is used and the probe + travel speeds

; Z - Probe
G31 P500 X-16.6 Y-13.5 Z1.60 ; Set Z probe trigger value, Increase to move head closer to bed, offset and trigger height previous Z0.55

; Bed Compensation
M557 X36.6:216 Y13:140 S20 ; Define mesh grid

; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
;M569 P4 S1 ; Drive 4 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure micro stepping with interpolation
M92 X88.9 Y177.8 Z400 E400.0 ; Set steps per mm (Y is .9deg) (E is geared)
M906 X800 Y1200 Z400 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Movement - Speeds
M566 X600 Y600 Z10 E30 ; Jerk - Set maximum instantaneous speed changes (mm/min)
M203 X15000 Y15000 Z600 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z150 E4000 ; Set accelerations (mm/s^2)

; Heaters
M143 H0 S125 ; Set Maximum Bed Temperature
M143 S260 ; Set maximum heater temperature to 260C
M307 H0 A222.9 C886.5 D4.5 B0 ; Use PID on bed heater (may require further tuning)
M307 H1 A655.3 C237.6 D7.5 B0 P1.0 ; Use PID on heater 1 (may require further tuning)
M305 P0 T110000 B3988 C0 R4700 ; Set thermistor + ADC parameters for bed heater 0
M305 P1 X200 ; Set PT100 Channel Heater 1
M141 H2 ; heater 3 is the chamber heater
M305 P2 R4700 T100000 B3950 ; heater 3 is monitored by a 100K thermistor with B=3950 and a 4.7K series resistor
M301 H2 P-1 ; use bang-bang control for the chamber heater

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Network
M550 PReplicator2x ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP

; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

;M106 P0 S0 H-1 F100 ; Set fan 0 , PWM signal inversion and frequency. Thermostatic control is turned off - FAN
;M106 P1 S1 H1 T50 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on - HS
;M106 P2 S1 H0 T60 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on - Motor

; Custom settings are not configured

; Miscellaneous
M912 P0 S-8.5 ; CPU Temperature Calibration

It started working at about layer 10 and is now updating for the moment, I have no idea why. I didn't do any thing, was just watching it and it started working

Windows 10
Firefox Version - 53.0 32 bit

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.18.1 (2017-04-09)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.15b

I just tried Internet Explorer and it shows the same thing

I spoke to soon,

Layer Statistics are not working and Layer Count is not updating, its stuck on 2.
Object Height, Total Layer Count and Total Filament Usage are now correct.

Link to file that it is printing https://www.dropbox.com/s/wv4ybg55gresa4l/DR2_Doug_duet_wifi_LID_5_May-2017_V1%20v3_With_SuggestedSettings_PetG.gcode?dl=0

Mark,

I just checked and I have it in Config.g
; General preferences
T0 ; Select first tool
M111 S0 ; Debugging off
G21 ; Work in millimeters
G90 ; Send absolute coordinates…
M82 ; Absolute Extruder moves (Cura)
M555 P1 ; Set firmware compatibility to look like RepRapFirmare
Thanks
Doug

@dc42 – Layer counts are working properly after making your code change, Thanks.

@burtoogle --

1. -- I'm using G90 to set the extruder to absolute, is that OK?
2. -- Thanks for the tip on combing, I was experiencing that problem
3. -- And also the tip on Expanding the skin

I'm re-printing now and will see how it turns out,

Thanks

Link to File - https://www.dropbox.com/s/qmof43tgvdw58kx/DR2_Doug_duet_wifi_case_1_May-2017_V1%20v2_PetG.gcode?dl=0

I have put it on my dropbox but I don't use dropbox very much, I think I need your email address to give you access

@burtoogle, No, I'm just printing a a new box for the DuetWif right now. But it happens on every print I do no matter what size or shape

WebControl seems to be displaying inaccurate info while printing.

1. The progress Bar is stuck saying "Layer 2 of 440" and not incrementing ; Cura say theres only 100 layers
2. Filament usage is also way off; Cura says 11.975m WebControl shows 49.2252

Size:
12.8 MiB
Object Height:
110 mm
Layer Height:
0.25 mm / 0.25 mm
Filament Usage:
49225.2 mm
Generated by:
Cura_SteamEngine 2.5.0

–--------------------------------------------------------------
Here's the first part of the code
;FLAVOR:RepRap
;TIME:4651
;Filament used: 11.9751m
;Layer height: 0.2
;Generated with Cura_SteamEngine 2.5.0
M190 S110
M104 S245
M109 S245
;Start of START Code

M561 ; Clear any bed transform
G28 ;Home All Axis
G29 ;Bed Mesh
G90 ; absolute positioning
G92 E0 ; zero extruders
M106 S0 ;Set Cooling Fan to 0
G1 X235 Y3 Z1 F3000 E0.3 ; Position to Wipe
G1 X15 Y3 Z0.3 F3000 E25.00 ; Wipe
G1 E23 F2000
G92 E0 ; zero extruders
;LAYER_COUNT:100
;LAYER:0
M107
G0 F9000 X22 Y15.501 Z0.18
;TYPE:SKIRT

PanelDue is running 7.0-1.16 I don't use a chamber heater but I do monitor the chamber temperature. The webcontrol displays the chamber temperature but the PanelDue does not. Is there something I'm missing?

Interesting solution, I should but one of my RC autopilots on it and see the results. The autopilot already has the Kalman filters in it along with sensor fusion for the Acc's, Gyros, and Magnetometers which will deal with temperature drift of the Gyro's. Might have to remove the Extruder motor to eliminate magnetic interference. Might also be able to calibrate the Magnetometers with the autopilot in the machine to eliminate the effect of the magnets in the motor. Then read the graph real time and see the results.