User Tools
hardware:hardware.mark5c
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
hardware:hardware.mark5c [2013/10/01 05:24] Jamie McCallum created |
hardware:hardware.mark5c [2013/10/02 02:50] (current) Jamie McCallum [Mark5C Configuration] |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| The recording program for the mark5C is called ''drs'' and is (somewhat) compatible with the mark5a/mark5b syntax. The currently installed version is 0.9.9-1 (June 2012 vintage), but a newer version is promised. | The recording program for the mark5C is called ''drs'' and is (somewhat) compatible with the mark5a/mark5b syntax. The currently installed version is 0.9.9-1 (June 2012 vintage), but a newer version is promised. | ||
| - | You can control the software either via the included ''drs_client'' software, or by using ''telnet'' or ''nc'' over port 2620. If you are using nc, please not that all commands need to have a trailing '';'' to be accepted e.g ''echo "vsn?" | nc localhost 2620'' will be rejected while 'echo "vsn?;" | nc localhost 2620'' will return the current VSN. | + | You can control the software either via the included ''drs_client'' software, or by using ''telnet'' or ''nc'' over port 2620. If you are using nc, please not that all commands need to have a trailing '';'' to be accepted e.g ''echo "vsn?" | nc localhost 2620'' will be rejected while ''echo "vsn?;" | nc localhost 2620'' will return the current VSN. |
| One other note - the ''vsn?'' query above would fail if it was issued before setting the ''personality'' of the mark5c - it has no default settings. The usual sequence of commands to bring the mark5c to readiness is | One other note - the ''vsn?'' query above would fail if it was issued before setting the ''personality'' of the mark5c - it has no default settings. The usual sequence of commands to bring the mark5c to readiness is | ||
| Line 51: | Line 51: | ||
| ''pointers?'' works as usual. | ''pointers?'' works as usual. | ||
| - | The time-tag of the recorded data seems to be earlier than expected - it might be that the recorded data comes from a FIFO buffer, or that there were synchronization issues with the DBBC/Fila10G. Also, note that when recording a 4 Gbps that mark5C is allegedly unable to stop a recording reliably - the data stream has to be halted at the Fila10G first. | + | The time-tag of the recorded data seems to be earlier than expected - it might be that the recorded data comes from a FIFO buffer, or that there were synchronization issues with the DBBC/Fila10G. **Update** - it's more likely due to the timing inaccuracy of the Fila10G. From APEX fringe tests, it appears that it's not uncommon for offsets of up to 2 seconds (integer and in either direction) in the recorded data. Happy fringe-finding! |
| + | |||
| + | |||
| + | |||
| + | Also, note that when recording a 4 Gbps that mark5C is allegedly unable to stop a recording reliably - the data stream has to be halted at the Fila10G first. | ||
/home/www/auscope/opswiki/data/attic/hardware/hardware.mark5c.1380605064.txt.gz · Last modified: 2013/10/01 05:24 by Jamie McCallum
Page Tools
