
Starting from left to right, the Fireberd 6000A puts out the "Quick Brown Fox" test stream and expects a loopback of the data sent. The Adtran DSU III TDM (two devices in the middle) doesn't really care how the data is formatted as long as it is sent at the correct baud rate and async. In this case it's 2400 baud. The DTech RS232 splitter is kind of a weird device. It has one input port and four output ports but if any of the four split ports responds, like a loopback, the data is only sent back to the input port which of course the IO Ninja Serial Tap received since it was connected inline. The return data is not sent to any of the other four ports so port 1, which is a standard serial com4 port, only sees the incoming data from the input port and not the loopback data which is sent back out of the "input" port. In the future I'll just hook up the IO Ninja to one of the splitter ports so that it doesn't see both TXD and RXD traffic.
Now for the Fireberd, it too is also a kind of weird device when it comes to the "Quick Brown Fox" test. If you hook up the output port of the Firebird directly to a standard serial port on a computer and run putty with the data format of 8,N,1 (any baud rate) the data is off and you can't read the incoming data stream which is "The Quick Brown Fox jumped over the lazy dog 0123456789". If you change the data format to 7,N,2 (any baud rate) on both sides you can then read the test message correctly. Hope that answers your question.
Now one more question please. In the Hex display I have plenty of display real estate left when running the capture and I would like to show more hex information and more of the test stream (all of it if possible) on one line. Is there a way to increase the number of hex bytes and translation to ASCII in order to show more data on one line?
Thanks,
Tom