Posts by Kaiser


    can you tell me where to download this MS Platform builder? I've found one and downloaded from Microsoft but can't install it. I have unzipped it, but haven't found any cerhost/cerdisp sources.
    Is it somewhere to download for free, at all?
    Or couldn't someone send me the neccessary files? That would be great!


    at the moment, I'm using following settings for touch in Registry:

    1. reg open \Hardware\Devicemap\Touch
    2. reg set value Debounce dword 0
    3. reg set value MinCalibrationPointCount dword 5
    4. reg set value PollUpTimeMultiplier dword 1
    5. reg set value TouchSamples dword 2
    7. reg set value Status dword 0

    Best regards, Andy


    I have downloaded the tools cerdisp.exe and cerhost.exe from "Tools/RemoteDisplay" and they work fine.
    I can start cerdisp.exe on display automatically by "cerdisp.exe -c".
    Now I want to start cerhost.exe without always typing in the IP address in dialog and connect automatically to display-IP-address by command line parameter.
    I found another thread where you said there is no support for command line parameter. But there is a possibility to download the source code
    and add command line parameter support by myself. Unfortunately I can't find nowhere the sourcecode.
    Can you tell me where to download or do you have maybe already a new version with that support?
    Thank you...

    Best regards, Andy


    wanted to ask what's about issue 2213?

    1. 0002213: [Touch driver] Touch coordinate depends extremely on the pressure and are very inaccurately on bigger panels

    Some of our customers have problems with the touch. They told me that the touch does not react always when they press.
    Sometimes they have to press up to ten times until they see a reaction.
    I haven't such strong problems but sometimes I also have to press 2-3 times until it works.

    I have seen issue 2213 in the roadmap and would like to ask if there is maybe soon an update which probably solves also my problem?

    Best regards, Andy


    I found a new Kernel (1.30 from 17.7.2017) for NetDCU11.
    Can you tell me what exactly changed?
    Neither in the History nor in the Changes this version is described.



    I don't know how. Customer told me machine was off for one week. After switching on, the password window was visible after switching on the machine.
    Nobody activated that. Customer now is not possible to work because display is locked.
    What do you mean with WCE module? It is a NetDCU11 with WinCE v6.00 installed. (Build 0 on May 15 2014).

    The question now is how to remove that password window? No password is known cause not set.


    a customer switched off the display for about one week.
    Now the switched on the machine and system password is activated.
    The main application is started but no access to it due to password window.
    Now the question, howto reset that? How could this happen?
    Is it resetable or do I have to install the system new completely?

    Thanks a lot.


    Software works fine now. All customers report no problems any more. Thank you.
    Just one question. Could you create the same version with a different date on desktop / in debug of bootloader?
    At the moment I can't distinguish between old and this beta.
    Thanks a lot.

    Best regards, Kaiser

    Hello together,

    do you know if there is a problem with the WriteFile() to serial interface (COM2:) method?
    Used kernel: Build date 15 May 2014

    I have following problem:
    When I use this method extensively, sometimes my complete board freezes because the WriteFile() method does not return any more - it still hangs. Sometimes this happens after a few minutes, sometimes after some hours and sometimes not on a day.

    Now I have tested this with a timer all 20ms sending a string of approx. 30 chars to COM2: and after max. 30min the board freezes - most times much earlier.

    At the moment I'm testing it on an older NetDCU6 board and for the moment it looks ok. I will report if there are some changes.

    Best regards, Kaiser


    I have problems with the calibration points on new 11.2 boards.
    Especially on the right and left side, middle height, I have a divergence about 0.5cm.
    Everywhere else on the screen (top, bottom, middle, the pressed point is correct.
    My touch settings are:

    1. reg open \Hardware\Devicemap\Touch
    2. reg set value Debounce dword 1
    3. reg set value MinCalibrationPointCount dword 10
    4. reg set value PollUpTimeMultiplier dword 5
    5. reg set value TouchSamples dword 5
    6. reg set value MaxCalError dword 25
    8. reg set value Status dword 0

    Does nobody have similar problems?
    I have seen this behaviour on several boards. Also customers are not very lucky with this.
    On old 11 boards there were no such problems.
    At the moment I use 1.28 Kernel with 1.39 bootloader - maybe there is an update?

    Thanks in advance


    I'm trying to trigger a scanner and read the read data over a serial connection.
    Triggering by a short message and reading the data works fine but is very slow.
    After reading the data, I want to trigger again, but I get no result. I have to wait aprox. 200ms Sleep(200). When I trigger after that time, I get a result. When I don't wait, my scanner delivers no data back.
    What could be the problem?
    I assume maybe the timeouts are the problem? But I set it to:
    COMMTIMEOUTS timeouts;
    timeouts.ReadIntervalTimeout = MAXDWORD; // MAXDWORD
    timeouts.ReadTotalTimeoutMultiplier = 0;
    timeouts.ReadTotalTimeoutConstant = 0;
    timeouts.WriteTotalTimeoutMultiplier = 0;
    timeouts.WriteTotalTimeoutConstant = 0;
    and no success.
    I raised the thread priority from THREAD_PRIORITY_NORMAL up to THREAD_PRIORITY_TIME_CRITICAL but also no success.
    Anyone a Idea? I don't know how to speed up my reading.

    Thanks a lot in advance


    I cannot finish the touch calibration after set following properties in the registry.

    1. reg open \Hardware\Devicemap\Touch
    2. reg set value Debounce dword 0
    3. reg set value MinCalibrationPointCount dword 1
    4. reg set value PollUpTimeMultiplier dword 1
    5. reg set value TouchSamples dword 3

    When I finish touch calibration, it starts again in the middle.
    When I clear the registry in the bootloader, I am able to calibrate and save.
    After setting the registry values again to this above, it doesn't word any more.

    Any ideas? With NetDCU 11 there were no problems.

    I have tested it with all parameters seperately. It works only if no parameter is set. If at least one parameter is set, the calibration does not finish.
    When I remove the parameter, it works again. After deleting the registry I have following parameters set:

    For information here is the debug output from the old NetDCU11 board:

    2. TCHPDD: EnableTouchscreen UCB1400
    3. TCHPDD: EnableTouchscreen PASSED

    and here is the debug output from the new NetDCU11.2 not working board:

    2. TCHPDD: EnableTouchscreen WM9715
    3. TCHPDD: EnableTouchscreen PASSED

    The kernel is the latest you send to me:

    1. Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 8 2013 at 17:05:33
    2. NetDCU11 V1.28 - Firmware Init
    3. Copyright (c) 2007 F&S Elektronik Systeme GmbH
    4. Build: Jun 12 2013/16:21:05


    I reviewed my sourcecode and found following out:
    1) The network connection problems start wehen I use the send method. The first few times it works fine but after some sent messages it works slower and slower. After about 4 messages ist takes a few seconds until message is send out, then longer and longer. Later the network connection brakes down.
    2) I assume that the reason are the very short messages I send (about 20Bytes). So I tested following points 3) and 4) but without success.
    3) I tried non blocking mode with

    1. u_long ul = 1U;
    2. int iResult = ioctlsocket(m_ServerSocket, FIONBIO, &ul);

    4) I tried disabling Nagle algorythm (TCP_NODELAY) with

    1. char value = 1;
    2. iResult = setsockopt(m_ServerSocket, IPPROTO_TCP, TCP_NODELAY, &value, 4);

    5) Under NetDCU6 everything works fine - the problems are only on NetDCU11.

    Don't know what I could do to solve this problem. Are there some further ideas?

    Best regards, Kaiser