Posts by Dirk

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.

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.

Thank you. I will try.

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:

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

It is true, the application was hanging in a while loop all the time, and this might block the Storage Manager. I waited for about 30 minutes, but the renaming of a file wasn't stored within this 30 minutes. But it worked when I prevent the application from hanging inthis while loop.

THANK YOU

I found out, that it has something to do with the application running on the NetDCUA5 while I am modifying the files in the FFSDISK directory using the MobileDeviceCenter over the USB. The application does not make changes in the FFSDISK directory, but the exe file of the application is stored in the FFSDISK directory.

I am using NetDCUA5. Problenm is, that I can modify all files stored in the FFSDISK directory, I can change their names, delete them, add new files, but after power on, all modifications are gone. What can I do to keep my modifications in the FFSDISK directory?

THANK YOU

Thank you.

I will try.

Okay, next question:

How to start the "ceplayit.exe" from my own programm?
I like to show short videos and like to start them from inside my own application, and I wish to get back control after the video is finished.

THANK YOU.

It works with wmv-files.

Thank you.

THANK YOU FOR YOUR ANSWER.

I downloaded the "ceplayit.zip" and extracted the "ceplayit.exe".

I copied the exe into the root directorie of the NetDCUA5 and tried to start it by doubleclicking, but nothing happened.

I opened the "Command prompt"and entered the command "ceplayit imgp1486.avi" but nothing happened.

How can I use the ceplayit.exe?

Hello

How can I play videos on a NetDCUA5 with WinCE 6.0?

THANK YOU

We buy about 300 NetDCUA5 every year. We use the version with WinCE 6 on board. The license sticker is always on board and there is no problem so far.
BUT: we have on customer who buys about 10 generators with the NetDCUA5 inside every year. This customer insists that he also receives a written license document. Is it possible to get a license document for WinCE together with the NetDCUA5?

Thanks

We are using NetDcuA5 with WinCE.
We use SD cards to store data which should be available even after power down.

This works fine so far.

My question is: which SD cards can be used?
We have the rule that we have to use SD cards which MUST NOT be SDHC cards, and the maximum allowed capacity is 2GB.
Is this rule correct?
Which SD cards can be used with WinCE?
What is the maximum capacitiy we can use?

THANK YOU

Okay, when using "HKLM\Drivers\builtin\NetDCUA5" I can see CAN1 and CAN2.
I will start to use CAN bus in my application as described in the document.

Thank you

I found a documet

Software Documentation
F&S CAN Driver
Version 2.06
2015 03 23

but this seems to be for the PicoCOM only.
Is there anything like that for the NetDCUA5?

Hello

I want to start using the CAN-Bus interface of the NetDCUA5.
The CAN driver is already existing on the NetDCUA5?

Where do I get a manual about how to activate the driver and how to use it in my application?
Does any example code exist?

THANK YOU

I read the PCN concerning the EOL of the used EON flash.

"We will use Micron MT29F1G08ABADAWP:D in future. Bootloader and BSPs from F&S for WEC6,7,2013 and Linux are supporting this flash since 04/2014."

Does this modification has any influence to form, fit, function of the NetDcuA5?

I tested it and it works. Thank you.
Where can I find and download the Device Driver documentation?

This is a working display setting for an EDT ET0700G8DH6:

reg open \drivers\display\LCD
reg create key mode108
reg set value name string "ET0700G8DH6"
reg set value BLW dword 153
reg set value HSW dword 63
reg set value ELW dword 40
reg set value BFW dword 33
reg set value VSW dword 2
reg set value EFW dword 10
reg set value msignal dword 2
reg set value rows dword 480
reg set value LPP dword 480
reg set value width dword 156
reg set value height dword 96
reg set value contrastenable dword 0
reg set value contrastvalue dword 0
reg set value type dword 6
reg set value config dword 0x00700000
reg set value columns dword 800
reg set value PPL dword 800
reg set value bpp dword 16
reg set value lcdclk dword 33
reg set value EnableCursor dword 0
display mode set 108
reg save