Posts by fs-support_ZU

    Hello,


    it is a know issue that particular USB Sticks does not work reliable under WCE/WEC! WCE/WEC has just one single driver which fulfill USB specification. Host PC has many drivers available, so OS may find one matches to your stick. We recommend to use only tested brands.


    Assume your USB lines routed adequate for USB high speed: efus design guide. Else in some cases it may help to switch to full speed. Unfortunately this feature is not adjustable via Registry at the time and you need a new driver. Please come back then.


    But I think we have the driver issue in your case, else more sticks would show problems.

    Hello,


    on NetDCUA9 under WEC2013 all files for debugging included into the image. You have to start "conmanclient3" and "cmaccept3".


    On NetDCUA9 under WEC7 you have to start "conmanclient2" (not "clientshutdown") and "cmaccept".

    The files must be copied to the board (also TcpConnectionA.dll, eDbgTL.dll, clientshutdown.exe).

    If it does still not work and you disabled explorer from autostart try to "start explorer" first.


    Commands:

    Code
    1. start explorer
    2. start conmanclient2
    3. start cmaccept

    Ok, thanks for this information.


    FYI:

    we never had any issues while operation with this touch chip/touch driver. If so, I assume there must be big spikes on the power supply.

    While power on we do HW reset the touch chip. While we do this the power supply must be stable.

    Hello Martin,


    as far as I see you already test: HKEY_LOCAL_MACHINE\Services\<Service Name>\Keep=DWORD:1. Does this not work? According the docs it should work! At least "services start FWS0:" should work (it may be case sensitive).




    Think we can ignore Flags|=0x10, it only means the service it loaded into the user mode.


    PS: concerning "autostart" I found following in the source code. This should work:

    // Read registry setting for Autostart Firewall Service

    // [HKEY_LOCAL_MACHINE\COMM\TCPIP\FIREWALL]

    // "FWSAutoStart"=dword:0

    // ; 0 - AutoStart Firewall Service Disabaled/ Default

    // ; 1.- AutoStart Firewall Service Enabled at boot time..


    Hello Dirk,


    please try if the problem persist if you enable the additional SW Reset via Registry:

    reg open \drivers\builtin\netdcua5\touch_tsc2004

    reg set value SWReset dword 1

    reg save


    In the meanwhile I will check if we have some more options via Registry.

    Hello thanks, for you detailed explanation and hint.


    [EDIT] ok think following is nonsense:(

    Anyway, a short comment to your "CreateProcess" above. Netstat is not a command it is an executeable, so maybe following works without showing console:

    BOOL bResult = CreateProcess(T("netstat"), T("-n > NetScan.log"), ...

    Hello, please check the following (if any issues you may use finally the copy command):

    Hello, test following on the cmd shell, it works : (I modify the "echo" sample from here Redirect )


    From your previous answers:

    >> All devices arer configured the same way at production

    >> AutoDST is set to '1'


    I can't believe this. If this is right you should have problems world wide. For example DST date in europe and US are different also some states does not have DST at all! But all devices are in the same time zone. So for me it is obvoius you do anything in Registry or code.


    >> but I do not have access to these devices in Japan :-(.

    << Is it possibel to reproduce the issue in your office? What happens when you do several transitions from "Nov 2nd or 3rd Nov" to later date? While power and power off.

    The four devices which swiched on 3. November are in "Pacific Standard Time" (see HKLM/Timezones/)?

    The time zone of the other is different from this value? I just read the "Japan Standard Time" has no DST since 1951.

    >> the units are not connected to a network since they are running in a hospital due to security reasons.

    << Ok, so we can exclude the time server. But can we be really sure that nobody can plug in the Networkcable? Not even a service technician?


    And what is about "HKEY_LOCAL_MACHINE\Software\Microsoft\Clock\AutoDST". Can you still check this value on the devices which switched DST?

    Hello,


    are all units connected to the Network?

    Assume you set "HKEY_LOCAL_MACHINE\Software\Microsoft\Clock\AutoDST" to zero for all devices?


    I am not sure what happens if you are connected to a Network and time server is active. It should recognize the "AutoDST" flag, but I am not sure if it is so!


    Please check following if time server is runnuing , set Flags to 0x04 (or at least add |= 0x04) and test the behavior of the device in a Network:

    PS: assume on NetDCU11/WCE6 servcer list is a bit different. DST server should not appear.