# FC-51 Infrared Obstacle Avoidance Proximity Sensors Module **URL:** \ **Category:** parts submit\ **Created:** [July 9, 2017, 5:55pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130 "2017-07-09T17:55:20Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![vanepp](https://forum.fritzing.org/user_avatar/forum.fritzing.org/vanepp/32/4426_2.png) [@vanepp](https://forum.fritzing.org/u/vanepp)\ **Post date:** [July 9, 2017, 5:55pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/1 "2017-07-09T17:55:20Z")
To my suprise there was no part for this common ebay module, nor for the right angle male .1 header that it uses (which was the most difficult part of this to make šŸ™‚ ) so I corrected that. All three views although PCB is minimal. edit: replaced by more correct version below. Peter ---
**Author:** ![KingDarBoja](https://forum.fritzing.org/user_avatar/forum.fritzing.org/kingdarboja/32/3552_2.png) [@KingDarBoja](https://forum.fritzing.org/u/KingDarBoja)\ **Post date:** [March 13, 2018, 9:55pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/2 "2018-03-13T21:55:52Z")
God bless you for making that part, I really needed it for my project. Can you upload it to github repository or shall I do it for you? šŸ˜ƒ ---
**Author:** ![Old\_Grey](https://forum.fritzing.org/user_avatar/forum.fritzing.org/old_grey/32/973_2.png) [@Old\_Grey](https://forum.fritzing.org/u/Old_Grey)\ **Post date:** [March 13, 2018, 10:32pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/3 "2018-03-13T22:32:41Z")
That part was made so long ago it probably doesnā€™t pass Vanā€™s standards. šŸ™‚ It could use a PCB outline. ---
**Author:** ![vanepp](https://forum.fritzing.org/user_avatar/forum.fritzing.org/vanepp/32/4426_2.png) [@vanepp](https://forum.fritzing.org/u/vanepp)\ **Post date:** [March 13, 2018, 11:49pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/4 "2018-03-13T23:49:27Z")
Sure, feel free to submit this improved version @Old_Grey is correct it had a few errors). I intended to do so when I got time, but so far time hasnā€™t appeared ā€¦ [fc-51.fzpz](https://forum.fritzing.org/uploads/default/original/2X/0/0fa250dec25bea8550a12ac98256f5944c3ff552.fzpz) (21.3 KB) Peter ---
**Author:** ![KingDarBoja](https://forum.fritzing.org/user_avatar/forum.fritzing.org/kingdarboja/32/3552_2.png) [@KingDarBoja](https://forum.fritzing.org/u/KingDarBoja)\ **Post date:** [March 14, 2018, 12:19am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/5 "2018-03-14T00:19:55Z")
Thanks! Indeed, I can see the improvements on pcb view, but breadboard can be improved a bit more šŸ˜‰ I do rather want to change the background color, place both smd led on the board and copper stuff on the infrared ones like this [image](https://1.bp.blogspot.com/-2oCKTfNNrnQ/WPkRTQJh7dI/AAAAAAAAA8c/eMQf_qqYcBol8Z6vxjzze6qwC7eCQl-dACLcB/s1600/Arduino-IR-Collision-Detection-Module-Pin-Outs.jpg). ---
**Author:** ![vanepp](https://forum.fritzing.org/user_avatar/forum.fritzing.org/vanepp/32/4426_2.png) [@vanepp](https://forum.fritzing.org/u/vanepp)\ **Post date:** [March 14, 2018, 12:21am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/6 "2018-03-14T00:21:26Z")
Fine by me, go for it! Peter ---
**Author:** ![Old\_Grey](https://forum.fritzing.org/user_avatar/forum.fritzing.org/old_grey/32/973_2.png) [@Old\_Grey](https://forum.fritzing.org/u/Old_Grey)\ **Post date:** [March 14, 2018, 12:27am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/7 "2018-03-14T00:27:57Z")
> [@KingDarBoja](#): > > Thanks! Indeed, I can see the improvements on pcb view, but breadboard can be improved a bit more šŸ˜‰ I do rather want to change the background color, place both smd led on the board and copper stuff on the infrared ones like this image. It would be nice to make everything perfect, but these things change so fast itā€™s probably not worth the time. ---
**Author:** ![KingDarBoja](https://forum.fritzing.org/user_avatar/forum.fritzing.org/kingdarboja/32/3552_2.png) [@KingDarBoja](https://forum.fritzing.org/u/KingDarBoja)\ **Post date:** [March 14, 2018, 12:32am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/8 "2018-03-14T00:32:48Z")
I know most Arduino stuff changes a lot but this part is currently missing from fritzing-parts repository and could be great if it looked like a real one (just minor fixes away). After that, just pull-up request and wait for admins to approve it. šŸ˜ƒ @vanepp If you get time, please make a list with all the parts you have designed so far šŸ˜ƒ ---
**Author:** ![Old\_Grey](https://forum.fritzing.org/user_avatar/forum.fritzing.org/old_grey/32/973_2.png) [@Old\_Grey](https://forum.fritzing.org/u/Old_Grey)\ **Post date:** [March 14, 2018, 12:48am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/9 "2018-03-14T00:48:21Z")
> [@KingDarBoja](#): > > @vanepp If you get time, please make a list with all the parts you have designed so far šŸ˜ƒ I asked him before but he is way too busy trying to make guides to get FZ complied on all platforms. ---
**Author:** ![vanepp](https://forum.fritzing.org/user_avatar/forum.fritzing.org/vanepp/32/4426_2.png) [@vanepp](https://forum.fritzing.org/u/vanepp)\ **Post date:** [March 14, 2018, 1:45am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/10 "2018-03-14T01:45:42Z")
Here is a list from my created\_parts directory. They should all be in the forums somewhere, but are probably (mostly!) not as good as current standard because many predate the creation of the parts check script. Many of them I donā€™t remember making, some of them may not be mine and just in the wrong directory šŸ™‚ . Then there are a bunch of user submitted parts that I have fixed up over the years that arenā€™t in this list (and because they arenā€™t mine, arenā€™t mine to submit to core either). 1x4 Membrane Matrix Keypad.fzpz 3.2in tft touch screen.fzpz 3.5mm switching Jack.fzpz 5-channel flame detector module.fzpz 6 circuit slip ring.fzpz 12circuit slip ring.fzpz 74LVC8T245.fzpz 74x125.fzpz 74x367.fzpz 74x541.fzpz 18650 battery holder.fzpz Ceramic Capacitor top view.fzpz DM860A Stepper Motor Driver.fzpz DC 3.3v-10v TO Ā± 12V Mini DC converter.fzpz DC 3.3v-12v TO Ā± 15V Mini DC converter.fzpz DC 5V TO Ā± 12V Mini DC converter.fzpz DC 5v-12V input to Ā± 12V DC-DC converter.fzpz Electrolytic Capacitor top view.fzpz fc-51.fzpz Goouuu Mini-S1 ESP8266 Nodemcu.fzpz gtm2088argb-21.fzpz hcmmodu0083.fzpz sen136b5b.fzpz HSM-A43 LED Indicator.fzpz IL612-2e.fzpz ITG-3200.fzpz JOYSTICK\_10mm\_fixed\_pcb1.fzpz Keyes l9110 Fan module.fzpz kmr1\_8\_spi\_tft.fzpz KWM-R30881CUAB.fzpz KY-026.fzpz ky-038.fzpz LM386\_fixed.fzpz sheilded\_nomag.fzpz Membrane Matrix Keypad\_mine.fzpz Micro Slide Potentiometer.fzpz Mini-360 DC-DC Buck converter.fzpz MOSFET-NCHANNEL\_fixed.fzpz non-restable\_thermal\_fuse.fzpz nrf24le1 larger (probably not finished as no fzpz file) nrf24le1 small " PH10PIN-2.0MM.fzpz Pololu QTR-8 Reflectabce Sensor array.fzpz roborio.fzpz Rotary\_Switch\_4x1.fzpz S-350-60 Power Supply.fzpz SBX DSUN.fzpz sct-013.fzpz Shortened\_LED.fzpz SMA Antenna Connector.fzpz soic20.fzpz STEF12 fuse.fzpz Stereo POT.fzpz SWITCH-DPDT-latching.fzpz tlp185.fzpz TLV431.fzpz TO-220-2lead.fzpz TO-220-3lead.fzpz TO220-4lead.fzpz top View TO-92.fzpz tp4056.fzpz VA250LA40BP.fzpz Vex Voltage regulator module\_improved.fzpz Wemos ESP-Wroom-02.fzpz Wemos lolin32.fzpz xr10910\_qfn40.fzpz Peter ---
**Author:** ![Old\_Grey](https://forum.fritzing.org/user_avatar/forum.fritzing.org/old_grey/32/973_2.png) [@Old\_Grey](https://forum.fritzing.org/u/Old_Grey)\ **Post date:** [March 14, 2018, 6:16am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/11 "2018-03-14T06:16:56Z")
> [@KingDarBoja](#): > > I know most Arduino stuff changes a lot but this part is currently missing from fritzing-parts repository and could be great if it looked like a real one (just minor fixes away). After that, just pull-up request and wait for admins to approve it. šŸ˜ƒ If its going to Git and everyones is going to get, yes, by all means make it good. Itā€™s about time to draw a line in that sand and make all parts good from now on. ---
**Author:** ![KingDarBoja](https://forum.fritzing.org/user_avatar/forum.fritzing.org/kingdarboja/32/3552_2.png) [@KingDarBoja](https://forum.fritzing.org/u/KingDarBoja)\ **Post date:** [March 14, 2018, 11:15pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/12 "2018-03-14T23:15:16Z")
Yes, of course it is going to be on github repository. I already got approved the next fritzing parts which you have been helping me along with vanepp: - Seeedstudio LinkIt One Board - XL4016 DC-DC Converter - IFR520 MOSFET module You can check those looking at the commit log [here](https://github.com/fritzing/fritzing-parts/commits/master) (search for KingDarBoja). ---
**Author:** ![KingDarBoja](https://forum.fritzing.org/user_avatar/forum.fritzing.org/kingdarboja/32/3552_2.png) [@KingDarBoja](https://forum.fritzing.org/u/KingDarBoja)\ **Post date:** [March 19, 2018, 2:22am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/13 "2018-03-19T02:22:50Z")
Updated part, I just changed the breadboard view component to make it look like the real one šŸ˜ƒ [fc-51\_IR\_Sensor.fzpz](https://forum.fritzing.org/uploads/default/original/2X/f/f396d1854d75df10e94240be64073afbe05107d3.fzpz) (24.9 KB) ---
**Author:** ![vanepp](https://forum.fritzing.org/user_avatar/forum.fritzing.org/vanepp/32/4426_2.png) [@vanepp](https://forum.fritzing.org/u/vanepp)\ **Post date:** [March 19, 2018, 9:00pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/14 "2018-03-19T21:00:58Z")
Very nice! You are much better at the breadboard graphics than I am (usually when part of one of mine looks like this itā€™s because I have copied it from someone more skillful šŸ™‚ ) and thatā€™s a big help as it makes the parts look more lifelike! Peter ---
**Author:** ![KingDarBoja](https://forum.fritzing.org/user_avatar/forum.fritzing.org/kingdarboja/32/3552_2.png) [@KingDarBoja](https://forum.fritzing.org/u/KingDarBoja)\ **Post date:** [March 19, 2018, 10:25pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/15 "2018-03-19T22:25:31Z")
Thanks šŸ˜Š Since there isnā€™t any mistake, I will do a pull-up request to github repository in some hours (to let you spot any problem at time). Also, I noticed you fixed a Raspberry Pi Zero Fritzing part but the related issue isnā€™t closed at the repository, would be nice if the devs could clean the solved issues. For last, I will start a new topic listing all the Fritzing parts so far with their current etiquettes so the whole community can help to fix the ones mistaken and check for the appropriate .fzb ---
**Author:** ![vanepp](https://forum.fritzing.org/user_avatar/forum.fritzing.org/vanepp/32/4426_2.png) [@vanepp](https://forum.fritzing.org/u/vanepp)\ **Post date:** [March 19, 2018, 11:04pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/16 "2018-03-19T23:04:24Z")
> [@KingDarBoja](#): > > Thanks šŸ˜Š Since there isnā€™t any mistake, I will do a pull-up request to github repository in some hours (to let you spot any problem at time). I ran it through the parts check script and it came up clean and I didnā€™t see any problems that the script may not find when I looked at the svgs, so I think itā€™s fine. > [@KingDarBoja](#): > > Also, I noticed you fixed a Raspberry Pi Zero Fritzing part but the related issue isnā€™t closed at the repository, would be nice if the devs could clean the solved issues. While that is true, I suspect the issue is that all the free time he has is going in to checking (and modifying where needed) new parts to add and working on the new web based code base. That leaves little time for closing solved issues. I have similar mods for the rest of the PI parts that I havenā€™t yet gotten around to submitting so I can sympathize with the problem šŸ™‚ . > [@KingDarBoja](#): > > For last, I will start a new topic listing all the Fritzing parts so far with their current etiquettes so the whole community can help to fix the ones mistaken and check for the appropriate .fzb That may be worthwhile, but the list just in core parts is very very long (the check script can be used to process the all the parts in the core directory and list their problems). It is possible that Iā€™ll switch back to doing some more work on the check script to add some mods to make it work in the Mac and add the check for the scale as a warning and then start fixing core parts as being a useful thing to do which ever direction (current code base, new web based code base, or nothing) turns out to be the way forward. What ever happens properly made parts are going to be an advantage. That said, fixing the parts requires a good knowledge of how to fix the parts and as you have seen that isnā€™t that easy to aquire. While Iā€™d love to be wrong, I donā€™t think we have a lot of people with that knowledge, interest and time to do the work from what Iā€™ve seen so far. I think a good next step would be to figure out and document how the ā€œreplace an existing part with an updated oneā€ is supposed to work (which likely will take research in to the obsolete parts bin and the source). If that was documented it may make parts update less work for el-j and free up some of his time which appears to be currently split too many ways. I figure the place to start on parts is with the most popular ones (which is why I started with the Raspberry PI series) and specifically the Zero when an update broke it. However even when I submitted it (because I didnā€™t and donā€™t yet know how to) make the old part obsolete el-j had to modify my original part to do that which burned yet more of his scarce time for Fritzing. Follwinig the PI parts I think the arduino parts (some of which have errors) should probably be the next on the list. Followed by any in the github issues list that point to core parts that are broken (usually in pcb view) of which I know a couple. Iā€™d suggest starting your list fairly small with much used parts and see if you can find anyone interested in helping. Iā€™m afraid my sense of it is that there arenā€™t going to be a lot of people with the knowledge and the time, those I know of with the knowledge usually donā€™t have the time but I would love to be proved wrong. Peter ---
**Author:** ![Grimmers](https://forum.fritzing.org/letter_avatar_proxy/v4/letter/g/f05b48/32.png) [@Grimmers](https://forum.fritzing.org/u/Grimmers)\ **Post date:** [August 29, 2022, 7:43pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/17 "2022-08-29T19:43:32Z")
Hi Peter, This is my first post on forum: Sorry if I have bumped an old topic, but seemed relevant and canā€™t see more recent. Iā€™ve tinkered with Fritzing a bit, but always found it too difficult to understand parts edit. So I have done so Youtubing and created a 4-pin version of your FC-51, because thatā€™s what I got off Amazon as they are cheaper, more available and have analogue output too. They donā€™t seem to have an Arduino part number like KY-something. Anyway, I would be grateful if you could see if the info in the part is OK, but I am not sure about upload rules, etc. Iā€™ve also done a motor driver board based on DVR8833. Again, cheap board, works with Micro:bit 4tronix add-on. Would be grateful for any advice on how to ā€œautomateā€ Inkscape issues (font px issue and naming/grouping). Itā€™s tedious to say the least. [DRV8833 Motor Driver Board (MJKDZ).fzpz](https://forum.fritzing.org/uploads/short-url/1ZNKOCMaEyv6Z4JsCFp6dz4TE0O.fzpz) (11.2 KB) [MHSensorsIR.fzpz](https://forum.fritzing.org/uploads/short-url/xAtkhGdXg5qwa5Xqpe8OcnnV6y4.fzpz) (26.0 KB) Regards, Andy ---
**Author:** ![vanepp](https://forum.fritzing.org/user_avatar/forum.fritzing.org/vanepp/32/4426_2.png) [@vanepp](https://forum.fritzing.org/u/vanepp)\ **Post date:** [August 29, 2022, 10:10pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/18 "2022-08-29T22:10:38Z")
> [@Grimmers](#): > > This is my first post on forum: Sorry if I have bumped an old topic, but seemed relevant and canā€™t see more recent. Not a problem, there isnā€™t all that much activity here any more. The MHSensorIR part is missing layerIds (which only causes the part to not export as an image.) ![capture](https://forum.fritzing.org/uploads/default/original/2X/6/60b2d4161600f9c9f18ee0f45104891a998d72f9.jpeg) To correct that do Edit-\>select all and group and name the group breadboard like this ![capture1](https://forum.fritzing.org/uploads/default/original/2X/0/04f08d8d783a622120113d5b2bd67e5736a4fde1.jpeg) (here I just renamed the group that was at the top.) Schematic is a OK but doesnā€™t meet the graphics standards. Here I replaced it using Randyā€™s Inkscape schematic extension available here (note it doesnā€™t run on the latest Inkscape Iā€™m still on 1.1.2 til that is fixed.) > [@Fritzing-Schematic an Inkscape extension - released](https://forum.fritzing.org/t/fritzing-schematic-an-inkscape-extension-released/13394): > > Hi all! I have been working on an extension for Inkscape to create rectangular schematic symbol .svg files for use in Fritzing. I think I created a useful tool to speed up creation of schematic symbols, and now I want to share it with the community. Itā€™s available on github: [https://github.com/revolt-randy/Fritzing-Schematic-an-Inkscape-Extension.](https://github.com/revolt-randy/Fritzing-Schematic-an-Inkscape-Extension.) To install: In Inkscape, the edit menu ā†’ user preferences ā†’ system will have an option for ā€˜User extensionsā€™ - allowing you to open the folder toā€¦ ![capture2](https://forum.fritzing.org/uploads/default/original/2X/e/e1114c1506d9d5bef137951c7acfa145cfa02cc6.jpeg) ![capture3](https://forum.fritzing.org/uploads/default/original/2X/7/79fe24f0a3f3ab2888f6885d466c469f26d65bf0.jpeg) ![capture4](https://forum.fritzing.org/uploads/default/original/2X/7/7bff27bc3c8929c4324ad4ef87610d5b2b43be98.jpeg) which results in this (more or less, there is only one line on the title so I duplicated and added text) ![capture5](https://forum.fritzing.org/uploads/default/original/2X/3/3cee18bb773dd47eb80dc1fbb5c0e77f75b1dc38.jpeg) which results in this svg ![svg.schematic.MHSensorsIR(4pin)_df379abd1f4a7b88a1f96448099b5d2b_1_schematic](https://forum.fritzing.org/uploads/default/original/2X/0/03d86f97a9941feb5be409cfb30a2230f0ffe13e.svg) right click on it and select save image as to download a copy. The motor driver has more issues. Breadboard appears to be looking at the bottom of the module when breadboard is typically from the top and thus the pins are likely backwards. This ![capture6](https://forum.fritzing.org/uploads/default/original/2X/3/340ae9be8927a498d806585a2db79d3093e9058c.jpeg) should change to something like the (preferably looking like the top of the board) with pin 1 being EPP and schematic and pcb changing to be the same. ![capture7](https://forum.fritzing.org/uploads/default/original/2X/8/8715618e112090bba15c1818e824e7dee29f39f5.jpeg) again the schematic extension will make a proper schematic. These two sets of tutorials cover the current versions of Fritzing (many of the others are for older versions) > [@Fritzing PART CREATION Video Tutorial Series](http://forum.fritzing.org/t/fritzing-part-creation-video-tutorial-series/2647): > > NEW FASTER PART MAKING VIDEOS AT THE BOTTOM-[Fritzing Parts Fast](https://forum.fritzing.org/t/fritzing-part-creation-video-tutorial-series/2647/19) ADVANCED FRITZING USER TIPS & TRICKS VIDEOS AT THE BOTTOM-[Fritzing Adv Tips & Tricks](https://forum.fritzing.org/t/fritzing-part-creation-video-tutorial-series/2647/15) A series of part creation videos - Iā€™m not an expert, but there was nothing else around at the time. Use 1080p HD fullscreen to see details clearly - use gear symbol bottom right -. Recorded slowly for older people, so select a higher speed if itā€™s too slow. P.S. - Sorry about the voice/sound yum Fritzing Part Creation - Chapter1 - New Part ā€¦ > [@Part creation howto part 1 breadboard and pcb](https://forum.fritzing.org/t/part-creation-howto-part-1-breadboard-and-pcb/7692): > > Someone in this forum post requested help to fix up a part. So while doing that I decided to record what I needed to do in order to fix the part to provide a tutorial to create new / fix broken parts. If you start from the Tarjeta S4A EDU.fzpz file posted in the above thread, you should be able to recreate my improved part posted in the same thread. I started by loading the original part in to Fritzing, that indicates breadboard is (at first look anyway) pretty good, but schematic and pcb areā€¦ Hope this helps. Peter ---
**Author:** ![Grimmers](https://forum.fritzing.org/letter_avatar_proxy/v4/letter/g/f05b48/32.png) [@Grimmers](https://forum.fritzing.org/u/Grimmers)\ **Post date:** [September 3, 2022, 11:40pm UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/19 "2022-09-03T23:40:05Z")
Hi, OK I understand and have fixed the ā€œbreadboardā€ ID in the XML and it the part is now visible in an exported image. However, you said ā€œSchematic is a OK but doesnā€™t meet the graphics standardsā€ which I took to mean the style, but it also doesnā€™t export as an image either: I just canā€™t see what I need to do in Inkscape XML to tell Fritzing that it is a ā€œschematicā€?? Sorry, I canā€™t run that add-in from Randy as Iā€™m using later Inkscape. Is that covered in the later tutorial links? My schematic was created from a Core IC Schematic, so not sure why it doesnā€™t work. thanks Andy ---
**Author:** ![vanepp](https://forum.fritzing.org/user_avatar/forum.fritzing.org/vanepp/32/4426_2.png) [@vanepp](https://forum.fritzing.org/u/vanepp)\ **Post date:** [September 4, 2022, 12:07am UTC](https://forum.fritzing.org/t/fc-51-infrared-obstacle-avoidance-proximity-sensors-module/4130/20 "2022-09-04T00:07:26Z")
The schematic group needs to contain the entire drawing (this is the one from your part above) ![capture](https://forum.fritzing.org/uploads/default/original/2X/c/c591e74c15253abdcea2cdea9582dcb32f551e43.jpeg) here only the outer rectangle is in the schematic group. You need to ungroup it and do Edit-\>Select all then group like this ![capture1](https://forum.fritzing.org/uploads/default/original/2X/a/a2ee50d31a1e0d29ef8c508cab3b973a8fc684b3.jpeg) Peter