asdasdasd
Update Track Nets when Updating PCB
If it is necessary to update a circuit after a PCB layout has been started, for example to simplfy a layout or correct an error in the schematic, and net connections are changed, components on the PCB will show the updated net assignments on their pads. However any connected tracks retain their pre-update assignments, generate DRC errors as a result, and must be updated manually or redrawn. It would be better if tracks updated to the new net assignments automatically. #FeatureRequests#
NuttyProfessor47 2018-06-19 18:23:51 comment 5 0 Feature Requests
Persistent unselectable/undeletable Pads
I've been working on and Arduino shield for some time but was not happy with my layout. Rationalising an associate board created an opportunity to enlarge the shield board outline and move some non Arduino connectors. I therefore took the opportunity to rework the rest of the layout Unrouting All, and moving a set of related components off the board outline in preparation for re-arranging them. However, although the components and their pads all seemed to move alright, duplicate pads remained on the board in their original positions disconnect from any ratlines fortunately, and I am unable to select, move or delete them. They light up when the multi layer layer tool is selected along with all those connected to the components. Please would you ensure that when components are moved after an Unroute, that they take all of their pads with them and advise what I should do? #FeatureRequests#
NuttyProfessor47 2018-06-14 00:26:10 comment 3 0 Feature Requests
Where is the Phantom Pad?
OK. I need eagle eyes and some lateral thinking here. Having completed my layout, the final DRC check showed two Track to Pad errors as shown below. For starters I deleted both tracks, and sure enough both errors cleared. As you can see though, both tracks and the pads that they were connected to are on the same net, and the error crosses are away from any visible pads so there should be no issue there. I then started to replace one of the tracks, with the following result. So where is the phantom pad? Starting the new track from the oval NEUTRAL pad, as I move the end of the track to the right or left the error cross moves horizontally along the centre (where the red dotted line of the track cursor is in the image above) of the grid square that surrounds the error cross. If I take the end of the track outside that square to the right, the error clears, and to the left it moves to become a genuine error on the U3_3 pad. Move it up and the error cross stays on the centre line. Move it down below the centre line of the grid square, and it clears. So what's on the grid square horizontal centre line that the DRC check thinks is a pad? Any suggestions welcome. #PCB#
NuttyProfessor47 2018-06-13 00:30:37 comment 8 0 Circuit Design
Screenshot feature missing
I have a major problem with a DRC error flagging a non existent conflict and would like to post screen shots to see if anyone can help. However the facility to do this is missing in the latest version of Easy EDA. Please would you restore the screen shot capability? #FeatureRequests#
NuttyProfessor47 2018-06-12 07:28:09 comment 6 0 Feature Requests
Update PCB fails to report footprint changes
Investigating the problem identified in my last post necessitated changes to component footprints in Schematic view and updates to the assiciated PCB. In the previous version of EasyEDA this presented no problems. However, in the latest version updated today, footprint changes (hole and pad size changes) are not carried over into the PCB consistently, and in any event are never reported as a change in the update dialogue. Because I have in some cases been editing standard EasyEDA package footprints, e.g. TO-220(TO-220-3) the edits became Personal. I checked that the component in the schematic was linked to the correct Personal PCB Lib footprint in each instance in the schematic, but clicked "Update" anyway. After changing all the TO-220 components, I updated the PCB, but the dialogue only showed changes to connections to GND (I don't have any, the ground plane being specified as EARTH for consistency with the mains PE (Protective Earth)) which I then have to reverse in Design Manager. It should be showing that the TO-220 components are to be updated. Nevertheless, upon checking the PCB, sometimes the hole size changes made would be present, sometimes not, and the update process would have to be repeated until they were. It would appear that the updates only take effect consistently and are presented in the dialogue if the component has been removed and replaced in the schematic, even though the effect in the schematic is the same regardless of whether it is updated or replaced. This is inconsistent and should be corrected. #FeatureRequests#
NuttyProfessor47 2018-05-08 15:18:20 comment 7 0 Feature Requests
Hole size Rounding Issue
It appears that there is an error in the conversion between Inch, mil, and mm dimensions in EasyEDA. Noting that the conversion factor was standardised in 1959 at 1inch = 2.540mm, errors in the third decimal place should be avoidable if arithmetic precision is suitably matched to the number of decimal places displayed, and appropriate rounding is used. Are all calculations done in mil regardless of the unit of measure selected and converted afterwards, or are calculations done, as they should be, in the selected unit of measure? This may be related to my previous post on DRC errors. When checking the Gerber PTH Drill sizes with Gerbv for my board I found that I had nearly twice as many drill sizes as hole sizes. I therefore went back to the board schematic and reviewed/ modified all the PCB footprints (PCB Lib) and standardised on hole/pad sizes based loosely upon IPC recommendations for lead clearance and relative pad size. This resulted in 6 different hole sizes being used: 0.800mm, 0.899mm, 1.000mm, 1.100mm, 1.200mm and 1.300mm. Note the 0.899mm is the size used for AXIAL-0.3 from EELib which i have used for all resistors, so I used the same sized hole (0.899mm) for all components needing 0.9mm. However, the resulting Gerber shows additional drill size requirements of 1.101mm for some of the 1.100mm, 1.201mm for some of the 1.200mm and 1.301mm for all of the 1.300mm holes. Going back and editing the footprint files to ensure that holes were defined to 3 decimal places (i.e. type 1.300 instead of 1.3) eliminated the 1.201mm and 1.301mm extraneous Gerber drill sizes, but NOT the 1.101mm. Checking all the 1.1mm holes on the EasyEDA PCB view showed them all indeed to be 1.100mm, however the same board in Gerbv has them all as 1.101mm. It is interesting to note that the holes from AXIAL-0.3 and others set to 0.899mm in order to standardise all come out at the preferred diameter in Gerber as 0.900mm. #BugReports#
NuttyProfessor47 2018-05-08 14:54:50 comment 0 0 Bug Reports
DRC Check Errors
I have used IPC recomendations as the basis for setting my track widths and spacing, and standardised on 0.25mm width and spacing for most of my board. However, if I set the DRC rules to the same value, 0.25mm for track width and all spacings, ALL tracks show a DRC error. The DRC check will NOT accept a track width equal to the defined minimum. It MUST be greater. Setting the DRC minimum to 0.249mm for actual widths of 0.25mm fixes the problem. Surely the minimum should be exactly that, a minimum ALLOWABLE value? I wonder if this is linked to the issue of Gerber not being able to identify the minimum track width? #BugReports#
NuttyProfessor47 2018-05-02 15:34:34 comment 4 0 Bug Reports
Misleading Time Stamps on Histories Record
The Time Stamps assigned to saves in the histories record are 7 hours ahead of the times when the saves were made. This causes confusion when the time of a save is known, but cannot be found. For example, I saved a file at 08:40:54 according to my system clock which is synced with an Internet time server, but the resulting Histories record is The Time Stamp should be the time at the origin of the save, in this case, 2018-04-22 08:40:54 #BugReports#
NuttyProfessor47 2018-04-22 15:50:16 comment 2 0 Bug Reports
Files NOT saved after "Save Success"
I've just realised that much of Tuesday's work on a schematic was wasted! The files that loaded when I logged on this morning are from Monday! Many components had been updated on the schematics to avoid availability problems, but those changes are no longer there. However, the library components that I had to create are all present and correct, and even worse (or maybe better?), the PCB appears to be up to date, and when I go to the schematic and select "Update PCB" the list of changes offered would take the PCB back to the state it was in BEFORE I updated all the components in the schematic on Tuesday. Whats going on? Clearly there is a bug in the save routine that allows it to signal success, when the file stored on your server has not been changed. Please fix this. I therefore need advice on how to proceed, i.e. how to get the schematic back in sync with the PCB without having to make all the changes again. #BugReports#
NuttyProfessor47 2018-04-19 17:29:45 comment 8 0 Bug Reports
Update about S$ "mystery" Nets
I'm unsure whether my issue is the need for an additional feature, or a bug. Either way, a couple of days ago I posted a screen shot of my Design Manager Net List showing five S$ nets that I could not explain or find because they do not highlight. Whilst waiting for a reply I verified that they do not exist in the schematic, so I went searching on the PCB for random unconnected bits of track but found none. I then discovered that three of my mystery S$ nets were in fact BottomSolderMaskLayer "Tracks" that I had added in areas where current capacity needs enhancing. Of the two remaining, I found that one was a TopScreen "track" that I had drawn to show the outline of where a daughter board will be mounted, and hence where no tall components should be placed. The other I cannot find at all. If selecting an S$ net in Design Manager highlighted it in the same way as all other nets, finding them would not have taken many hours, and left the job unfinished - one S$ net still to find. Please consider adding the highlight feature to ALL nets in the design manager netlist. It would help immensely. #FeatureRequests#
NuttyProfessor47 2018-04-19 17:09:00 comment 0 0 Feature Requests
Ratlines don't clear when tracks are laid.
I've reviewed as many of the reports about ratlines that I could find and as a result have cleared many of the persistent ratlines from my final PCB layout, but there are 2 that I just can't fix, as you will see in the attached screen capture. In addition to the two voltage lines I've shown here, the ratlines for a RESET track also persist. All tracks and pads display the same NET which agree with the schematic, and track ends are alligned with the ends of the Ratlines within pads. Checking these factors fixed all the others, but not these three, two of which you see below. The only clue is all the persistent Ratlines go to or from SMD pads, but not all SMD pads have persistent Ratlines! Any suggestions about what to check next would be most welcome. #PCB#
NuttyProfessor47 2018-03-22 17:00:30 comment 4 0 Circuit Design
Telling a PCB from a Module
Because I'm moving a design from a different Spice simulator/schematic package I have 4 schematic diagrams that must be integrated onto, and connected on a single PCB. I started this process some time ago, but now need to update some of the schematics because component have been replaced due to obsolescence. I have a project for each schematic, and a PCB layout in each too, but some were saved as modules so that they could be added to the master PCB for final layout and connection work. How can I tell which of the PCB layouts are modules? #PCB#
NuttyProfessor47 2018-03-03 06:09:34 comment 3 0 Circuit Design
"Grouped elements"
I'm attempting to use the Arduino Shield schematic in a design and need to amend it by removing the 6 pin plug. However if I select any element and try to delete it the whole footprint gets deleted. I've tried "lasooing" the whole footprint and clicking Group/Un-Group but that does nothing. How can I seperate the elements to manipulate them, or must I recreate the shield myself? Arduino Shield converted to PCB #PCB#
NuttyProfessor47 2017-11-15 19:09:22 comment 2 0 Circuit Design
Creating a PCB symbol from a datasheet
I need to create a PCB symbol for a board mounted mains transformer. I've read the tutorial and referenced a couple of other sources, but the instructions for drawing the physical outline seem to fail at the first step. There is no line drawing tool. I can place the pads, but how does one draw the outline with only the PCB tool box available? The drawing toolbox doesn't appear when a PCB Lib pane is opened. I've tried selecting different layers (top silk, board outline) but drawing a shape with the cursor only draws a dotted box for as long as left mouse is held down, and using the "track" tool for the outline doesn't work either. I'm sure as before that I'm missing something obvious to others, but it's not to me. #PCB#
NuttyProfessor47 2017-09-21 03:03:20 comment 10 0 Circuit Design
Schematic and PCB layout re-use
Is it possible to use a schematic as a starter for 10 in a new schematic? In particular, is there a way to use the Arduino UNO shield as the staring point for a larger schematic/PCB that will preserve the Arduino interface connections and layout? If so, how? I've tried copy and paste, but that doesn't work between tabs, and the Arduino sample won't copy at all. So can it be removed from it's frame (if I try to magnify it, it dissapears top left, and recentering reduces it back to its original size with the other frames around it) and repositioned in the centre of the screen (canvas)? #Schematic#
NuttyProfessor47 2017-09-06 16:42:46 comment 5 0 Circuit Design