You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using the Enocean U60 USB interface for having the LON-FT communication feature on our i.MX6 platform.
This is working with the lon-stack-ex at the moment. Now I wonder if the lon-stack-dx would be a more actual alternative for us? Now the question: Has anyone tried the lon-stack-dx with the U60 interface on Linux? Is this working (at least theoretically)?
My first tries with added functions in IzoTHal.c and IzoTCal.c are running on the i.MX6 platform with Linux but LON communication is not working yet. The U60 is registered in my system as an own network interface. I try to use sockets on this network interface on port 2541 and receive no communication - although I see the LON-FT traffic on the network interface statistics (packet and byte counts).
Thanks for any hints.
If this is interesting for the community, of cause we will share our additional code we did on the stack.
The text was updated successfully, but these errors were encountered:
We're using the Enocean U60 USB interface for having the LON-FT communication feature on our i.MX6 platform.
This is working with the lon-stack-ex at the moment. Now I wonder if the lon-stack-dx would be a more actual alternative for us? Now the question: Has anyone tried the lon-stack-dx with the U60 interface on Linux? Is this working (at least theoretically)?
My first tries with added functions in IzoTHal.c and IzoTCal.c are running on the i.MX6 platform with Linux but LON communication is not working yet. The U60 is registered in my system as an own network interface. I try to use sockets on this network interface on port 2541 and receive no communication - although I see the LON-FT traffic on the network interface statistics (packet and byte counts).
Thanks for any hints.
If this is interesting for the community, of cause we will share our additional code we did on the stack.
The text was updated successfully, but these errors were encountered: