Posts by fs-support_ZU

    Hi Didier,


    first - an additional question from my side. Your expansion board where I2C TI PCF8574A is mounted works currently in combination with an ArmstoneA9r3? That's stange! As far as I see (all) previous armStones have no I2C option at all on FC.29, FC.31 (refer HW doc). There is only AIN available. Else please provide me the serial number of ArmstoneA9r3 so that I can double check.


    >>1. can you explain me what AIN stands for, what is its purpose?

    << Analog Input (ADConverter). There are ADS1015 mounted and AIN0...3 available on FC.29, FC.31, FC.33, FC.35.


    >> 2. do we have a one-off board or do all the armStoneMX8MP-V22I-LIN SBC's have this AIN on board?

    >> 3. if all the armStoneMX8MP-V22I-LIN do have AIN on board, is there another armStoneMX8MP variant that does not have the AIN?

    << Part number "armStoneMX8MP-V22I-LIN" do have AIN on board. It is no problem to create a part number with I2C_D option. Please contact our sales office for this purpose.


    >> 4. An alternative is to use another I2C, i.e. I2C4 (on pins 8 / 10). Is this I2C available for our use?

    << Sorry, these pins confugured as SPI in part number "armStoneMX8MP-V22I-LIN"! We have to move some jumpers too in this case to use I2C instead of SPI.

    What is about I2C_C (FC.19, FC21). These pins seems to have the I2C option not UART_B_RTC/CTS;).

    Hi Didier,


    yes this it the right number. So I figure out your baord is configured for AIN not for I2C_D.


    a) You can send use the board(s) as RMA for conversation (add these post as referee).

    b) I can send you conversation instructions in a separate private mail if desired. You have to remove ADS1015 and add two jumpers. Note, warranty voids if you do this.

    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.