Creating Fusion Electronic Component Libraries from PCB modules

Many of the Arduino related modules have their own PCB with the relevant semiconductors on board.  This creates a chicken and egg situation when creating the library parts to match.  Remember that some of these modules are slightly different in their physical appearance dependent on supplier.  The manufacturers do not always have a library file to offer or a detailed dimensioned drawing. The manufacturers also do not seem to profile the PCB accurately. The SSD1306 is a good example where the mounting holes are in slightly different places dependent on source.   One particularly tricky one is the DS3231 RTC module.  This has two sets of matching pads and three mounting holes and as far as my searching goes, there are no detailed drawings available.  My process on the DS3231 was to scan the board and use the Fusion ‘first dimension’ scaling rule.  Here are the steps.

    First step is to make sure you have ‘Scale Entire Sketch to First Dimension’ ticked in Fusion Prefs/General/Design.

    If the board has one side unpopulated with components this is ideal to get an image of it.   You can use a mobile phone or similar but there will be distortions in the resulting image due to lens geometry.   My preferred method is to place the flat side of the board on my office scanner, scan and save the image as a jpg.  Try to scan it so there is little or no rotation off square.  The easiest way is to locate the board up to the platen edge.  The DS3231 does not have a flat side and I resorted to removing the battery holder to allow a flat scan…. perfectionist did I hear you say ? ….

    Import the resulting jpg image as a Canvas into Fusion and set up the workspace to be in Imperial units.  Use the image as a Canvas background to trace and locate the key aspects of pad locations and mounting holes etc.  Try to be as accurate as you possibly can with your tracing.   The important aspect of the traced features is their X and Y location.  Hole sizes are not critical at this stage just the location of the hole.

    The outer perimeter of the board is less critical on accuracy. 

    Do not dimension anything at this stage so your traced image should all be in blue lines.

    Once you have all the key aspects traced, measure a key dimension on the actual board and mimic this same dimension on your sketch and dimension it to match the actual measured value.   This is a critical step as any error in your physical measurement will magnify or shrink your resulting sketch.   The sketch should now have expanded to match your measurement and can now be used to accurately measure the remaining geometry locations.

    Continue with the sketch dimensioning tool to document the X and Y positions of the geometry of interest.   Do not dimension to the outline as it won’t be accurate.  Instead think about where you want the placement zero to be in Fusion Electronics and then dimension to this.   Components such as 0.1”SIL connectors make a useful cross check that things are progressing well. SILs also make good locations for X0Y0 using a point midway along the SIL pad array.

    Once you have a sketch showing all the key locations you can proceed in FE to create the symbol and the footprint.  Use the Properties ‘right click’ on pads to accurately locate them in relation to your sketch X0Y0 location. Use pads as mounting hole location markers.

    When all the locations are entered, draw a nominal outline as the silk screen image.

    With the footprint complete, use the ‘three dot’ route to creating the 3D model.  Fusion modelling workspace will open with the faint outline of the footprint you have just created and you can then build the 3D model to match the geometry and holes etc.

    If you attempt to create the 3D model first without the matching sketch of the geometry you are going to have fun trying to make the footprint and the 3D model match each other.

    Once you are happy with the footprint and the 3D model don’t forget to use the joint command to locate a ‘hole to a hole’ to lock the footprint and the 3D model.

    It sounds complicated but it works…. once you have the routine clear in your head.  Below is the Canvas import of the DS3231 and the resulting sketch created after the Canvas trace had been scaled up.  Engineers creating the Arduino modules seem to lack a certain discipline.   The electronic parts all get nicely placed (hopefully on 50 thou related positions) and then they seem to arbitrarily position the mounting holes where they can find some remaining space to fit them in.

    These additional notes have been added to my Fusion Electronic library waffle document that you can download on the link below.

    Links to similar or related post are listed below : –

    MX3660 as used on Tormach PCNC440

    My Tormach PCNC440 made a nasty electrical bang the other day. At first I believed the 48V main power supply had died but it was simply being dragged down by a fault in the Leadshine MX3660 master stepper controller.

    As ever the Tormach helpline was supportive and helped with the diagnosis. The replacement MX3660 was likely to be a long delivery delay from the States. It would probably have a significant delivered cost after shipping and VAT were added to Tormach’s ex works price.

    Some checking on the web revealed a company called Motion Control Products which was listing the MX3660 but their URL was a dot com address so at first I assumed that they were also Stateside. After looking closer I discovered they were located in Bournemouth UK, around one hour from my home. Although they listed the MX3660 as a line item they were not showing stock. A request for deliver leadtime to their sales team brought an answer from Richard in Sales to say he had found one in stock. Happy days.

    A few days later the new MX3660 arrived. After setting the DIP switches to match those on the fried one, I installed it and switched on. My Tormach burst into life and the cover plates could be fastened back in place.

    The obvious moral to the story is don’t blindly assume a dot com can’t be a UK supplier…..

    Links to similar or related post are listed below : –

    Arduino LoRa power supply issues

    I have been working on a control system using a Seeed Xiao processor with a LoRa radio link (also with an OLED display, SD card and RTC). The system seemed to run but not reliably and was causing some head scratching. Was it my code or was it the hardware ?

    After lots of playing with the code I decided it must be hardware. I had run a PCB in Fusion Electronics so all the connections were stable and reliable so what else ? …… Stupidity had persuaded me to power the LoRa modue (RFM9x) from the 3V3 stabilised output provided by the Xiao. Which might be fine when in receive mode but when the LoRa goes over to transmitter it takes a whopping surge of current. This was glitching the system.

    All the modules are now powered with 5V via their RAW / VCC power input pins and look after their own 3V3 stabilised rail. Problem solved, system working well. Here is a overview image of the board.

    Links to similar or related post are listed below : –

    Fusion Electronics Library Notes and Crib Sheet

    After spending many hours going round in circles trying to create new custom library parts in Fusion Electronics (FE) I gave in and posted a plea for help on the FE forum. I received some helpful replies but not sufficiently uplifting to put me at ease with the process.

    As ever my nerdy side stepped up and armed with this new knowledge I set about learning the process step by step in a way that I could understand it and more importantly repeat it successfully.

    The result of this is a 30 page document that can be downloaded from the link below. This contains the library process, a help crib sheet for using FE and the copies of the original support replies I received from the FE forum.

    It may not be perfect and it is a work in progress so feel free to give me feedback on errors and content changes. Remember it is based on Fusion Electronics as of May 2025 with build version 2602.0.71. As I learn more I will update the contents and re-post.

    I hope it helps someone, somewhere, sleep better. The length of the waffle will almost certainly guarantee the latter.

    Links to similar or related post are listed below : –

    CCTV System with remote camera over WiFi

    I had a request for help with a CCTV system where the owner wanted to add a remote camera to an outbuilding with no cable route possible. This should have been a JSN job (Just Say No) but I’m always up for a (steep learning curve) challenge. After some investigation (back of a napkin sketch and a quick Google search) I opted for a 5GHz WiFi bridge and thought the job was going to be easy. JSN jobs are like that but you have to be conscious that they come configured with inbuilt mission creep.

    The WiFi link was a 24V power over ethernet (PoE) system. The existing three cameras were 48V PoE and the additional camera was to be the same.

    Here is the final configuration. The red lines are PoE and the blue lines are just basic CAT5 unpowered connections.

    The NVR is a SPRO four port device with 48V PoE on all ports. To save cabling the owner had used a PoE pass through switch so two cameras could share the same cable running back to the NVR. The existing third camera was a direct feed from the NVR. I was quite impressed with the pass through device. It has the capacity to allow four cameras to share the same PoE NVR connection.

    Back to the plot … Adding the fourth remote camera using a bridge would have been simple if the bridge was 48V PoE powered but it was 24V PoE. The remote location therefore needed two PoE inserters – a 24V one for the bridge and 48V for the camera. The LAN ports on the two inserters just need connecting together to complete the link. The NVR ‘sees’ the remote location as a locally connected camera.

    Something to note. The bridge (KuWfi) as delivered has two IP addresses configured, 10.1.1.253 for the Master location and 10.1.1.100 for the Slave location. All the cameras are allocated 10.1.1.x IP addresses on the NVR. The NVR also has an internet connection for remote Smartphone viewing.

    KuWfi provide an application to configure the two bridge units. I spent a long time trying to work out how to get this to respond to either device. In the end a light bulb moment reminded me that a previous Chinese sourced product had the same issues. I had traced this to a Chrome related problem (which I never solved) and found the Application would only work using Edge. The same happened this time. Using Edge got me into both units without a problem. Note that you have to set your host interrogating computer to be on the 10.1.1.x domain.

    There is a signal strength graphic on the Slave GUI which is very useful. You can connect your computer LAN port to either the Master or Slave 24V injector LAN port and request either of the two addresses (10.1.1.100 or 10.1.1.253) from either end of the link

    Just think how much simpler it would have been if the bridge also ran from 48V …. maybe someone produces a 48V to 24V PoE step down converter ? Or maybe I should just stick to the things that I pretend to know more about … and JSN.

    Links to similar or related post are listed below : –

    Verified by ExactMetrics