Thanks for your reply.
I think my problem is quite simple: a LXRT task ( acquiring and processing images in real-tme ) runs on the RT-machine ( that schedule only that task, in the future will be a embedded machine mounted on a automatic vehicle ). At the same time I would that the LXRT-task sends the results ( few bytes ) to the other machine ( non RT, running matlab or similar ), that only receive the data ( don't trasmits anything via LAN, is the receive station and is connected only to the RT-machine ). To close the control loop properly, the sending must be real-time.
I' ve written the LXRT code, but if I use the Linux net protocol ( I've do it and all the system works ) then the task is not hard-scheduled ( of course it's forced to soft-real-time); therefore I need something that guarantee me a real time sending, according to LXRT.
I see, using RTnet is an option here.
If the destination address you use for send_rt (i.e. the one passed via connect_rt) is actually listed by rtroute, send_rt should not fail. However, I'm not yet able to track down the return code you mentioned. Is it really -2 (ENOENT)?
"NO SUCH FILE OR DIRECTORY" is the message returned on the console when the task fails ( on send_rt() ). The value returned by the send_rt() is -38.
Ok, 38 means ENOSYS (don't know where that clear-text message comes from), and this in turn could mean that you call send_rt accidentally from soft-real-time mode. Maybe LXRT performed some automatic switching due to a forgotten printf or so.
Jan
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ RTnet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rtnet-users
