I'm building a library for io-link in Rust and i've used your repository as inspiration.
I do have some questians i would like to ask you. Hope it is okay that i write here as an issue.

I have a problem getting process data from my io-link device and communicating with other Types than Type_0.
I can get 1 byte of procces data by using M-sequence Type_0 in any mode (Startup, Preoperate, Operate).

By reading the M-sequence capability (page 1 of direct parameter) i know what M-sequence Type my device are supporting (Type_2_V).
But when i try to use this Type, my device doesn't respons.
I've calculated the ProcessDataIn and ProcessDataOut length also by reading it from Page 1, so i should be sending the right quantity of octets.

I know that when the device are in Statup Mode it only supports Type_0, so it seems like my device never enters in Operate mode.
The thing is that my device has a green light indicator, which is solid green when in SIO communication, and blinking when in io-link communication. So i tried sending a Fallback(0x5A) mastercommand and the light turned Solid so i assume sending a Operate mode(0x99) command also works.

My questian is:

• How can i know if my device is in Operate mode.
• Do you use Process channel (0x00) in MC message when accessing Process data memory?

Hi,

I would like to get the demo application running, but i ran into a problem that I was not able to solve.
I am using a setup with a Embedded Linux System and a MAX14819 EVKIT. I am able to build and run the stack as well as the demo application on the target, for example I can set the LEDs on the EVKIT.

Here is the problem: The stack initializes and reaches the PREOPERATE_6 status for the attached devices (verified with message 0x9A in the communication trace). All information is transferred correctly from the device (e.g., device ID, vendor ID, etc). After that, I would expect message 0x99 from the master to enter OPERATIONAL state (I have another master demo setup where I can observe this).

However, this message does not appear so the device stays in PREOPERATE_6 and the main loop in the iolink_handler is entered without further activity (other than the timeout printing “.”). The behavior was tested with the two devices from the demo setup (Display IFM E30391 and RFID Reader IFM DTI515) as well as with one IFM proximity sensor (IF 6124).

Is there any kind of message though the internal messaging mechanisms (iolink_app_master.app_event) that the IO link handler expects?