Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
gqgmc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Kevin Lyda
gqgmc
Commits
5f7e768d
Commit
5f7e768d
authored
10 years ago
by
Phil Gillaspy
Browse files
Options
Downloads
Patches
Plain Diff
Update README.txt
parent
32d4616d
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.txt
+27
-19
27 additions, 19 deletions
README.txt
with
27 additions
and
19 deletions
README.txt
+
27
−
19
View file @
5f7e768d
...
...
@@ -7,6 +7,7 @@
2. The following list of files need to be downloaded. Obtain them from
the gqgmc folder.
Makefile
Defines.mk
Patterns.mk
...
...
@@ -18,6 +19,8 @@
plotter.hh
plotter.cc
51-gqgmc.rules
3. Create the following subdirectories of your root directory:
bin
libs
...
...
@@ -35,28 +38,33 @@
will be put into bin subdirectory. Try "make all" as the build
command.
6. With the GQ geiger counter connected to your PC via USB and turned
6a. Copy the 51-gqgmc.rules file to the /etc/udev/rules.d directory and
force the reload of udev rules:
sudo cp ./51-gqgmc.rules /etc/udev/rules.d/51-gqgmc.rules
sudo udevadm control --reload-rules
Disconnect the GQ GMC-300 from the computer and then reconnect.
Verify that there exists a /dev/gqgmc in the /dev directory with
read/write permission for all users.
ls -la /dev/gqgmc
6b. With the GQ geiger counter connected to your PC via USB and turned
on, start either bin/gqgmc or bin/gqgmc_gui from a console command
line. However, you must supply the device name of the USB port on
the command line, for example on Ubuntu 11.10 try
"bin/gqgmc /dev/usb/ttyUSB0". On Ubuntu 12.04 try
"bin/gqgmc /dev/ttyUSB0".
You can try to identify USB port using the following scheme.
(a) Before plugging in the GMC-300, run the command "dir /dev/ttyUSB*".
Take note of what, if any, devices are listed. After plugging
in the GMC-300 and turning it on, wait one minute,
then run the command line command "lsusb". You should see a line
with "Prolific Technology Inc." at the end of the line. This
indicates that Linux has successfully recognized and setup a port
for the GMC-300. Now try the command line command "dir /dev/ttyUSB*".
The device name for the GMC-300 should be the newest port added
to the previous listing of the same command. (On Ubuntu 11.10,
try changing /dev/ttyUSB* to /dev/usb/ttyUSB*)
line. The USB device name must be supplied from the command line, e.g.,
bin/gqgmc /dev/gqgmc
bin/gqgmc_gui /dev/gqgmc
The code expects the GQ GMC USB device name to be /dev/gqgmc. This
device name was created at step 6a.
7. The following is a list of prerequisites for successful compilation:
a. Ubuntu Linux 12.04 or 1
1.10
b. GNU g++ 4.6.x compiler installed
a. Ubuntu Linux
11.10,
12.04 or 1
4.04
b. GNU g++ 4.6.x
or more recent
compiler installed
c. Qt4 Software Development Kit (SDK) installed
or Qt Creator installed (required only for GUI)
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment