Re: [RTnet-developers] Ethernet IP

[Glen W. <gl...@je...>]

My current theory is that with RTNET you need a Connect() to do a Send().

Connect() only works if a socket is not in listen().

Not sure what happens yet if I change the send() to a sentto() if the first
example

On Xenomai , Sent() does not error. it just blocks. On RTAI, it produces an
"oops".

I have extended the pools via RTNET_RTIOC_EXTPOOL to both 30 and 1024 with
no effect on above.


On 2/9/11 9:24 AM, "Jan Kiszka" <jan...@si...> wrote:

> On 2011-02-09 15:18, Glen Wernersbach wrote:
>> Jan,
>> 
>> I think I figured out the send error.
>> 
>> With RTNET I cannot receive and send on the same socket.
>> 
>> So I cannot with RTNET do the follow that works with Linux:
>> 1. Socket
>> 2. SetSocketOpts
>> 3. Bind
>> 4. Listen
>> 5. Accept
>> 6. Recv
>> 7. Send
>> 8. close
>> ------
>> 
>> I can however with RTNET do the following:
>> 1. Socket
>> 2. SetSocketOpts
>> 3. Bind
>> 4. Listen
>> 5. Accept
>> 6. Recv
>> 7. Close
>> ------
>> 8. Socket
>> 9. SetSocketOpts
>> 10. Bind
>> 11. Connect
>> 12. Send
>> 13. Close
>> 
>> The second seemed to work.
>> 
>> Does this makes sense to you?
> 
> Not yet. You once said accept() fails, but your setup starts to diverge
> after recv() (by doing a send()). What errors do which services return?
> Did you check that you have sufficient buffers configured for your
> network load (RTNET_RTIOC_EXTPOOL)?
> 
> Again, it's _much_ easier if you stick this simple setup in a generic
> test case.
> 
> Thanks,
> Jan

-- 
Glen Wernersbach
President & CTO

Jetsoft Development Co.
629 Old St Rt. 74 ­ Suite 210
Cincinnati, Oh 45244
Custom Programming Web Site: www.jetsoftdev.com
Retail Products Web Site: www.scanhelp.com
Phone:   513-528-6660
Fax: 513-528-3470
----
"Support Dyslexia Research"