code:work:lvisf:2020centos8withgui:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| code:work:lvisf:2020centos8withgui:start [2020/01/29 21:33] – david | code:work:lvisf:2020centos8withgui:start [2020/02/13 23:25] (current) – [Malibu Qt Library] david | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== CentOS | + | ====== CentOS |
| + | |||
| + | ===== Takeaways ===== | ||
| + | |||
| + | * Looks like there is a **pretrigger** now, so we should be able to capture the pulse exactly if we go triggered mode | ||
| + | * The **_Mb** includes are the Malibu library (ahhh) | ||
| ===== Core System ===== | ===== Core System ===== | ||
| Line 66: | Line 71: | ||
| sudo tar -zxvf / | sudo tar -zxvf / | ||
| cd / | cd / | ||
| - | ln -s 64X3-SDF X3-SDF | + | sudo ln -s 64X3-SDF X3-SDF |
| </ | </ | ||
| - Install the firmware from the windows side, for some reason the linux side contains nothing < | - Install the firmware from the windows side, for some reason the linux side contains nothing < | ||
| - | cd / | + | cd / |
| sudo unzip ~/ | sudo unzip ~/ | ||
| </ | </ | ||
| - | - Firmware file is there < | + | - Firmware file is here (or in my VM I put Hardware in top level, so **/ |
| / | / | ||
| # md5sum is | # md5sum is | ||
| Line 92: | Line 97: | ||
| ==== Compile Ourselves ==== | ==== Compile Ourselves ==== | ||
| + | |||
| + | ==== Malibu Qt Library ==== | ||
| + | |||
| + | For our old CentOS 6.5 we need to build the libraries from scratch | ||
| + | |||
| + | - Become root < | ||
| + | sudo bash | ||
| + | </ | ||
| + | - Install a dependent 3rd party utility that is not mentioned in the readme (but doesn' | ||
| + | yum install wxWidgets-devel | ||
| + | yum install wxBase #for / | ||
| + | cd /usr/bin; ln -s wx-config-3.0 wx-config | ||
| + | </ | ||
| + | - Create the **Makefiles** for the debug and release < | ||
| + | cd / | ||
| + | / | ||
| + | / | ||
| + | </ | ||
| + | - Compile < | ||
| + | |||
| + | </ | ||
| + | - For some reason, the Qt path is missing in **Framework_Qt**< | ||
| + | Could manually just add the path to the MakeAllDebug but it appears to overwrite when I run from above | ||
| + | Looks to be missing at least this: -I../ | ||
| + | </ | ||
| + | |||
| + | ==== Snap ==== | ||
| - Looks like | - Looks like | ||
| < | < | ||
| sudo yum install qt-devel | sudo yum install qt-devel | ||
| - | sudo yum install qt3-devel | ||
| </ | </ | ||
| - OK, this worked with just the **qt** as is < | - OK, this worked with just the **qt** as is < | ||
| Line 171: | Line 202: | ||
| Idx_2=0 | Idx_2=0 | ||
| Idx_3=0 | Idx_3=0 | ||
| + | </ | ||
| + | |||
| + | ==== Input Connector JP1 ==== | ||
| + | |||
| + | JP1connector is the front panel connector for the analog inputs, external clock and external trigger inputs. | ||
| + | |||
| + | ^ Connector Type | MDR | | ||
| + | ^ Number of Connections | ||
| + | ^ Connector Part Number 3M part number | ||
| + | ^ Mating Connector: 3M part number | ||
| + | ^ Digikey ([[https:// | ||
| + | ^ Cable Innovative part number | ||
| + | |||
| + | MDR68 male to-male, 36 inches (0.91meters) | ||
| + | |||
| + | This is the MDR68 as viewed from the front panel. | ||
| + | |||
| + | ^ Pin ^ Signal | ||
| + | | 02 | AGND | 36 | AGND | | ||
| + | | 03 | A/D0 IN+ | 37 | A/D0 IN- | | ||
| + | | 04 | AGND | 38 | AGND | | ||
| + | | 10 | AGND | 44 | AGND | | ||
| + | | 11 | A/D1 IN+ | 45 | A/D1 IN- | | ||
| + | | 12 | AGND | 46 | AGND | | ||
| + | | 18 | AGND | 52 | AGND | | ||
| + | | 19 | A/D2 IN+ | 53 | A/D2 IN- | | ||
| + | | 20 | AGND | 54 | AGND | | ||
| + | | 26 | AGND | 60 | AGND | | ||
| + | | 27 | A/D3 IN+ | 61 | A/D3 IN- | | ||
| + | | 28 | AGND | 62 | AGND | | ||
| + | | 32 | AGND | 66 | AGND | | ||
| + | | 33 | EXT CLK+ | 67 | EXT CLK- | | ||
| + | | 34 | TRIGGER1 | ||
| + | |||
| + | My question to Innovative Tech Support 2020.02.01 | ||
| + | < | ||
| + | In Common/ | ||
| + | HandleDirectDataAvailable() | ||
| + | Would that be the place to check the time and if greater than our 60 seconds | ||
| + | - Close the current file | ||
| + | - Set the new file name | ||
| + | - Open the new file name | ||
| + | | ||
| + | and then let it continue? | ||
| + | | ||
| + | seems like the right place to do that? | ||
| </ | </ | ||
code/work/lvisf/2020centos8withgui/start.1580333611.txt.gz · Last modified: 2020/01/29 21:33 by david