Posts by fs-support_ZU


    if the touch works you can ignore this output. it has definetly nothing to do with the origin problem. Maybe it is caused by the amount of debug output which takes some more time.

    You can increase the timeout under HKLM\System\gwe\touchproxi\driverloadtimeoutms=DWORD:<timeout in ms>.


    and sorry, you are right! I saw that this debug feature and also debug zones are disabled in the current driver. So please try the attached one. It is the latest version. Copy it to ffsdisk and change register value "DLL" to "ffsdisk\...".


    keep in mind - if you use a board with multiple cores you have to do the measurement above for each CPU!

    You can use the SMP functions to do this, like:



    Refer SMP Functions documentation on MS Windows Dev Center.


    use latest device dirver document "play around" with the values, ZXMin/MaxBound(, PNDTPullUp, SetDelay, AdcReadHoldoffHns, ...) . Use also the SX data sheet. Assume a touch dection while low pressure delivers wrong values.

    PS: check also if these values are already implemented in your resent touch driver version ("debug=4" should output the settings during boot on the debug line).

    Hope this helps.


    to get an event from an ordinary button a WM_DOWN and WM_UP from inside the buttom area is required. It would be also interesting which events fail and how far is the distance from the buttons border in this case.

    I do not await that the driver does any mistakes because it gets ready-made values from the SX controler.

    Does recalibration helps?

    Any EMV sources near the touch or SX chip?

    I will also check if there are any registers inside the SX which may bring improvments and come back here.

    Just an update about which OS requires which Visual Studio:

    WEC6R3 WEC7:

    Visual Studio 2005 Standard (c++, .NET CF2.0)

    Visual Studio 2008 Professional (c++, .NET CF3.5)


    Visual Studio 2012/13/15 Professional (c++, .NETCF3.9)

    Windows 10 IoT Core

    Visual Studio 2019 Professional

    To get access to older Visual Studio versions you need a "Microsoft MSDN Subscriptions" license.

    You can use CERHost to connect to your Windows Embedded Compact terminal over Ethernet and display its screens in a window. You can also use the mouse and keyboard on the desktop to remote control the device the same way as if you were using the UI on the device.

    In general device side component is already available on the device. Just launch is by enter "start CERDisp -c". Now launch cerhost on your desktop and select the device you want to conncet.



      (13.29 kB, downloaded 111 times, last: )

      (13.79 kB, downloaded 851 times, last: )

    Hi Hans Kessel,

    step into the bootloader enter "XDS", enter your desired video memory size, reboot - thats all.


    Hello t4science,

    you have to launch "cerdisp" with a command line. This is not possible under HKLM/init! Launch "cerdisp -c" will broadcast the ip-address. Use startup feature (refer DeviceDriverDoc) with cmd or lnk file for do this *or* write an onw program which launches "cerdisp -c".

    As far as i remenber you can also adjust ip-adresse via registry. I will check it and come back.


    because we have the fault on two complete different CPUs (Samsung, NXP) we should check first if Ethernet itself is the problem or just a subsequent fault.

    Is there any serial debug output in case of fault?

    You have no display also not in a test environment - right? Maybe you can deploy a program similar like this out of control?

    Please keep me informed.


    a better solution to get the "first" WCE MAC adddress (= serial number) is use of ndcucfg libraray. The library will by found in the tools-section of the download area. Advantage is, you do not need any information about adapters name or adapter registry path (=platform independent):

    1. #include "ndcucfg_lib.h"
    2. //link against ndcucfg_lib.lib
    3. ...
    4. PSD_TCPIP Data;
    5. memset( &Data, 0, sizeof(Data) );
    6. Data.dwSize = sizeof(PSD_TCPIP);
    7. NETWORK_TYPE type;
    8. DWORD flags;
    9. NDCUCFG_CmdBOOTGetConfigFlags(&flags, &Data, &type);
    10. ....


    one customer asks me how to perform "3. Set taskbar attribute "Auto Hide" and disable attibute "Always on Top" (by right click on none icon area on taskbar ... )" via WCE Registry:



    "Default "=dword:1


    "Default "=dword:0


    FS Device Spy listen to the UDP Broadcasts from the device. You can configure the device side by modify WCE Registry:


    "Dll" = "fs_bcsend.Dll"

    "Prefix" = "BCS"

    "Order" = dword:64

    "Flags"=dword:10 ; DEVFLAGS_LOAD_AS_USERPROC(0x10) ;0x4 -> DEVFLAGS_NOLOAD

    "FriendlyName" = "F&S Broadcast utility"


    "BroadcastDelay"=dword:6 ; in seconds


    Welcome to the Windows CE Telnet Service on FSIMX6UL

    Pocket CMD v 8.00

    \> ndcucfg

    NetDCU Config Utility Ready

    Version: 69

    Build from: Nov 5 2018

    Type help for commands



    reg open

    reg open <key> = HKLM

    reg opencu <key> = HKCU

    reg opencr <key> = HKCR

    reg path


    Another possibility is to use functions from winreg.h.


    if you have more than one SIP installed it is possibel to change the default SIP by modifiy the Registry. SipShowIM() shows/hides always the default SIP.

    The installed SIPs are listed here: HKCU\ControlPanel\SIP\installed\ (refer the CLSID under HKCR\CLSID for details).

    The default SIP is set here: HKCU\ControlPanel\SIP\DefaultIM=<CLSID_of_desired_SIP>.

    Also you can use the OS function: BOOL SipSetCurrentIM(CLSID* pClsid).