Touch

Hello

We are facing troubles with the TOUCH. I can clearly identify that the NetDcuA5 is the cause for the problem, NOT the display or the touch itself.

This did not happen in the past, but we see this problem with new NetDcuA5 used in our production in the last weeks.

Problem is, that the touch doesn't work after power on. After a power off/on, it works.

It also happens that the touch works after the NetDcuA5 had finished booting, but after half an hour or one hour, it stopps working. Everything else is working correctly, only the touch doesn't work. Again, after a power off/on it works. This happens with independend of the connectet touch.

And even if our application is NOT started, if only WCE is running after booting, it is the same: one of every 5 to 10 power on will lead to a not working touch.

This doen't appears with all NetDcuA5, only same, maybe half or a third of the tested NetDcuA5.

If the touch doesn't work, there are no signals on X+/X- or Y+/Y- if the touch is pressed.

If the touch works, signals on X+/X- and Y+/Y- can be seen if the toouch is pressed.

THIS IS AN URGENT MATTER CAUSE WE CAN NOT DELIVER GENERATORS TO OUR CUSTOMERS UNTIL THIS IS SOLVED.

Thank you for looking at this very soon.

Dirk

This are the messages I receive from a NetDcuA5 which shoduring booting:

Microsoft Windows CE Bootloader Common Library Version 1.3 Built Aug 6 2021 12:49:50

Microsoft Windows CE Bootloader for NetDCUA5 Built Apr 22 2024

Portions copyright (c) 2012 F&S Elektronik Systeme GmbH

Boot Loader, Version 2.4

NBoot, Version VN17

HW rev. 1.30

System ready!

Preparing for download...

Press >S< to step into monitor...

AUTO BOOT enabled

HW-Watchdog: ON

Kernel (3385kB) read from flash disk started finished in 611 milliseconds

INFO: OEMLaunch: Jumping to Physical Address 0x8010BB2Ch (Virtual Address 0x0h)...

Jumping to Kernel @ 0x8010BB2C

Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 8 2013 at 17:05:33

INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb

HW-WATCHDOG: ENABLED

NetDCUA5 V3.5 - Firmware Init

Copyright (c) 2013 F&S Elektronik Systeme GmbH

Build: Apr 24 2024/10:40:19

FMD: NAND ID:0xeff10095 --> Winbond: 1GBit (128MB)

FMD: Block 0 to 16 are locked for boot loader

WARNING: SNVS was reset.

I2C: Version 2.5

INFO: No external RTC found!.

OAL: RestartReason=Power On Reset

FMD: NAND ID:0xeff10095 --> Winbond: 1GBit (128MB)

FMD: Block 0 to 16 are locked for boot loader

FSPART: FS partition driver loaded

BINFS: RegisterVolume - Mounted volume '\BINFS'

FS-PM: STARTED

BE2: Version 1.4, ActiveKey = Drivers\Active\01

PSS: Version 1.1, ActiveKey = Drivers\Active\07

FCR: Version 0.6, ActiveKey = Drivers\Active\14

NI2C: Version 1.0, ActiveKey = Drivers\Active\15

ENET: Version 01.04, ActiveKey = Comm\ETHNETA

ENET: Version 01.04, ActiveKey = Comm\ETHNETB

BE2: Version 1.4, ActiveKey = Drivers\Active\18

COMMDD2: Version 1.0, ActiveKey = Drivers\Active\19

UART: Version 1.17, Key = Drivers\Active\19

UART3 RS232 Configured

COMMDD2: Version 1.0, ActiveKey = Drivers\Active\20

UART: Version 1.17, Key = Drivers\Active\20

UART2: Port disabled. Serial debug is on !

COMMDD2: Version 1.0, ActiveKey = Drivers\Active\21

UART: Version 1.17, Key = Drivers\Active\21

TCH: Version 1.6, ActiveKey = Drivers\Active\22

CID: Version 2.8, ActiveKey = Drivers\Active\23

CID: Version 2.8, ActiveKey = Drivers\Active\24

PIF: Version 1.2, ActiveKey = Drivers\Active\25

AIN: Version 1.2, ActiveKey = Drivers\Active\26

EXTRTC: Version 1.1, ActiveKey = Drivers\Active\27

EXTRTC: No external RTC detected

I2C: Version 4.2, ActiveKey = Drivers\Active\28

SDHC: Version 1.2, ActiveKey = Drivers\Active\29

WAV: Version 2.3, ActiveKey = Drivers\Active\31

ETHMAN: Version 1.2, ActiveKey = Drivers\Active\42

BCS: Version 1.4, ActiveKey = Drivers\Active\49

NSPI: Version 3.1, ActiveKey = Drivers\Active\50

DIO: Version 2.9, ActiveKey = Drivers\Active\51

LCD: Version 1.10, ActiveKey = Drivers\Display\LCD

LCD: Read registry settings from Drivers\Display\LCD

LCD: Display-Mode 107, Name ET070001DM6

TchProxy: TouchDriverTimeout=100ms

NDCUCFG V 71 started. Platform: NetDCUA

CheckAutoStart: Version 1.7, LaunchNum = 100

NDCUCFG Open COM1: at 38400 Baud

CreateFile() failed -> ERROR COM1:

Thank you. I will try.

I found out, that the minimum delay between power off and power on must be at least 15 seconds. If this is the case, the touch will work after power on. With a delay of 10 seconds or less the touch will never work after power on. This is not influenced by the additional value in the registry.
But this is not a real problem. If we can be 100% sure that the touch will work every time after booting if the delay between power off and power on was more that 15 seconds it is okay.

Right now, I can not say if it will realy work every time. I only made about 30 tests with a delay of more than 15 seconds. Everytime the touch worked well after booting.

I will run four displays for the whole weekend to see wether the touch is still working on Monday morning or not. Nothing will be done with display or touch during the weekend, it just communicates with our microcontroller board and shows some values. Nobody is here to touch the touch.

Two of the NetDcuA5 have the additional value in their registry, the other two don't have it.

Power supply is fine.

Have a nice weekend.

The touch of all four NetDcuA5 were still working on Monday morning.

Maybe, the touch controller is more sensitive to electromagnetic fields than in the past?
The generator was in standby during the weekend, what means that there had been no disturbances.