Anyone using PCBs?

[MacFevre]

I wanted to try my hand at making homemade PCBs. Just for fun, really, and seeing if I could do it. I also wanted to try it out for my CDU, as after I made the UFC with just a perf-board, it really looks like a rats nest!

 

I've been looking everywhere for either a Fritzing or Eagle CAD library for a simple tactile switch with an LED. Haven't found one! So I thought I'd try and look for anyone else who has used either of these programs, (or any others,) to create their own PCBs or found a switch with LED?

 

I Haven't found any or seen any PCB creators, so thought I'd ask and see if anyone has made any PCBs or PCB files, or would like to share? Gus shows he's made one for his radios one on his Web site, but it links to a 404 page. I haven't seen anyone else making any.

[metalnwood]

Try this one, designspark.

 

http://www.rs-online.com/designspark/electronics/eng/page/designspark-pcb-home-page

 

I dont use it but have had a quick look at it, it will probably have a better library of components to use as it is done by rs components so if it has a lot of their catalog then you will be happy.

 

Making the pcb is easy enough but if you have to drill all the holes you may not like it by the end.

 

One other option is design your pcb for surface mounted switches, that may be easier for a lot of switches.

[Duckling]

..Gus shows he's made one for his radios one on his Web site, but it links to a 404 page....

 

Ooops. sorry for that, checking up on that one tomorrow..

 

Used Eagle CAD free version for the 7-segment displays on UHF and VHFs, most for fun to see how the process is.

 

Cheers

Gus

[whartsell]

I have made PCBs. With regards to a tactile SW with a LED in it, they are hard to find and very expensive. I just designed my boards with LEDs next to the switch. Not sure how well they work yet. As I haven't had time to fab em yet

[whartsell]

Here you go. http://www.digikey.com/catalog/en/partgroup/tl1240-series/19887

[Gadroc]

I use designspark for the EOS boards. I'll be making some for the MFCDs as well. So much to do and so little time.

[whartsell]

Gadroc, Are you using Flims models for the MFCDs? I have also designed a PCB for them but it sounds like you took a slightly different approach...care to share what you have done? Im gearing up to build a batch ...BTW your EOS boards I fabbed worked great but havent had a chance till the last few weeks to do anything with them due to the little one.

[MacFevre]

Thanks for the idea of using Designspark. Will try it tonight.

 

Gadroc, are you going to be selling your EOS boards, or can you sell me the plans for them? I'm still hoping to consolidate all my different I/O systems into just one system type. I've been waiting for your boards, but would love to try creating them myself if it would make getting it a little sooner.

 

I've got your CMSP panel and it works wonderfully. I'm assuming your EOS boards will come with sketches? (Of course that also makes a huge assumption that it's based on Arduino.) Sorry, but I've been struggling with trying to make my own, and it's simply taking me a really long time to learn. Thanks.

[whartsell]

How many EOS boards you think you need? I'll be having more built soon

[MacFevre]

Hi Whartsell. Not sure, how many inputs will one board take? And does it do output? I've got a few Unos and a couple Megas, but no sketches for them yet. But yes, I can use some more.

[Stevos758]

MacFevre, I plan on doind a UFC build as soon as my double sided copper blank PCB boards show up. I will be trying out eagle cam. I am going to try surface mount LEDs and i got a 100 pack of tactile switches off ebay.

I'll keep you updated. I will be running across the same issues.

 

I have 1mm end mills and .8 and 3mm drills for all of the holes.

 

I plan on using a Teensy 3.1 or a arduino Uno for mine.

 

I still need to figure out how to get the master caution light to work. I'll worry about that later.

 

Here is a video of someone else with the same machine I have. Seems to work awesome!

 

Edited April 8, 2014 by Stevos758

[MacFevre]

Hey Steve, have you checked out Devon Custard's Arduino thread? At http://forums.eagle.ru/showpost.php?p=1975655&postcount=18 he does a Master Caution example.

[Stevos758]

Hey Steve, have you checked out Devon Custard's Arduino thread? At http://forums.eagle.ru/showpost.php?p=1975655&postcount=18 he does a Master Caution example.

Kind of. Not too much yet. I will review. I found an eagle cad component that matches my tactile switched. Ill tinker with it throughout the day when I have time.

[whartsell]

The standard EOS board has 16 digital inputs,16 digital outputs as well as dimmable backlight control and 4 analog inputs. There is also an expansion port that exposes a few outputs as well as the i2c bus (for more I/O). Connectivity is via serial or rs485 (there is a shield circuit that allows you to connect up to 12 to a single arduino Leonardo which is connected to PC via usb)

 

Configuration is done in Helios. There are libs for encoders and such as well

[whartsell]

The boards were intended to be inexpensive as the idea was to use 1 or so per panel

[Gadroc]

EOS boards are essentially low component count arduinos. What they add above and beyond off the shelf arudinos is bus communications (RS-485) and connector standardization. (same connector/headers for serial bus and power on all boards).

 

When I put them together most of the solutions on the market where huge IO count centralized models (OpenCockpit and PHCC). I found two problems with them. First it required running hundreds and hundreds of wires from panels to the central IO solution. While fairly realistic it's a big pain to run and really hard to troubleshoot and fix. Second due to pin configurations on the IO board you often had to run custom break out boards in order to manage wiring. This meant I was paying for PCB fab.

 

The other options on the market where low I/O count boards which where MUCH more expensive per input. Often they also where specialized input (Joystick/Keyboard Emulator) or output boards. Very few combined each. They also ended up consuming a large number of USB slots which becomes problematic.

 

So EOS was conceived to do the following:

1) Standard wiring to each panel being two serial ports for daisy chaining and power.

2) Low cost per panel (<=$25)

3) Small in size so it can be mounted with the panel / instrument

4) Flexible to have multiple form factors (panel vs gauge)

5) Allow for a single connection to the computer per console (left, right and center)

6) Flexible firmware to do many tasks with the same hardware

 

The pin I/O count was specifically chosen to satisfy the majority of all panels in the A-10 pit. I think it will hold true for other aircraft. Those panels which are different can be handled via expansion/daughter boards. (Example MFCDs will use the expansion header and input headers using the flexible firmware to run the MFCDS as a matrix giving enough inputs.)

 

EOS Firmware Library Support Function

1) Analog Inputs

2) Direct Digital Inputs

3) IO Expander Digital Inputs (MCP3017)

4) Digital Outputs

5) IO Expander Digital Outputs (MCP3018)

4) Analog Outputs

5) Servo Outputs

6) Stepper Driver (Only one per board due to interrupt limitations right now)

 

EOS Firmware Library Upcoming Features

1) Rotary Encoder Support

2) Matrix Input Allowing

 

It's very very easy to make these work in a custom sketch (basically create an object and tell it which pins to use). Then Helios can communicate and map input / outputs to the boards.

[Stevos758]

EOS boards are essentially low component count arduinos. What they add above and beyond off the shelf arudinos is bus communications (RS-485) and connector standardization. (same connector/headers for serial bus and power on all boards).

 

When I put them together most of the solutions on the market where huge IO count centralized models (OpenCockpit and PHCC). I found two problems with them. First it required running hundreds and hundreds of wires from panels to the central IO solution. While fairly realistic it's a big pain to run and really hard to troubleshoot and fix. Second due to pin configurations on the IO board you often had to run custom break out boards in order to manage wiring. This meant I was paying for PCB fab.

 

The other options on the market where low I/O count boards which where MUCH more expensive per input. Often they also where specialized input (Joystick/Keyboard Emulator) or output boards. Very few combined each. They also ended up consuming a large number of USB slots which becomes problematic.

 

So EOS was conceived to do the following:

1) Standard wiring to each panel being two serial ports for daisy chaining and power.

2) Low cost per panel (<=$25)

3) Small in size so it can be mounted with the panel / instrument

4) Flexible to have multiple form factors (panel vs gauge)

5) Allow for a single connection to the computer per console (left, right and center)

6) Flexible firmware to do many tasks with the same hardware

 

The pin I/O count was specifically chosen to satisfy the majority of all panels in the A-10 pit. I think it will hold true for other aircraft. Those panels which are different can be handled via expansion/daughter boards. (Example MFCDs will use the expansion header and input headers using the flexible firmware to run the MFCDS as a matrix giving enough inputs.)

 

EOS Firmware Library Support Function

1) Analog Inputs

2) Direct Digital Inputs

3) IO Expander Digital Inputs (MCP3017)

4) Digital Outputs

5) IO Expander Digital Outputs (MCP3018)

4) Analog Outputs

5) Servo Outputs

6) Stepper Driver (Only one per board due to interrupt limitations right now)

 

EOS Firmware Library Upcoming Features

1) Rotary Encoder Support

2) Matrix Input Allowing

 

It's very very easy to make these work in a custom sketch (basically create an object and tell it which pins to use). Then Helios can communicate and map input / outputs to the boards.

 

Very informative! Thanks!

[MacFevre]

OK. I'm sold. What do I need to do or can I do to start using this on my pit? Can I create my own boards or is this a project that we have to wait for? Honestly, I've got time that I can spend on this, is there anything I can do to help? I'm not a programmer, but I try to help in any other way. I don't have a lot of extra money, 2 kids in college,) but I could even try helping financially.

 

The reason I ask is I just really hate to keep creating the I/O system when a system like this is so much better. I mean, I'd definitely like to use this, but really would like to make use of the pit in the near future.

[Stevos758]

OK. I'm sold. What do I need to do or can I do to start using this on my pit? Can I create my own boards or is this a project that we have to wait for? Honestly, I've got time that I can spend on this, is there anything I can do to help? I'm not a programmer, but I try to help in any other way. I don't have a lot of extra money, 2 kids in college,) but I could even try helping financially.

 

The reason I ask is I just really hate to keep creating the I/O system when a system like this is so much better. I mean, I'd definitely like to use this, but really would like to make use of the pit in the near future.

 

Same. My blank PCBs should be here any day.