Remote connect/debug

    Hello,


    I'm trying to connect and debug my NetDCUA9 board by TCP, but I get no connection -> "Fehler beim Verbinden. Das Gerät ist nicht bereit."

    Im using the tools from NetDCU11/9 called:

    clientshutdown

    CMAccept

    On netDCU11 it works fine.

    But on NetDCUA9 I get no connection. Maybe there are other tools or other version for NetDCUA9 board?


    Thanks, Andy


    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

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Edited 2 times, last by fs-support_ZU ().

    Hello,


    thanks for your answer.

    Of course, I started conmanclient2 and notclientshutdown - sorry.

    But now it seems to work for a while - I don't know why.


    I also added

    Reg set val CoreConOverrideSecurity dword 1

    into registry - maybe this helped.

    Or I had a open connection by US, but I think this wasn't the reason...


    But after some further tests and changed IP address, there is again no connection any more.

    Often, after once connected by USB, also the network connection works.


    What I detected, after start of conmanclient2 a file is generated (514c36bf-c13e-4091-a3a7-1e566227b20d).

    After change of IP address, I have to delete that file, to create a new one. And sometimes after restart, I get a connection.


    Once connected, after restart of all (netdcu and VisualStudio), I always get a connection.

    But first connection with new IP causes problems - seems that restarts after each cahnges help.


    I also found out, the change in registry does not help. I have to start cmaccept anyway.