Error :firmware download for the actuator Siemens 5WG1 512-1AB11 with ETS 3.0f

[sliderem]

I have problem to program an firmware for the actuator Siemens 5WG1 512-1AB11 with ETS 3.0f. I have the following message error:

"An internal error has occurred (Details: authentication failed) Please report this to KNX Association"

I did recently an upgrade to Falcon 2.1 because one of the new components was not working with my software version... can this have an impact?


Thank you in advance for any response...
Sorry that I write in English...

[Klaus Gütter]

Hello,

this happens e.g. if the address of the communication interface collides with some other device in the installation. But there may be other causes; difficult to tell without more details.

Klaus

[sliderem]

Hello,

this happens e.g. if the address of the communication interface collides with some other device in the installation. But there may be other causes; difficult to tell without more details.

Klaus

Thank you for your response!
Normally this has the address 1.1.2 and it is the single one with the address on the network. I can "unload" and "program" very easy the physical address on the device but when I try to download the application program via USB connection I have this exception :
"An internal error has occurred (Details: authentication failed) Please report this to KNX Association"

If I am trying to program via KNX IP connection I have have a different error : the "device did not respond", but I suppose it is a similar error wrapped differently.

[Klaus Gütter]

Maybe you can get some more information about the error by doing a busmon recording while trying to program the device. For a busmon recording you need two interfaces: e.g. USB for recording and IP for downloading.

Klaus

[sliderem]

Maybe you can get some more information about the error by doing a busmon recording while trying to program the device. For a busmon recording you need two interfaces: e.g. USB for recording and IP for downloading.

Klaus

OK I will do try to do that... I have to go at home to activate the bus monitor.... I have also more details about the error as it is presented when you expand details with "error detail button"....

[sliderem]

Maybe you can get some more information about the error by doing a busmon recording while trying to program the device. For a busmon recording you need two interfaces: e.g. USB for recording and IP for downloading.

Klaus

Hello,

I attached the following files :

-The bus monitor telegram record (first file ,renamed to .txt)
-Error details when I am trying to download via USB and via IP interfaces

[sliderem]

Maybe you can get some more information about the error by doing a busmon recording while trying to program the device. For a busmon recording you need two interfaces: e.g. USB for recording and IP for downloading.

Klaus

I re-uploaded the telegrams file....alsoas a TXT (even if it is a CSV)

[Klaus Gütter]

I have some problems matching the different files. Which time zone are you in?
Can you try with a minimal test installation, just the actuator, the interface and a power supply?

[sliderem]

I tried with fresh copy of ETS3f in an virtual machine (to see if it has something to do with the last updates) and no success.


So the error is like this on USB

EDI: Standard USB EDI
Params: Device=0;Path=\\?\hid#vid_0e77&pid_0112#6&2b193a1c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Last messages (cEMI):
  14:09:07.268 S L_DATA.req (ACK-3/) 90 60 0000 1102 00 CE
  14:09:07.300 R L_DATA.con (ACK-3/) B0 60 114D 1102 00 CE
  14:09:07.940 S L_DATA.req (NDT-4/Authorize_Request) 90 60 0000 1102 06 53 D1 00 FF FF FF FF
  14:09:07.990 R L_DATA.con (NDT-4/Authorize_Request) B0 60 114D 1102 06 53 D1 00 FF FF FF FF
  14:09:08.010 R L_DATA.ind (ACK-4/) B0 60 1102 114D 00 D2
  14:09:08.038 R L_DATA.ind (NDT-4/Authorize_Response) B0 60 1102 114D 02 53 D2 00
  14:09:08.040 S L_DATA.req (ACK-4/) 90 60 0000 1102 00 D2
  14:09:08.071 R L_DATA.con (ACK-4/) B0 60 114D 1102 00 D2
  14:09:08.087 S L_DATA.req (NDT-5/PropertyValue_Read) 90 60 0000 1102 05 57 D5 04 0D 10 01
  14:09:08.134 R L_DATA.con (NDT-5/PropertyValue_Read) B0 60 114D 1102 05 57 D5 04 0D 10 01
  14:09:08.156 R L_DATA.ind (ACK-5/) B0 60 1102 114D 00 D6
  14:09:08.205 R L_DATA.ind (NDT-5/PropertyValue_Response) B0 60 1102 114D 0A 57 D6 04 0D 10 01 00 01 98 20 02
  14:09:08.208 S L_DATA.req (ACK-5/) 90 60 0000 1102 00 D6
  14:09:08.242 R L_DATA.con (ACK-5/) B0 60 114D 1102 00 D6
  14:09:08.311 S L_DATA.req (NDT-6/Authorize_Request) 90 60 0000 1102 06 5B D1 00 FF FF FF FF
  14:09:08.361 R L_DATA.con (NDT-6/Authorize_Request) B0 60 114D 1102 06 5B D1 00 FF FF FF FF
  14:09:08.381 R L_DATA.ind (ACK-6/) B0 60 1102 114D 00 DA
  14:09:08.408 R L_DATA.ind (NDT-6/Authorize_Response) B0 60 1102 114D 02 5B D2 00
  14:09:08.410 S L_DATA.req (ACK-6/) 90 60 0000 1102 00 DA
  14:09:08.442 R L_DATA.con (ACK-6/) B0 60 114D 1102 00 DA
  14:09:08.455 S L_DATA.req (NDT-7/PropertyDescription_Read) 90 60 0000 1102 04 5F D8 00 4E 00
  14:09:08.500 R L_DATA.con (NDT-7/PropertyDescription_Read) B0 60 114D 1102 04 5F D8 00 4E 00
  14:09:08.520 R L_DATA.ind (ACK-7/) B0 60 1102 114D 00 DE
  14:09:08.566 R L_DATA.ind (NDT-7/PropertyDescription_Response) B0 60 1102 114D 08 5F D9 00 4E 00 16 00 01 30
  14:09:08.569 S L_DATA.req (ACK-7/) 90 60 0000 1102 00 DE
  14:09:08.602 R L_DATA.con (ACK-7/) B0 60 114D 1102 00 DE
  14:09:08.617 S L_DATA.req (NDT-8/PropertyValue_Read) 90 60 0000 1102 05 63 D5 00 4E 10 01
  14:09:08.680 R L_DATA.con (NDT-8/PropertyValue_Read) B0 60 114D 1102 05 63 D5 00 4E 10 01
  14:09:08.701 R L_DATA.ind (ACK-8/) B0 60 1102 114D 00 E2
  14:09:08.754 R L_DATA.ind (NDT-8/PropertyValue_Response) B0 60 1102 114D 0B 63 D6 00 4E 10 01 00 00 00 00 00 28
  14:09:08.756 S L_DATA.req (ACK-8/) 90 60 0000 1102 00 E2
  14:09:08.791 R L_DATA.con (ACK-8/) B0 60 114D 1102 00 E2
  14:09:08.851 S L_DATA.req (NDT-9/Authorize_Request) 90 60 0000 1102 06 67 D1 00 FF FF FF FF
  14:09:08.901 R L_DATA.con (NDT-9/Authorize_Request) B0 60 114D 1102 06 67 D1 00 FF FF FF FF
  14:09:08.921 R L_DATA.ind (ACK-9/) B0 60 1102 114D 00 E6
  14:09:08.949 R L_DATA.ind (NDT-9/Authorize_Response) B0 60 1102 114D 02 67 D2 00
  14:09:08.953 S L_DATA.req (ACK-9/) 90 60 0000 1102 00 E6
  14:09:08.987 R L_DATA.con (ACK-9/) B0 60 114D 1102 00 E6
  14:09:09.013 S L_DATA.req (NDT-A/PropertyValue_Read) 90 60 0000 1102 05 6B D5 04 05 10 01
  14:09:09.058 R L_DATA.con (NDT-A/PropertyValue_Read) B0 60 114D 1102 05 6B D5 04 05 10 01
  14:09:09.080 R L_DATA.ind (ACK-A/) B0 60 1102 114D 00 EA
  14:09:09.118 R L_DATA.ind (NDT-A/PropertyValue_Response) B0 60 1102 114D 06 6B D6 04 05 10 01 00
  14:09:09.120 S L_DATA.req (ACK-A/) 90 60 0000 1102 00 EA
  14:09:09.165 R L_DATA.con (ACK-A/) B0 60 114D 1102 00 EA
  14:09:09.229 S L_DATA.req (NDT-B/Authorize_Request) 90 60 0000 1102 06 6F D1 00 FF FF FF FF
  14:09:09.278 R L_DATA.con (NDT-B/Authorize_Request) B0 60 114D 1102 06 6F D1 00 FF FF FF FF
  14:09:09.298 R L_DATA.ind (ACK-B/) B0 60 1102 114D 00 EE
  14:09:13.050 S P_GETV.req 00 0100 60
  14:09:13.060 R P_GETV.con 00 0100 60 12
  14:09:15.413 S L_DATA.req (CLR/) 90 60 0000 1102 00 81

[sliderem]

Hello
Lately I did the following tests:

To test for hardware problems:

• I bought a new "Siemens 5WG1 512-1AB11" (anyway I needed another one) installed this by replacing the existing one and, even if initial worked in manual mode, after first tentative to update the application program I faced the same error!
• I tried to unplug all the other KNX components from my network (including the USB Gateway and alternately the IP Gateway) to have only this component on the network! no success either
• I changed the cable that is powering the interface… no success ...the same error


To test for software problems:

• I re-downloaded the VD5 files and reimported them
• I installed a fresh copy of ETS 3f into a virtual machine initially into Windows 7 and later into Windows XP and I executed this from my windows machine… the same error
• I tried this virtual machines also from my MacOSX machine, the connection was OK but the download application error is still
• I even tried form someone an ETS4.0 without any success , I still have an error even if the details are not presented as before

Conclusion is that the software part is seems OK!


What else could I try? Thank you in advance for any idea!