yes it works with RC4. Thanks
Posts made by Bravojul
-
RE: RepRapFirmware 2.03RC4 available
I have tried 2.03RC3 with new PrusaSlicer 2.0. Filament used is not recognized. PrusaSlicer now output:
; filament used [mm] = 3363.4
; filament used [cm3] = 7.9It works if I edit the file before sending it to the printer. I change to :
; filament used = 3363.4mm
; filament used [cm3] = 7.9 -
RE: Motors lose steps when heater is on
Do you have the reference for the connector and where I can buy a replacement ?
-
RE: Motors lose steps when heater is on
Thank you David.
Do you think it's fixable ? I didn't really realized it was so severe. It looks like the connector is affected and maybe a capacitor according to the fine white powder around.
-
Motors lose steps when heater is on
hello,
for some days, I am unable to use my CORE XY C-Bot anymore. I experience huge voltage drops from 12V nominal to 9V or even 8V, with alarms appearing on the console. The power supply has been changed to no avail. My bed is powered by the main, so the only current sinks are the 5 motors (X, Y, 2x Z & E) and the hotend (12v E3D v6), plus a fan and a led strip that currently stay off.
The last days here where very hot and I noticed that before the problem arose, the board temperature sensor went to 50°C. Immediately removed the board cover but the problem is still here even if the temp is now reported to be 32°C in operation.I am at a loss to fix that. I don't know if the board is suddendly faulty or if the hotend needs to be changed.
What can I check to assess the problem ?
Thank you
-
RE: Determine real nozzle diameter
I was puzzled to find that Slic3r was dead on horizontal dimensions and Cura was off by several tenth of millimeter. I compared gcode from both and found out that Cura needs a line width of 0.45mm and an extrusion factor of 87.84% to match Slic3r
-
Wifi reconnect options
Hi,
Is there a way to avoid the firmware to stop trying to reconnect in case of losing the Wifi network ?
Every time my wifi router needs to reboot, which can take several minutes in order to reconnect the Wan network, the duet retries several times and then bails out. I then have to reissue a M552 command on the console to make connection great again. I have a macro but it's a PITA to do that every time.
Thanks -
RE: Motor stall detection as Z probe
I was thinking of stall detection to calibrate z probe offset (G31 Z value). Is it possible to do that. I would continue to probe using my inductive sensor.
-
RE: Cannot connect to duet 085
Yesterday I had a problem similar to yours. USB Ok but unable to connect DWC. Until I rebooted my wifi rooter…
-
RE: Problem with homing
Thank you. I was able to have a working homeall.g file by copying and tweaking the one in /sys-CoreXY
Regards -
RE: Problem with homing
G28 in the starting code of a part file abort the print. I have G28; G29 in my slic3r start g-code settings
-
RE: Problem with homing
G28 stops heaters (and print actually) but G28 X0; G28 Y0; G28 Z0 doesn't. There something corrupted with that file.
Now Wifi stopped working :-(((
-
RE: Problem with homing
I have another question : is it normal behavior that G28 turns off heaters ?
In Marlin, you can preheat the nozzle without waiting (with M104) while homing and probing the bed. -
RE: Problem with homing
M555 P2 ; Set firmware compatibility to look like Marlin
I just upgraded from RAMPS / Marlin and thought it would be wise to have compatibility.
-
RE: Problem with homing
I downgraded from 1.18.1 to 1.17e and the problem disappeared
-
RE: Problem with homing
This is really strange. This file works :
[[language]] ; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool on Thu May 18 2017 22:03:21 GMT+0200 (Paris, Madrid (heure d’été)) ; Relative positioning G91 ; Lift Z G1 Z5 F6000 ; Course home X or Y G1 X-325 Y295 F1800 S1 ; Course home X G1 X-325 S1 ; Course home Y G1 Y295 S1 : Move away from the endstops G1 X5 Y-5 F6000 ; Fine home X G1 X-325 F360 S1 ; Fine home Y G1 Y295 S1 ; Absolute positioning G90 G90 ; Go to first bed probe point and home Z G1 X47 Y20 F6000 G30 ; Uncomment the following line to lift the nozzle after probing ;G1 Z5 F100
This file doesn't :
[[language]] ; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool on Thu May 18 2017 22:03:21 GMT+0200 (Paris, Madrid (heure d’été)) ; Relative positioning G91 ; Lift Z G1 Z5 F6000 ; Course home X or Y G1 X-325 Y295 F1800 S1 ; Course home X G1 X-325 S1 ; Course home Y G1 Y295 S1 : Move away from the endstops G1 X5 Y-5 F6000 ; Fine home X G1 X-325 F360 S1 ; Fine home Y G1 Y295 S1 G90 G90 ; Go to first bed probe point and home Z G1 X47 Y20 F6000 G30 ; Uncomment the following line to lift the nozzle after probing ;G1 Z5 F100
Notice the only difference is :
[[language]] ; Absolute positioning
removed in the second file.
Anyway, only one G90 doesn't work for me.
-
RE: Problem with homing
M208 X320 Y290 Z300 S0 ; Set axis maxima
by the way, sending G90 followed by G1 X47 Y20 F6000 manually works as expected
PS : the geometry is CoreXY
-
Problem with homing
Hi,
I am confused by my homeall.g file. I have an inductive probe mounted on the hotend carriage and I want to use it for homing Z.
My X endstop is at 0, my Y endstop is at 290. homeall.g as these 3 lines to home Z :G90
G1 X47 Y20 F6000
G30but the position reading on the console is :
M114
X: 47.000 Y: 290.000 Z: 2.490 E0: 0.0 E1: 0.0 E2: 0.0 E3: 0.0 E4: 0.0 E5: 0.0 E6: 0.0 Count 26960 19440 3984as if the G1 command was executed in relative mode, hiting the Y endstop
What's wrong with the G90 inside homeall.g ?
Regards
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.15a