Duet2 WiFi Firmware on Raise 3d E2 ?

Veti

which firmware file did you use?

Proschi3D

the files you send me

Veti

i did not send you any files

Proschi3D

@Veti sorry I confused you with Jay

Veti

which one did you use? the one from the dropbox or the one from the 3.0 one?

jay_s_uk

the one from dropbox could be 3.0 to be fair. i just built it from their github

Proschi3D

the one from dropbox

Veti

the src says 2.02
https://github.com/Raise3D/Reprap-Raise3D-E2-Series/blob/master/RepRapFirmware/src/Version.h

Proschi3D

then does not flash the return value

Veti

@Proschi78
btw when you says your printer does not work, what do you mean?

there are configuration changes required for going from 2.0 to 3.0

Proschi3D

@Veti the printer no longer starts with firmware 3.0

Veti

it does. you posted the m122 output.

Proschi3D

@Veti (>>) === Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later<LF>Board ID: 08DGM-9T6BU-FG3SS-6J9FD-3S46R-TVSHD<LF>Used output buffers: 1 of 24 (3 max)<LF>=== RTOS ===<LF>Static ram: 30516<LF>Dynamic ram: 91744 of which 68 recycled<LF>Exception stack ram used: 256<LF>Never used ram: 8488<LF>Tasks: NETWORK(ready,1888) HEAT(blocked,1476) MAIN(running,3764) IDLE(ready,156)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:00:15 ago, cause: power up<LF>Last software reset time unknown, reason: User, spinning module GCodes, available RAM 8440 bytes (slot 1)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 26.0, current 28.1, max 28.4<LF>Supply voltage: min 1.4, current 1.5, max 1.6, under voltage events: 0, over voltage events: 0, power good: no<LF>Dr[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

Veti

yes so the printer starts.

Proschi3D

@Proschi78 said in
this is befor updating

Duet2 WiFi Firmware on Raise 3d E2 ?:

(>>) === Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later<LF>Board ID: 08DLM-996RU-N8PS4-7J1D8-3SJ6N-1B9BR<LF>Used output buffers: 1 of 20 (1 max)<LF>=== RTOS ===<LF>Static ram: 25536<LF>Dynamic ram: 99000 of which 0 recycled<LF>Exception stack ram used: 256<LF>Never used ram: 6280<LF>Tasks: HEAT(blocked,1232) MAIN(running,3828) IDLE(ready,200)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:00:40 ago, cause: power up<LF>Last software reset time unknown, reason: User, spinning module GCodes, available RAM 6224 bytes (slot 0)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 18.7, current 23.2, max 23.4<LF>Supply voltage: min 0.0, current 0.6, max 0.9, under voltage events: 0, over voltage events: 0, power good: no<LF>Driver 0: ok, SG[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

Veti

yes, but my statement was, the firmware was updated to 3.0.

there are config changes you need to do as the rrf2 config does not work with rrf3.

see
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files

without those changes you wont be able to move anything.

Proschi3D

I'll keep trying tomorrow, thank you

Proschi3D

the main problem now is that the printer doesn't start anymore.
by start I mean that the display no longer starts up in the menu.
it doesn't finish loading

jay_s_uk

@Proschi78 i guess you need to go back to 2.02 then

Proschi3D

@jay_s_uk that's exactly what I tried.
it just didn't work out.
the board stays at 3.0