the holy grail...

Oh well... all other devices seem to be ok.

If I now only knew how to transfer that data into the generic xml:).

<!-- EL2004 stoneage manually -->
<slave idx="29" type="generic" vid="00000002" pid="07D43052" name="el2004_dout">
<syncManager idx="0" dir="out">
<pdo idx="1600">
<pdoEntry idx="3001" subIdx="01" bitLen="1" halPin="dout-0" halType="bit"/>
</pdo>
<pdo idx="1601">
<pdoEntry idx="3001" subIdx="02" bitLen="1" halPin="dout-1" halType="bit"/>
</pdo>
<pdo idx="1602">
<pdoEntry idx="3001" subIdx="03" bitLen="1" halPin="dout-2" halType="bit"/>
</pdo>
<pdo idx="1603">
<pdoEntry idx="3001" subIdx="04" bitLen="1" halPin="dout-3" halType="bit"/>
</pdo>
</syncManager>
</slave>

Man, your awesome.

Funny thing though: I just managed to f*** around with TwinCat3 to the extent that the previous ethercat pdos -p now reads like it should in bronze age: it now reads 7000/7010/...

I gets worse: I had just forked the linuxcnc-ethercat stuff, mangled some code (haven't written a line of C in my life) and got it to provide a custom EL2004 setup. While that compiled, I got similar error messages again. Only then did I check pdos....

Well, I'm not complaining... but it is a bit weird;). Twincat3 didn't appear to have done anything...

Edit: Celebrations are a bit early: Output won't actually do something;)

In reply to my own working.

Yes, you can change the firmware (revision) using TwinCat3. One should consider compatibility though. While I was able to make "stone age" think it's rev xxx018 and make it read other index, it does not mean it will actually do shit.

The xml file above - after reset to rev 0000 - works just fine. Beforehand I was unable to actually make it do something (I could read and write registers) but to no physical effect (this is a DO after all).

Splendid - next step: make a BK1120 work;)