Help! Uploaded CRC is different (25e2595f vs. expected 2080b701)



  • When uploading smaller parts, I have no issues. But larger ones are giving me this error. Anyone have ideas?
    I'm using Simplify3D for my slicer.

    2/17/2020, 12:31:55 PM Error: Uploaded file CRC is different (25e2595f vs. expected 2080b701)
    2/17/2020, 12:31:55 PM Failed to upload AW1.gcode
    Operation failed (Reason: err 1)

    Here is my current Config if needed.

    M503
    ; Configuration file for Duet 3 (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Feb 16 2020 20:03:50 GMT-0600 (Central Standard Time)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"Duet 3" ; set printer name

    ; Drives
    M569 P0.0 S0 ; physical drive 0.0 goes forwards
    M569 P0.1 S0 ; physical drive 0.1 goes forwards
    M569 P0.2 S1 ; physical drive 0.2 goes backwards
    M569 P0.3 S1 ; physical drive 0.3 goes forwards
    M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
    M350 X128 Y128 Z128 I0 ; configure microstepping without interpolation
    M350 E16 I1 ; configure microstepping with interpolation
    M92 X640.00 Y640.00 Z3200.00 E415.00 ; set steps per mm
    M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X12000.00 Y12000.00 Z1200.00 E3000.00 ; set maximum speeds (mm/min)
    M201 X1000.00 Y1000.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
    M906 X855 Y855 Z855 E855 I30 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X0 Y0 Z0 S1 ; set axis minima
    M208 X200 Y200 Z180 S0 ; set axis maxima

    ; Endstops
    M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io1.in
    M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in
    M574 Z1 S1 P"io3.in" ; configure active-high endstop for low end on Z via pin io3.in

    ; Z-Probe
    M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
    M557 X25:175 Y25:175 S20 ; define mesh grid

    ; Heaters
    M308 S0 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0
    M950 H0 C"out1" T0 ; create bed heater output on out1 and map it to sensor 0
    M143 H0 S60 ; set temperature limit for heater 0 to 60C
    M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
    M140 H0 ; map heated bed to heater 0
    M308 S1 P"temp1" Y"thermistor" T100000 B3988 ; configure sensor 1 as thermistor on pin temp1
    M950 H1 C"out2" T1 ; create nozzle heater output on out2 and map it to sensor 1
    M143 H1 S280 ; set temperature limit for heater 1 to 280C
    M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

    ; Fans
    M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
    M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
    M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
    M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off
    M950 F2 C"out9" Q500 ; create fan 2 on pin out9 and set its frequency
    M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off

    ; Tools
    M563 P0 D0 H1 F-1 ; 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

    ; Custom settings
    M552 S1 P0.0.0.0

    ; Miscellaneous
    M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
    T0 ; select first tool

    M501



  • So this is only happening on my Duet3 board connected via Ethernet. It works fine when uploading and printing to my other machine using a Duet2 Wifi....



  • This was a problem way back in November, before any official firmware was released but I haven't experienced it since then. The CRC error check means that the uploaded file got partly "scrambled" somehow. DC42 will be the one who can give you some definitive advice. Meanwhile please post your firmware version and DWC version. A workaround until you get a better answer than I can give, is to remove the SD card and manually copy the file onto it (into the gcodes folder) using a PC or laptop.



  • Thank you. I appreciate your response! Here is my current firmware:

    FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_VERSION: 3.0beta12

    ELECTRONICS: Duet 3 MB6HC FIRMWARE_DATE: 2019-11-02b1

    Duet Web Control 2.0.7



  • you using an old beta Version i think it make sense that you upgrade your duet to the final rrf 3.0



  • if you're using the card that came with the duet3 i think its set to track the stable repository, you might have to add the unstable if the update instructions doesn't give you a newer firmware.



  • @Shanian79 said in Help! Uploaded CRC is different (25e2595f vs. expected 2080b701):

    Thank you. I appreciate your response! Here is my current firmware:

    FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_VERSION: 3.0beta12

    ELECTRONICS: Duet 3 MB6HC FIRMWARE_DATE: 2019-11-02b1

    Duet Web Control 2.0.7

    Yes that's a very early early firmware - probably circa the time before the issue was fixed. So I'm reasonably confident that if you update it, your problem will go away.



  • @deckingman Thanks! Could you send me a link to the correct firmware I should use? I was going to try updating, but I'm new to much of this and I didn't see anything on Github that was specific to the Duet 3 board, so I didn't want to take a chance.



  • @Shanian79
    RRF3 v3.0 release https://github.com/dc42/RepRapFirmware/releases/tag/3.0
    the Duet2and3Firmware-3.0.zip is common for all boards

    and then if you want to go to the very latest do this afterwards
    https://github.com/dc42/RepRapFirmware/releases/tag/3.01-RC1
    (where you'll find duet3 specific files instead of a bundled zip file)



  • @bearer Thank You!



  • Thank you everyone for your help! I'm back up and running!



  • @Shanian79 Glad you got it sorted.


Log in to reply