User Tools

Site Tools


code:work:lvisf:2020centos8withgui:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
code:work:lvisf:2020centos8withgui:start [2020/02/01 13:42] davidcode:work:lvisf:2020centos8withgui:start [2020/02/13 23:25] (current) – [Malibu Qt Library] david
Line 1: Line 1:
 ====== CentOS 7 with GUI Innovative Development ====== ====== CentOS 7 with GUI Innovative Development ======
 +
 +===== 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 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 <code>
 +sudo bash
 +</code>
 +  - Install a dependent 3rd party utility that is not mentioned in the readme (but doesn't fix the issue) Here is how to install it on CentOS 6<code>
 +yum install wxWidgets-devel
 +yum install wxBase #for /usr/bin/wx-config-3.0
 +cd /usr/bin; ln -s wx-config-3.0 wx-config
 +</code>
 +  - Create the **Makefiles** for the debug and release <code>
 +cd /usr/Innovative/Malibu/Qt
 +/usr/lib64/qt4/bin/qmake -spec /usr/lib64/qt4/mkspecs/linux-g++ -unix CONFIG+=debug -o MakeAllDebug MakeAll.pro
 +/usr/lib64/qt4/bin/qmake -spec /usr/lib64/qt4/mkspecs/linux-g++ -unix CONFIG+=release -o MakeAllRelease MakeAll.pro
 +</code>
 +  - Compile <code>
 +
 +</code>
 +  - For some reason, the Qt path is missing in **Framework_Qt**<code>
 +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../../../../include/QtGui
 +</code>
 +
 +==== Snap ====
  
   - Looks like    - Looks like 
Line 170: Line 202:
 Idx_2=0 Idx_2=0
 Idx_3=0 Idx_3=0
 +</code>
 +
 +==== 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                  | 68                  |
 +^ Connector Part Number 3M part number   | 10268-55H3VC        |
 +^ Mating Connector: 3M part number       | 10168-6000EC (IDC)  |
 +^ Digikey ([[https://www.digikey.com]])  | P/N MPB68A-ND       |
 +^ Cable Innovative part number           | 65057               |
 +
 +MDR68 male to-male, 36 inches (0.91meters)
 +
 +This is the MDR68 as viewed from the front panel.
 +
 +^ Pin  ^ Signal    ^ 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  | 68   | TRIGGER0  |
 +
 +My question to Innovative Tech Support 2020.02.01
 +<code>
 +In Common/ApplicationIo.cpp
 +  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> </code>
code/work/lvisf/2020centos8withgui/start.1580564521.txt.gz · Last modified: 2020/02/01 13:42 by david