From: Uzumaki on
Hi friends,

I intend to connect a microcontroller with a desktop PC running Real-time Windows Target (RTWT) via Ethernet (UDP protocol). My question is: How fast can this connection be? For example, if I send a data-request command (from PC) to the microcontroller and then the microcontroller responds (to the PC) with a data packet, what is the total time needed for this process? (I hope this is within ~1ms so that it can be applied in real-time control projects ^^)

Thank you for reading my question. If you have free time please help me to answer it.

Regards,

Uzumaki
From: Assaf Galil on
On May 14, 7:44 am, "Uzumaki " <narutofan01...(a)yahoo.com> wrote:
> Hi friends,
>
> I intend to connect a microcontroller with a desktop PC running Real-time Windows Target (RTWT) via Ethernet (UDP protocol). My question is: How fast can this connection be? For example, if I send a data-request command (from PC) to the microcontroller and then the microcontroller responds (to the PC) with a data packet, what is the total time needed for this process? (I hope this is within ~1ms so that it can be applied in real-time control projects ^^)
>
> Thank you for reading my question. If you have free time please help me to answer it.
>
> Regards,
>
> Uzumaki

Try TenAsys INtime (www.tenasys.com)
The time is set deterministically less than 3 microseconds from the
received interrupt.
From: Uzumaki on
Thank you for your suggestion but I only interest in Real-Time Windows Target.
From: Walter Roberson on
Uzumaki wrote:

> I intend to connect a microcontroller with a desktop PC running
> Real-time Windows Target (RTWT) via Ethernet (UDP protocol). My question
> is: How fast can this connection be? For example, if I send a
> data-request command (from PC) to the microcontroller and then the
> microcontroller responds (to the PC) with a data packet, what is the
> total time needed for this process? (I hope this is within ~1ms so that
> it can be applied in real-time control projects ^^)

First let me say that I have not done real-time work, and do not know
very much about USB, so it could easily be that I missed something:

I looked around the 'net a bit on the topic of USB latency, and it
appears that 6-8 ms is condsidered "good" latency for USB, with 10-15 ms
being common. The figures I found were from people doing MIDI or sound
work; in my experience such people tend to know a lot of tricks and
hacks; if 1 ms could be routinely achieved, they would probably have known.
From: Uzumaki on
Walter Roberson <roberson(a)hushmail.com> wrote in message
>
> First let me say that I have not done real-time work, and do not know
> very much about USB, so it could easily be that I missed something:
>
> I looked around the 'net a bit on the topic of USB latency, and it
> appears that 6-8 ms is condsidered "good" latency for USB, with 10-15 ms
> being common. The figures I found were from people doing MIDI or sound
> work; in my experience such people tend to know a lot of tricks and
> hacks; if 1 ms could be routinely achieved, they would probably have known.

Hi Roberson, I am talking about Ethernet (UDP/IP), not USB. Please read my question more carefully. Thank you for your concern anyways.

Regards,

Uzumaki