AX58100

Congrats to that, the debugger is a big big help, for some problems.
As you found out, the variable updates when the program is paused, or stepping.

I have been playing with the inputs and outputs of the card and I realized that these are of type u32 and in order to be used in LCN they must be converted to BITs with the conv_u32_bit component, this is because some pins that LCN automatically creates are of type bit, such as joint.N.amp-fault.in, iocontrol.o.emc.enable-in, or any other pin that has been declared as type bit.

The DAC also works by placing values ​​between 0 and 1020 volts, which gives values ​​between 0 and 3.28 volts at the output. It could be used directly to control the speed of a VFD by scaling it.

You can (or should be able to, is best to say) select your own datatypes.
Starting in eeprom_generator. Then for lcec in ethercat-conf.xml you can select the datatype of the created hal pin.
I don't think every combination is possible or makes sense, but to go from ethercat u32 to hal bit should work. For example.

Regarding the Analog voltage output - yes that was the reason to chose that pin - it is DAC capable.
The STM32 is really picky which pin one selects, they all have special functions and are not interchangeable at all.

COFHAL wrote:

I have been playing with the inputs and outputs of the card and I realized that these are of type u32 and in order to be used in LCN they must be converted to BITs with the conv_u32_bit component, this is because some pins that LCN automatically creates are of type bit, such as joint.N.amp-fault.in, iocontrol.o.emc.enable-in, or any other pin that has been declared as type bit.

This problem is fixed directly in ethercat-conf.xml using the original eeprom.  

ฮาคานโพสต์=316122 userid=22448ขอแสดงความยินดีด้วย โปรแกรมดีบักเกอร์ช่วยได้มากในการแก้ปัญหาบางอย่าง
ดังที่คุณทราบ ตัวแปรจะอัปเดตเมื่อโปรแกรมหยุดชั่วคราวหรือกำลังดำเนินการ

Thanks for the guide.

Next step, I might change the name of pin in u32 index-status; in metalmusings_encoder.comp to match the name of pdo, as I have confused it, and might need to change the data type of one of the parts to match.

Then reconnect the hal.

As I understand it,
when "Obj.IndexStatus" is sent to "pin in u32 index-status" in metalmusings_encoder,
it causes "pin io bit index-c-enable", which is equivalent to the original index-enable, to change the state to 1.
When index-c-enable is triggered, "pin out u32 index-latch-enable" will return to "Obj.IndexLatchEnable" to reset encCnt to 0, waiting to be 1 in the next round.