User:Callahanp: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(→‎'What I'm doing:: February 2018 update)
Line 1: Line 1:
====='What I'm doing: =====
===== What I'm doing: =====
  I am a flight simulation hobbyist currently working on building instruments, gauges, radios and controls for a C172. As of Nov 1, 2017, I've done only a few prototype circuits and have been working to develop skills I'll need to produce a realistic cockpit.  I think I'm ready and it's time to [[Bending Tin| bend tin]].  I'm also working on [[User:Callahanp/Two Way Communication between a Raspberry Pi and Arduinos]]  and [[User:Callahanp/Snippets |Snippets]] of text that may or may not be used somewhere
  I am a flight simulation hobbyist currently working on building instruments, gauges, radios and controls for a C172.
 
As of Feb 1, 2018:
 
* I've done only a few prototype circuits
* have been working to develop skills I'll need to produce a realistic cockpit
* Developing skills in Fusion 360 to support 3d Printing and 3d machine tools.
* Working on tests for a cluster based on Raspberry Pi Zeros
* Beginning to use a 3d Router
* Milling into thin prisms and hand polishing disks of plexiglass for illuminating dials in Sim Instruments
 
 
Recently I began the effort to fully understand the skills needed to contribute to the Flightgear project's codebase.  I know c++ from a course in the early 90's.  I'm looking at Kdevelop and QTquick as development tools.
 
My area of interest is in Flightgear's code includes:
 
* telnet
* phi
* any method to set or get a property
* the property tree itself
* configuration files
* command line parameters
 
I'll be working on the interface between Flightgear and low level hardware in a panel or cockpitIt is my understanding that others, including core flightgear developers are also working on this and my efforts will  follow, derive from, depend on and I hope contribute in some small way to their work.
 
I'm also working on
* [[User:Callahanp/Two Way Communication between a Raspberry Pi and Arduinos]]  
* [https://github.com/callahanp/raspberrypi-zero-usb-ssh-internet/wiki Connecting to a Raspberry Pi Zero via USB Ethernet Including the use of SSH and connection of the zero to the internet ]
* [https://www.raspberrypi.org/forums/viewtopic.php?f=49&t=199994 Creating a cluster with Raspberry Pi Zeros ]
* [[User:Callahanp/Snippets |Snippets]] of text that may or may not be used somewhere


===== Contact =====
===== Contact =====

Revision as of 18:43, 3 February 2018

What I'm doing:
I am a flight simulation hobbyist currently working on building instruments, gauges, radios and controls for a C172.

As of Feb 1, 2018:

  • I've done only a few prototype circuits
  • have been working to develop skills I'll need to produce a realistic cockpit.
  • Developing skills in Fusion 360 to support 3d Printing and 3d machine tools.
  • Working on tests for a cluster based on Raspberry Pi Zeros
  • Beginning to use a 3d Router
  • Milling into thin prisms and hand polishing disks of plexiglass for illuminating dials in Sim Instruments


Recently I began the effort to fully understand the skills needed to contribute to the Flightgear project's codebase. I know c++ from a course in the early 90's. I'm looking at Kdevelop and QTquick as development tools.

My area of interest is in Flightgear's code includes:

  • telnet
  • phi
  • any method to set or get a property
  • the property tree itself
  • configuration files
  • command line parameters

I'll be working on the interface between Flightgear and low level hardware in a panel or cockpit. It is my understanding that others, including core flightgear developers are also working on this and my efforts will follow, derive from, depend on and I hope contribute in some small way to their work.

I'm also working on

Contact

Maybe our projects overlap and maybe I can be of help you in some small way. I love bouncing ideas back and forth in personal or public e-mails. Feel free to contact me about your non-commercial simulation projects.
Email Callahanp through the wiki

I show up occasionally on #flightgear on irc.flightgear.org and am a member of several public forums related to cockpit building.

Callahanp (talk) 09:45, 11 November 2017 (EST)

My Skills
  • Programming in whatever language is available
  • Databases
  • Making the following list of chips do what they do:
  • MCP23XXX Multiplexer
  • MAX7219 Serially Interfaced, 8-Digit LED Display Driver
  • Designing a few types of circuits that work on a breadboard (see electronics below)
My Developing Skills -- Beginner
  • Getting a cokpit project off the ground
  • Very basic machining on a lathe or mill - no significant experience
  • Electronics
  • Designing circuits that make it from breadboard to cockpit.
  • Fusion 360 3dCad
  • OnShape 3d CAD
  • 3d Router
  • Writing Howtos
The Howtos -- Oh yeah... those...

I'm working on these along side building my cockpit. Some of the early attempts were not that useful. My current approach is to build and document actual hardware. I hope this will be more helpful.

Current Projects:

See below for the my personal rules about these howtos going forward. I had to write these because it was becoming a morass and time waster.

The following is yet another work in progress

Writing Advice to Callahanp from Callahanp  or How to write a Howto.

Rule 1. Brevity.

Rule 2. Real Hardware. If I haven't done it yet I'll talk about it on my personal wiki page. That's where stuff like that belongs.

Rule 3. Project Planning, Building Teams, and anything else about developing a hobby project belong elsewhere. If you want to write about these things, go ahead, but don't do it in a Howto on building something specific like a cockpit. If you haven't done the project yet you'll get it wrong. Plus, you'll sound like a...

Rule 4. Grand visions, Vaporware, Abstract thinking, Advice and other nonsense don't belong anywhere.

Rule 5. Get rid of your darlings. Those witty turns of phrase, that elegant prose, the puns, jokes and asides. Fun to write maybe but not so fun to read. They're distractions. These are things a skillful writer can weave into an uninterrupted smooth train of thought but you're not that good a writer. Don't even try,

'nuff said.