@resh said in Duet 2 wifi - Can't connect via USB:

Not sure what I did but I finally got this thing connected and running via DWC. I'd say it had to do with the USB 3.0 or probably if I had a powered hub like others have mentioned.

Glad to hear you got it sorted.

As you have found out the power available from USB ports varies greatly.

Frederick

@Phaedrux said in Issues upgrading to 3.2.2 firmware:

iles, one at a time i

Cool, thanks. I used the tool to create a new config, and then i diffed both configs old and new to see where I forgot something. Machine is moving and not killing itself, and the delta calibration works.

Mesh bed calibration not working yet: Error: G29: No valid grid defined for bed probing

Issue was my M557 command which used a too low S value, I had it set to 5. Now that I set it to 20 it works

@taconite Glad it made a difference. Be aware though that you probably still have some noise on the connections. The changes to DSF just mean that very small glitches are being ignored. So you might want to keep an eye on the logs to see if you are still getting any errors (that are being recovered from).

@antunisac start a new topic and post info about your thermistor and your config

Take a close look at the other chips and see if you can spot and scorched. Sounds kind of like a short took something out.

The firmware version 3.0 file is under 448Kb and you should be able to install it along with the new SDiap file in the 3.0 release. From 3.0 you can upgrade to later versions.

@fcwilt said in Upgrade firmware 2.02(RTOS) to 3.2.2 error:

Hi,

As I recall you have to upgrade first to 3.0.0.

All of the steps are documented somewhere.

Frederick

It works .. Thanks for the Help !

@Marcelofs13 said in Duet 3 busy after homing all:

RepRapFirmware for Duet 3 MB6HC version 3.01-RC9

please update to 3.2.2

(>>) === Diagnostics === (0.000) (>>) RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later (0.000) (>>) Board ID: 08DGM-9T6BU-FG3SS-6J9FD-3S46R-TVSHD (0.000) (>>) Used output buffers: 1 of 20 (3 max) (0.000) (>>) === RTOS === (0.000) (>>) Static ram: 25536 (0.000) (>>) Dynamic ram: 99012 of which 0 recycled (0.000) (>>) Exception stack ram used: 448 (0.000) (>>) Never used ram: 6076 (0.000) (>>) Tasks: HEAT(blocked,1216) MAIN(running,3772) IDLE(ready,200) (0.000) (>>) Owned mutexes: (0.000) (>>) === Platform === (0.000) (>>) Last reset 00:03:38 ago, cause: power up (0.000) (>>) Last software reset time unknown, reason: User, spinning module GCodes, available RAM 6212 bytes (slot 3) (0.000) (>>) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d (0.000) (>>) Error status: 0 (0.000) (>>) Free file entries: 10 (0.000) (>>) SD card 0 detected, interface speed: 20.0MBytes/sec (0.000) (>>) SD card longest block write time: 5.0ms, max retries 0 (0.000) (>>) MCU temperature: min 26.8, current 32.7, max 33.0 (0.000) (>>) Supply voltage: min 23.8, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes (0.000) (>>) Driver 0: standstill, SG min/max 0/348 (0.000) (>>) Driver 1: standstill, SG min/max 0/139 (0.000) (>>) Driver 2: standstill, SG min/max 16/358 (0.000) (>>) Driver 3: standstill, SG min/max not available (0.000) (>>) Driver 4: standstill, SG min/max not available (0.000) (>>) Driver 5: standstill, SG min/max not available (0.000) (>>) Date/time: 1970-01-01 00:00:00 (0.000) (>>) Cache data hit count 413358567 (0.000) (>>) Slowest loop: 10.00ms; fastest: 0.08ms (0.000) (>>) I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0 (0.000) (>>) === Move === (0.000) (>>) Hiccups: 293, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 237, MaxWait: 129054ms, Underruns: 0, 0 (0.000) (>>) Scheduled moves: 12, completed moves: 12 (0.000) (>>) Bed compensation in use: none (0.000) (>>) Bed probe heights: 0.000 0.000 0.000 0.000 0.000 (0.000) (>>) === Heat === (0.000) (>>) Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 (0.000) (>>) Heater 1 is on, I-accum = 0.0 (0.000) (>>) === GCodes === (0.000) (>>) Segments left: 0 (0.000) (>>) Stack records: 2 allocated, 0 in use (0.000) (>>) Movement lock held by null (0.000) (>>) http is idle in state(s) 0 (0.000) (>>) telnet is idle in state(s) 0 (0.000) (>>) file is idle in state(s) 0 (0.000) (>>) serial is ready with "M122" in state(s) 0 (0.000) (>>) aux is idle in state(s) 0 (0.000) (>>) daemon is idle in state(s) 0 (0.000) (>>) queue is idle in state(s) 0 (0.000) (>>) autopause is idle in state(s) 0 (0.000) (>>) Code queue is empty. (0.000) (>>) === Network === (0.000) (>>) Slowest loop: 0.00ms; fastest: 4581298.50ms (0.000) (>>) Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) (0.000) (>>) HTTP sessions: 0 of 8 (0.000) (>>) - WiFi - (0.000) (>>) Network state is disabled (0.000) (>>) WiFi module is disabled (0.000) (>>) Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485 (0.000) (>>) Socket states: 0 0 0 0 0 0 0 0 (0.000) (>>) === Filament sensors === (0.000) (>>) Extruder 0 sensor: ok (0.000) (>>) Extruder 1 sensor: ok (0.000)

Thanks for your help, Seems to be a Safari/ Mac M1 issue. Safari unzipped the download by default must have changed something in the process.

After downloading the Zip on a Rpi4 it worked as expected via the web interface and M115 now reports 3.2.2.

This issue is now resolved.

Latest firmware for Duet 0.8.5 is version 1.26.1 which is similar to RRF 2.05.1 for the later Duets. It's available at https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1. You should read all the upgrade notes between 1.17 and 2.05.1 before upgrading. In particular, mDNS support was removed and that may affect how you access the web interface.

I understand that F3 made a few firmware changes to RRF 2.x on later boards. I don't know whether they made any to 1.17.

@Ralms said in RepRapFirmware 3.2.2 update question:

've noticed that there is no "Duet3and3Firmware-3.2.2.zip" combined file.

I have now added that file and announced the 3.2.2 release. The IAP file is unchanged from firmware 3.2.

You can delete iap4s.bin too, that's used by the Maestro only.

Do you have a DueX in your system? If not, then you don't need the third value. If you do, then create a third sensor with type "drivers-duex" and include that one in your M106 command too.

The drivers do not return actual temperatures, just normal, warning, or overheat status. These are represented as temperatures 0, 100 and 130C.

Ah ok,
This is what i need to know.
If this is normal, all good.
Thank´s guys.

But I'm guessing that is way it was that unreliable?

Please post the results of M122 and M98 P"config.g"
Post your full config.g and your pause and resume macros.

@zapta 😁
Because for example i phone my wife to do this or this on the printer, she see the "Never" button! Lol.

@Chriss said in 3.2.1 2nd toolbord problem...:

@dc42 Thanks David! I still wounder why I have that problem since 3.2.1 only. Exactly with that version to be precise here. The last view prints where fine.

Anyway, I will double check the Can wires and the Signals.

Cheers, Chriss

It wouldn't be the first time that a poor connection just happened to start causing trouble at the same time that a firmware upgrade was installed.

Firmware versions 3.2 and 3.2.1 are compatible as far as CAN protocols are concerned, so if you remain convinced that the issue is connected with installing 3.2.1 then you can try downgrading the tool board firmware, or the main board firmware, or both.

I've installed all the updates one by one. And tried to print something and it seems like everything is working. All of my problems have been resolved after the 3.2 update.

Thank you very much for you're time and you're help.
Cheers
George