Hi!

I have a issue with PanelDue. I'm using 3.2 firmware version but I suspect that older firmwares also have the same issue.

Sometimes after reset touchscreen doesn't work at all. I tried to reset LCD plenty of time but it still happen(reset button, not power). I assumed that PanelDue is broken but I tried to reproduce it on second LCD and this issue still exist.
Only solution to make it work is power reset.

Then I released that the printed case is touching a touchscreen all the time. So if something is touching the screen and you reset the screen - touchscreen won't respond.

I prepared instructions and movie how to reproduce it
(https://youtu.be/uh4lXjrA4ks)

• put you finger or two on the touchscreen (all the time)
• in this same time click reset button
• after reset touchscreen won't respond at all

I've started diggind what is going on. It looks that ATSAM microcontroller works fine, but something is wrong with SSD1963. I tried to find schematic, but I found only old version when main microcontroller and display were seperate.

@jayt
Hi, I had similar issues.
Can you give me more information like duet version and firmware version? What browser do you use?

Next time when it occurs, let's check:

1. Try to ping your duet
2. Connect usb cable to your duet and get M122 log
3. Instead of reset you duet just plug again ethernet cable (it should reinit network)

@mackiez

Here you are my configuration files. I hope it will be working well.
I changed a bit extruder so XY maxima are bit smaller than normal.

tpre0.g tpost0.g tfree0.g stop.g sleep.g resume.g pause.g homez.g homey.g homex.g homeall.g config-override.g config.g bed.g

Hi!

You have very old firmware (1.x). This is the reason why your script doesn't work. It is dedicated to newest firrmware (3.x) so you need to upgrade. I prefer use Bossa and USB cable
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

@pavelsplavel
Turn on board -> put jumper on erase pins -> press restart button -> pull off jumper -> press restart button one more time.

After that procedure I hope the microcontroller will erased. If not check your jumper and reset button

@reahax Did you try replace sd card? I compiled (I hope correct version) firmware and checked map file. According to stack in you M122 the issue is reading blocks.

@droftarts
Yes, I posted about this issue
https://forum.duet3d.com/topic/21264/firmware-restart-while-refreshing-dwc-and-pausing

and confirmation
https://forum.duet3d.com/topic/21489/known-issue-unsafe-to-use-external-sd-card-slot

@mikes
I also bought this board from Aliexpress and I wasn't able to run it. After investigation I realized that it is LIS3DSH chip which has different registers than LIS3DH.

AFAIK RRF3 doesn't support LIS3DSH right now.

Take a look on the chip. There is DSH instead of DH.

@Phaedrux internal SD card works great but external SD has issues.

PanelDue is not problem in this case.

I enabled debugPrint in CoreNG and M111 S1 P10 (Storage) in order to find bug.

This log below is while simulating and refreshing DWC (sd_mmc errors)

Read 1 1 97118<LF>
Read 1 1 97119<LF>
Read 1 1 9508<LF>
Read 1 1 97120<LF>
Read 1 1 97121<LF>
Read 1 1 97122<LF>
Read 1 1 97123<LF>
Read 1 1 97124<LF>
Read 1 1 97125<LF>
Read 1 1 97126<LF>
Read 1 1 97127<LF>
Read 1 1 9508<LF>
Read 1 1 97128<LF>
Read 1 1 97129<LF>
Read 1 1 97130<LF>
Read 1 1 97131<LF>
Read 1 1 97132<LF>
Read 1 1 97133<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 35840<LF>
Read 1 1 97134<LF>
Read 1 1 97135<LF>
Read 1 1 9508<LF>
Read 1 1 97136<LF>
Read 1 1 97137<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 35968<LF>
Read 0 1 16384<LF>
Read 0 1 16385<LF>
Read 0 1 35584<LF>
Read 0 1 41088<LF>
Read 0 4 36096<LF>
Read 0 4 41216<LF>
Read 0 4 36100<LF>
sd_mmc_spi_adtc_start: cmd 12, arg 0x00000000, R1 timeout<LF>
<CR>sd_mmc_spi_adtc_start: cmd 12, arg 0x00000000, R1 timeout<LF>
<CR>Read 0 4 41220<LF>
Read 1 1 97138<LF>
Read 1 1 97139<LF>
Read 1 1 97140<LF>
Read 1 1 97141<LF>
Read 1 1 97142<LF>
Read 1 1 97143<LF>
Read 1 1 9508<LF>
Read 1 1 97144<LF>
Read 1 1 97145<LF>

I figured out that ctrl_access.c is vulnerable and two task might have access in the same time so there can be a race condition.

I also noticed that there is support for FreeRTOS but is disabled by default. I enabled FreeRTOS from FreeRTOS project and now it works flawlessly.

I'm testing this solution on my desk now, but I looks promising.
Now I can simulating and refreshing in the same time and I works stable. I can even upload files on internal SD card during simulating from external SD card - it takes a bit longer but it is still stable.

I did this modyfication on 2.05 firmware.

@droftarts
I haven't merged it yet but I'm going to pull request soon if you don't mind.

@phaedrux Thank you!

Hi,

some time ago I bought 5 panel dues (directly from Duet3D, november 2021). One of them has a yellow line. I tried to reflash firmware but it didn't help.

@dc42 Thanks David for fast response and firmware. I've tested with v0.10 and v0.11 Duex and it works great.

@dc42 When will it be implemented? I've bought a few 0.10 and 0.11 duex boards recently. Now I have to manually change the config files for them. In the future it will also be a problem for maintenance.

@jayt
Hi, I had similar issues.
Can you give me more information like duet version and firmware version? What browser do you use?

Next time when it occurs, let's check:

1. Try to ping your duet
2. Connect usb cable to your duet and get M122 log
3. Instead of reset you duet just plug again ethernet cable (it should reinit network)

@mackiez

Here you are my configuration files. I hope it will be working well.
I changed a bit extruder so XY maxima are bit smaller than normal.

tpre0.g tpost0.g tfree0.g stop.g sleep.g resume.g pause.g homez.g homey.g homex.g homeall.g config-override.g config.g bed.g

@mikes
I also bought this board from Aliexpress and I wasn't able to run it. After investigation I realized that it is LIS3DSH chip which has different registers than LIS3DH.

AFAIK RRF3 doesn't support LIS3DSH right now.

Take a look on the chip. There is DSH instead of DH.

@robbe21 Ok, that's weird.
Can you post M122 anyway?

@robbe21
Did you try to replace endstop?

While homing Y axis try to put M122 in DWC console and put here output

@robbe21
Do you get any error/warning in DWC Console?