Response not sent in V2.0.0-RC01

[mkjeff]

Response not sent in V2.0.0-RC01

[Metetron]

Yes, I found the issue. You should not directly access the connection in the ConnectionChanged handler. I don`t know if this is a problem in the library or a difference in behaviour in .Net Framework and .Net Core.

This is the code I wrote to send the S1F13 command in the equipment in the original example:

connection.ConnectionChanged += async (sender, state) =>
{
    Console.WriteLine(state);

    if (state == ConnectionState.Selected)
    {
        var reply = await connection.SendAsync(establishConnectionRequest);
        Console.Write(reply);
    }
};

If you want to send a message on state change, you have to write the code like this, then it works:

connection.ConnectionChanged += async (sender, state) =>
{
    Console.WriteLine(state);

    if (state == ConnectionState.Selected)
    {
        await  Task.Run(() => await connection.SendAsync(establishConnectionRequest));
    }
};

I have built a host, that is used in production with the RC01 version and it is working fine.

[OrangeUtan84]

I can also reproduce this behavior. When I'm using active host and passive equipment and the host sends S1F13 and the equipment replies with S1F14 + MDLN + SOFTREV. But the reply doesn't reach the host and the host waits until T3 timeout.

@Metetron You closed the issue. Could you find out anything to fix this issue?

Kind regards

[OrangeUtan84]

@Metetron Thanks a lot!! After modifying the code to send S1F13 in a new task it worked like charm.