Re: Aurora implementation



vt2001cpe,

It seems that if bit errors are not acceptable, as you say, they WILL
happen (if not because of marginal signal integrity of cables,
connectors, etc. then because of EMI/RFI ... in efect "**it happens").

Given a bit error is unavoidable, then that says you MUST use FEC, or a
acknowledge, negative acknowledge (resend) protocol.

A bit error causing the link to loose frame synchronization, or channel
synchronization is something I have not studied for the Aurora core, and
you could email a webcase to ask them exactly that question: "how does
aurora deal with a bit error that may cause frame, or channel
synchronization? Can that even happen?" It may not be possible to
corrupt a 8b/10b character such that you lose sync...after all, it is a
well tried and well thought out old coding (by IBM), and they were
always good at making channel coding such that loss of link sync was not
possible, even at very high error rates...

For example to lose frame sync on a T1 or E1 link requires an error rate
of ~ 1E-3 or worse. Systems are usually designed such that single
isolated bit errors don't cause problems (except to data).

Austin

vt2001cpe wrote:
Here is my potential setup:
1. N-boxes connected to a single box (Spoke to Hub config) via RocketIO
running the simplex Aurora protocol.
2. Each channel would consist of four 3.125Gb/s lanes bonded together.
3. Time aligned samples are transmitted from each spoke to the hub.

Here are my assumptions, please correct me if I am wrong:

1. If my data throughput is less than the max throughput of the link,
the Link Layer will add filler data during the idle periods that will
be stripped out on the receiver side.
2. The elastic buffers on the TX and RX sides are filled and emptied,
respectively, by me.
3. If data were continuously fed into the TX buffer, sent, and
correctly received by the receiver, the RX buffer would not reach an
empty state.
4. I do not have to send alignment characters after the channel has
been successfully initialized.

I am concerned that if a sample took a bit hit, which caused the sample
to be incorrectly interpreted as a idle or alignment character, the
sample would basically be thrown away. This results in my data no
longer being time aligned, which is catastrophic for this application.
Any insight or suggestions? Is it possible to pass all data
transmitted, user data and special characters to the buffers?

Given the number of channels, the length of operation, and the rate of
transmission, I believe bit errors will be unavoidable. Incorrect data
is relatively acceptable, but skewed data is not.

Thanks!

.



Relevant Pages

  • Re: ADC mux charge injection on commercial DAQ boards
    ... This didn't involve any electronics design, ... made a 4 layer PCB anyway to keep analog and digital signals over ... This seemed like a good compromise rather than building buffers into ... channel to another. ...
    (sci.electronics.design)
  • Re: voom for OTA?
    ... On the rear of the receiver, you may find attached a silver box with an RF ... GREEN button (for Options & Settings menu) ... all the locals used by the previous owner are also still stored. ... Regarding the PBS channel, oftentimes these boxes will get enough signal ...
    (alt.tv.tech.hdtv)
  • Re: voom for OTA?
    ... On the rear of the receiver, you may find attached a silver box with an RF ... GREEN button (for Options & Settings menu) ... all the locals used by the previous owner are also still stored. ... Regarding the PBS channel, oftentimes these boxes will get enough signal ...
    (alt.tv.tech.hdtv)
  • Re: Beyond DAB+
    ... That would mean transmitters would have to broadcast both codecs for ... broadcast in a data channel on each multiplex. ... download it is, and what piece of the download it is. ... A receiver could then keep a check on the download channel, ...
    (alt.radio.digital)
  • Re: 5.1 AC3 passthrough
    ... > the DVD menu patch? ... the audio codec is claud.ax and the video codec is clvsd.ax ... > What is a capable WMA PRO receiver? ... no center channel. ...
    (microsoft.public.windows.mediacenter)