Re: xPC FIFO blocks behaviour.
- From: Gordon Weast <gweast@xxxxxxxxxxxxx>
- Date: Tue, 04 Apr 2006 14:12:41 -0400
Pablo,
The fifo read block updates the read index after copying characters to
the output port. If you don't change the read index, then nothing is
removed from the fifo storage. You can modify the fifo read to do lots
of different checks that fit your specific need. I suggest you give a
new name to your modified version and point a new block to it. That way
you can still use the old ones.
For instance, the new ascii read header version of fifo read will only
return characters if it finds an entire sequence from the specified
header to the termination string in the fifo. If the sequence isn't
complete, then nothing is removed from the fifo on that time step.
Gordon Weast
xPC Target Development
The Mathworks
Pablo Ausin wrote:
Hi Gordon:.
Last was clear. Now i have a new question about fifo reading. If i do
not manipulate pointer signal (from a FIFO Read block), does it read
from the FIFO?
In my USART at the beginning of each cycle i want to test if the
previous message was sent correctly, otherwise i would like not to
lose bytes by fifo reading in those cases.
Thanks a lot.
- References:
- Re: xPC FIFO blocks behaviour.
- From: Pablo Ausin
- Re: xPC FIFO blocks behaviour.
- From: Gordon Weast
- Re: xPC FIFO blocks behaviour.
- From: Pablo Ausin
- Re: xPC FIFO blocks behaviour.
- Prev by Date: xPC triggered by external clock?
- Next by Date: Re: email code
- Previous by thread: Re: xPC FIFO blocks behaviour.
- Next by thread: problem with divx codec
- Index(es):
Relevant Pages
|