schematic PNG export: unicode encoding issue
Special charters are exported into the PNG-image with there HTML code/Unicode decimal. example schematic text: ^ exported picture: &94; schematic text: picture: #BugReports#
copper area broken after import
Imported an standard project and was greeted with this result: Is this an known issue? #BugReports#
3D-viewer and export still broken?
Can't remember how many moons ago this issue was first report but it is still broken: 1. 3D-models in standard version not displayed properly 2. some parts missing in the 3D-export from the pro version. Any comment? Any chance at least this beahvior will be fixed? pro: standard: 3D-export: #BugReports#
wrong link: https://cart.jlcpcb.com/capabilities/Capabilities
In the online gerber viewer there are broken links (encircled in red): e.g. capabilities is https://cart.jlcpcb.com/capabilities/Capabilities which is still in the cart.jlcpcb.com subdomain. while the working link would be www.jlcpcb.com #BugReports#
[bug] new supplier not saved
The option to add new suppliers is broken. After restarting esayeda all supplier are set to unknown. #BugReports#
BOM tool: 100% part match but wrong footprint
The particular line items reads the following: ID Name Designator Footprint Quantity Manufacturer Part Manufacturer Supplier Supplier Part "5" "SSP1117-ADJ" "U1" "SOT-223_L6.3-W3.5-P2.30-LS7.0-BR" "1" "SSP1117-ADJ" "Shanghai Siproin Microelectronics" "LCSC" "C277894" For some reason, the BOM tools match this to this with 100% match to a wrong part: In my eyes, this isn't a close match at all. While the name and manufacturer are identical the package and LCSC part number are completely different. It is fundamentally wrong when a strong identity like the provided LCSC part number differs to signal a perfect match. With this particular bom there are more errors but as far as I can tell none of them are marked as 100% match: e.g. C210335 was matched with C497920. Different footprint, different color temperature. "17" "2800K" "LED3,LED4,LED5,LED6,LED7" "LED3014-RD" "5" "-" "Hongli Zhihui (HONGLITRONIC)" "LCSC" "C210335" Another example: C245696 matched with C399497 "20" "0.15Ω 1W" "R9,R10" "R2512" "2" "CR2512J0R15E04" "Ever Ohms Tech" "LCSC" "C245696" The list of mismatches continues: here it suggested a through-hole female header (C2977590) instead of the specified SMD male header (C919361) "30" "2.54-2*2P" "H6" "HDR-SMD_4P-P2.54-V-M-R2-C2-LS7.5" "1" "2.54-2*2P 立贴" "BOOMELE(博穆精密)" "LCSC" "C919361" "0.032" This bug/behavior should be taken seriously as it converts the bom tool to dangerous if I need to crosscheck each line item based on the ID with the BOM open in excel to catch these errors. #BugReports#
State of LCSC integration into easyEDA
Over the last months to year I noticed a lot of higher LCSC-partnumber, newer parts, aren't added to the easyEDA library. Additionally I have come across a handful of parts with wrong pinout (e.g. NPN on a PNP) and a lot of parts have just default U? as schematic designator instead of the appropriate. On top the style isn't consistent. Different valued MLC-capacitors have differently sized schematic symbols or similar parts use different styles. As an example C118954 and C118963: #FeatureRequests#
3D-model/STEP-export: provide plug
At the moment the 3D model and STEP export of connectors is lacking the plugs. Providing the plug directly inside the STEP would significantly speed up the workflow. At the moment you need to search manually for the matching plug and add it to the assembly. Ideally, the connector should be two parts within the step file: receptacle and plug #FeatureRequests#
Add keepout zones to (connector) footprints
It would be very helpful if footprints of components like connectors have the appropriate keep-out zone in the document layer. Here is an example around this plug with the horizontal/90° socket: easyEDA/LCSC footprint: improved footprint with keep out zones preventing clearance issues: another example where the keep-out zones are critical would be the ESP-8266 modules and again the official footprint doesn't have the keep-out zone from the datasheet in the document layer. A improved footprint for this part looks like this: This is especially annoying since custom/workspace footprint isn't accessible through searching the LCSC part number even if they are named appropriately. e.g. KF2EDGSRMG-3.5-2*2P (C2923269) #FeatureRequests#
STEP export: component rotated
Exported this PCB as .json (easyEDA standard), imported to the pro version and exported it as STEP. 1. easyEDA standard: one component doesn't load while it works as intended in the pro version (not the only component where I observe this issue) 2. pro version: no issue 3. STEP exported from pro version: 1 connector is rotated. Tried a different PCB with the same result (1 part rotated). #BugReports#
DRC error between copper area?
I get a DCR error between two copper areas. How is this even possible? In theory this should be impossible. #PCB#
DRC error: show layer information
It would be helpful to get beside the location also the layer information where the DRC error was found. With 4 layer I have a hard time to locate this DRC-error as nothing obvious sticks out: #FeatureRequests#
BOM export: "JLCPCB Part Class" twice
In the BOM export dialog there is twice the option to include "JLCPCB Part Class". Looking at the generated csv this might be related to C2681227 (ID/line 24). #BugReports#
Import EasyEDA Pro Standard?
EasyEDA Pro Standard is mentioned under the "Specific function comparison" section. I think this should be EasyEDA Standard. Also some explanation what half offline and full offline mode means would be nice. In this regard if I try the pro version now do I lose access to the files if I decide later against the abo? As far as I can see it is not possible to import a "pro" project into the standard edition. #BugReports#
bug report forum: can't post in bug reports LCSC
Trying to post in LCSC - bug report results in this error message: #GeneralDiscuss#
Results number doesn't match result count
The shown result count doesn't match the actual results count if the option in stock or ROHS is selected: https://lcsc.com/products/Programmable-Logic-Device-CPLDs-FPGAs_11330.html?keyword=intel%20max10 number shown: 1719 actual results: [removed]
Can't update or create PCB from schematic: connection error
Can't update or create the PCB from the schematic: Chrome console looks like this: #BugReports#
board outline moving diagonal
With some shapes the board outline moves diagonal if the arrow keys are used. Demo: https://oshwlab.com/Xenons/demo-copper-area #BugReports#
copper area: clearance not properly shown in properties tab
It looks like my design rule of 15 mil is obeyed but the properties window of the copper area still shows 10 mil clearance which can lead to human error. #BugReports#
design rule preset/dialog when a new PCB is created
When a new PCB is created a dialog for selecting a design rule set and layer count preset would be helpful (e.g. free version: JLC 2 layer\, 4/6 layer\, aluminium | pro/paid version: custom presets). #FeatureRequests#
OSHWlab broken links on landing page
The collections links on the landing page are all leading to HTTP Error 500 pages. e.g. https://oshwlab.com/recommend/ATtiny #BugReports#
LCEDA-OBJ-Transform: out of bound exception
The converter tool for the OBJ throws an exception: Index was outside the bounds of the array. As far as I can see I can't attach the easyEDA export here as file. Details: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IndexOutOfRangeException: Index was outside the bounds of the array. at LCEDA_OBJ_Transform.MainForm.button1_Click(Object sender\, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4420.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- LCEDA-OBJ-Transform Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/user/Desktop/LCEDA-OBJ-Transform.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4400.0 built by: NET48REL1LASTC CodeBase: file:///C:/Windows/[Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0\_b77a5c561934e089/System.Windows.Forms.dll](http://Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll) ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4360.0 built by: NET48REL1LASTC CodeBase: file:///C:/Windows/[Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0\_b77a5c561934e089/System.dll](http://Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll) ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LASTC CodeBase: file:///C:/Windows/[Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0\_b03f5f7f11d50a3a/System.Drawing.dll](http://Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll) ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LASTB CodeBase: file:///C:/Windows/[Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0\_b03f5f7f11d50a3a/System.Configuration.dll](http://Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll) ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LASTC CodeBase: file:///C:/Windows/[Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0\_b77a5c561934e089/System.Core.dll](http://Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll) ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: \ \ \ When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. #BugReports#
metric or at least common imperial scale for OBJ export
Currently the OBJ export feature creates files with 1/100th of inch as scale which isn't avaible for import in ervery programm [e.g. Autodesk Inventor] (if it must be imperial then foot, inch or tau but not 1/100th inch). #FeatureRequests#
BOM export not wroking?
Does anybody else has the problem that the BOM export isn't working (pick&place and gerber works)? Clicking export does nothing. #BugReports#
footprint size preference
It would be nice if there would be either a global/project preference or drop-down menu to quickly change the footprint size. A lot of components have a standardized footprints with different pad size options so it shouldn't be a problem to add quick access (compared to footprint manager -> search the component in question -> search for the footprint -> update) which allows swapping the footprint on the PCB or schematic directly. #FeatureRequests#
language setting ignored [decimal separator]
This software ignores the language setting of the system. As a result it ignores the [,] input for decimal seperator (e.g. on the numpad) if a system is set to an language which follows DIN/ISO. I don't know about electron but usally this only requires one additional line of code. #FeatureRequests#
rotation/mirror not a group
In theory geomatric opperation like mirror or roation should cancle each other out and not distrub the geometry itself but in EasyEDA it does. simple example using a single net lable (is an issue everywhere and not exlpainable with grid/snapping): #BugReports#
[bug] ghost/invisible net pins
On this schematic there is one net which has a few invisible pins: How can I remove them? Already tried reopening the project. #BugReports#
[bug] ghost/invisible net pins
On this schematic there is one net which has a few invisible pins: How can I remove them? Already tried reopening the project. #BugReports#
[bug] footprint datasheet not overwritten by schematic footprint
The datasheet from the schematic symbol does not overwrite the one linked in the footprint. This bevhavior results in the majority of LCSC part been linked to the wrong datasheet on the PCB. #BugReports#