New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client Software on Linux? #4
Comments
I'll try to setup some Linux builds for you that could be easily downloaded. If you're eager to get it going you could follow the Build From Source instructions for OS X. The The server side was written specifically for the Raspberry Pi's GPIO, so it might run on your Ubuntu box but only in testing mode. |
Thank you, the build worked. Under the client/build/libs folder there is client.jar file, but running it with
I'm not used to running Java on my machine, so my apologies if this is obvious. What we're trying to do is transducer calibration, and all the plumbing is set up just fine with our pressure tank, but I couldn't get any readings from the ADC. What I was doing was just running the ReadPressures.py program (not sure if you wrote that?) while SSH'd into the Pi, but as I said this gave no readings. All the ethernet ports were occupied and hooked up to the ducers, but the raw voltage readings from all the ADCs were zero. I've been looking into this client to see if there's a solution here. |
Did the build produce any files in the The If you follow the Getting Started instructions then it should start the server application that I wrote on the Pi:
The first line will download/install the server software on the Pi. The second line will start the server software. If it starts properly (without any errors) then press You also will need to have the Galactic Aztec Heavy Raspberry Pi Add-on: ADC board plugged into the Pi in order to get ADC readings. Alternatively you could launch the server in Testing mode to at least run with test data, which might help if you are trying to get the client software to connect with the server. |
I attempted to build the project in an Ubuntu Docker and had some trouble with ASCII encoding and dependency changes, so I'll try to resolve the issues and push the changes soon so that you can build the client under Ubuntu. |
After the build, in my client folder I have these folders.
Within classes there are some java class files: But besides that, the folders are pretty sparse. Thanks for attempting the build. There is a Windows laptop, Ryan's, that we're also trying to use, but I'm having networking troubles using it. Simply put, trying to SSH into it using Putty isn't working. I know its static IP is 10.42.0.230, I've got internet and network sharing enabled (it's windows 10), and I've tried when firewall is disabled, but I simply can't connect to it. On my machine, a simple |
Yup, that is the dependency issue I saw as well. I'll try to fix that soon. |
In the meantime: I can run the server on the Pi with the ADC board attached, and run |
The logging simply needs a folder to save logs to, so just make a folder, On Tue, Nov 1, 2016, 4:32 PM Christian Engelbrecht notifications@github.com
|
Ah, perfect. |
One more stupid question: A0 through A5 correspond to LOX, Kero, Motor and Helium (and RCS low and high, but those aren't hooked up right now). Are they in that order? Apologies if this is documented somewhere obvious. I.e is A0 Lox, A1 Kero, etc |
The client software is setup for the following configuration:
But the actual configuration totally depends on how you hook up the Galactic Aztec Heavy Raspberry Pi Add-on: ADC board. The ports on that board are labeled with the A0, A1, etc channels. |
We've hooked it up in that configuration. I just wanted to make sure there wasn't a built in software bias towards a particular line, so if we calibrated the lox ducer while it was hooked up to, say A1, and the software assumed it was a kero ducer, then that would make all sorts of issues I'm sure. |
The software doesn't treat the data any differently on the different channels, so as long as you are consistent (use the same channel for the same transducer when calibrating and when recording data) then you'll be fine. The only thing the software does is display the data differently per channel. Depending on the calibration values that are set in the software it will read different pressures, but it will always record unmodified raw voltage readings. Also, the Galactic Aztec Heavy Raspberry Pi Add-on: ADC has different ADC chips on channels A4 and A5 than A0 through A3 (see specifications for details). Basically, A0 through A3 will be able to read data faster and with more accuracy because those channels are running the higher end ADS1114 chip. |
@CEngelbrecht please try dataacquisitionclient-1.0.1.deb and let me know if it works for you.
|
The dkpg and install went off without a hitch. I can run In the main DataAcquisitionClient folder, running
but I'm assuming this is not a problem. |
I suspect the error you're receiving is related to javafx-maven-plugin issue #124. The javafx-maven-plugin is a tool used to package the project. Running the application directly using I'll push the changes (and add documentation) so that a Linux distribution is part of the releases published to GitHub when updates are made to the project; so that if any changes are made it will be easy for you to update your installation. If I have time I'll look into fixing the launcher error you're seeing, but since it works running it directly with Java, it is pretty low on my list, so it's not likely I'll get to it anytime soon. |
Updated build scripts to include Linux packages in the release cycle (on the latest release page) and added Linux specific documentation to the readme. Also note that all Opened issue #5 to later address the Linux launcher Closing out this issue, feel free to create more issues if you need further assistance. |
Hi Travis, I'm new to the Galactic Aztec Heavy avionics team as of Fall 2016. On my personal PC I'm running Ubuntu, and was wondering if there was a way to get the data acq software to run on my machine.
Regards
Christian
The text was updated successfully, but these errors were encountered: