MobiFlight / mobiflight-panels

A repository with open source panel designs for flight simulation.
GNU General Public License v3.0
82 stars 53 forks source link

General questions #90

Closed Krakend70 closed 2 years ago

Krakend70 commented 2 years ago

@ssewell Hi I am discovering your work - it is excellent. Thanks !!! Now, I am starting randomly the A32X Illumination folder and the components are a bit strange: For ex., led for backlight are... red ! Is that normal ? Do I have to check all components ?

Many thanks again !

ssewell commented 2 years ago

@Krakend70 The color of the LED to be used should be indicated in the Name field of the BOM image

The LEDs included in the EasyEDA Common Library are somewhat limited, so most of the representations are going to use that generic model (you'll see it as such when viewing a 3D representation of the PCB) and will typically include a "RED" in the footprint, but you should reference the Name field to determine the actual color to be used.

It's been lower on my priorities, but I intend to create a symbol/footprint library that uses a common that doesn't include a color name in the footprint itself.

Krakend70 commented 2 years ago

OK got it, thanks. I finally started by the ECAM project.

Question 1 How do I correct if I find mistakes or suggest improvements or equivalent components ? I suppose that you want any request before change. Example: You mentionned 1k resistor in BOM but in your schema you mentionned 10K (same as 3D colours). Can I change directly in the file on github ?

Question 2 I understood nearly everything (I am not an expert in electronics)- thanks again for all your work - but something remains not totally clear : How do you flag your inputs (and outputs occasionnally) ? I have the 12V input by the jack or the headers, I have the micro usb to the PC (Mobiflight) and that is all ?

PS: No worry about the symbol/footprint common - users have now an explanation in github issues comments

Krakend

ssewell commented 2 years ago

We welcome any contributions or corrections!

In our current workflow, the EasyEDA JSON files are artifacts of the shared workspace in EasyEDA. Unfortunately, the exported JSON files don't lend themselves well to the current diff mechanism in GitHub. The MobiFlight Discord server is a great way to meet up and inquire about gaining access to the MobiFlight EasyEDA team. The #pcb-design channel is fairly active.

Alternatively, you can submit a PR including a description of the changes in the comments (to assist in identifying the changes) and it will be merged into the main branch, post review.

12V will be labeled with a Net Port and 5V will be labeled with either a Net Port or Net Flag (+5V), with varying names, depending on who created the design. Most designs will have a USB input via the on-board Arduino and a 12V input if backlighting is used.

Krakend70 commented 2 years ago

OK thanks for the infos Probably last question about ECAM: Where are the 'External for Switching Panel' headers supposed to be connected to ? Where can I find the info ? Thx

Krakend70 commented 2 years ago

About my last post, I mean the following: Are these headers to be connected with the 'Pedestal Switching Panel', correct ? - By 'Pedestal Switching Panel', I mean the panel highlighted in the attached picture. In that case, how to connect them to this panel ? Furthermore, do you have already drafted such panel and PCB ? If not, do you want me to do it ? It should not be too complex. image

ssewell commented 2 years ago

The ECAM panel provides an interface for three pins per rotary switch on the Switching panel, with the intent of a common GND being shared among the two panels. However, the Switching panel hasn't been developed yet.

Krakend70 commented 2 years ago

got it thx