asdasdasd
Left-click and drag Delta X and Delta Y info no longer works in WaveForm
I don't know when this functionality stopped working. Some time after Version 4? This used to be possible in WaveForm but does not work now: Delta X and delta Y trace data can be seen on-screen using a Left-Click and Drag select box, with the readout adapting to the Y axes in each pane. Returning the cursor to within a small radius of the starting point of the select box - without releasing the Left-Click - returns the readout to X and Y trace data." Left-click and drag still draws the bounding box but there is no Delta X and Delat Y data shown. Dragging and releasing the Left-Click zooms as usual. #BugReports#
example 2020-06-25 23:50:44 comment 0 0 Bug Reports
delta X and delta Y value readout in Waveform window no longer appears
X and Y readout is OK: delta X and delta Y values no longer appear: Note that the zoom of the selected area is OK: #BugReports#
example 2019-11-21 18:20:09 comment 0 0 Bug Reports
Spice model and symbol for Ammeter updated: please replace symbol in your spice simulation schematics.
The spice model associated with the Ammeter symbol had been accidentally removed from the spice model library. The model has now been replaced but the Ammeter symbol has also had to be modified. Simulation schematics with the old Ammeter symbol may no longer work. If you encounter this problem, please delete the Ammeter symbol from your schematic, do a SHIFT+F search for Ammeter then select the one with a small blue "S" in the icon on the left of the search results: and then replace the ammeter instances in your schematic with the new symbol. Sorry for the inconvenience. #Simulation#
example 2018-07-12 18:06:42 comment 0 0 Circuit Design
Formatting of Forum posts gets very strange
There seems to be an excessively wide line spacing even with only a single Return at the end of a line which makes posts look strange but there is more going on that appears to result in strange formatting. The formatting - except for the excessive line spacing - seems to work OK if you're writing new text in either WYSIWYG or Markdown modes but as soon as you start copying and pasting from an earlier post, it all seems to get messed up because the copy and paste picks up a load of html-like formatting that the act seems to be inserted after you have pressed the Add Comment button. In other words, what seems to be Markdown when you have entered and formatted it seems to have html syntax wrapped around it after it has been posted and appeared in the forum. Copying and pasting this back into a new post makes the formatting look inconsistent #FeatureRequests#
example 2018-03-13 22:32:51 comment 1 0 Feature Requests
Essential checks before placing a PCB order
Updated 170905 A copy of this can now be found at: https://easyeda.com/andyfierman/Essential_checks_before_placing_a_PCB_order-de51f1401cec4bd2896ea835aca67db8 A simple mistake can make a batch of PCBs useless so before submitting an order for PCBs, there are a lot of things to check. The list below is a good starting point for the essentials but it by no means exhaustive! 1) Check that all nets and netnames are as intended. For example nets can be accidentally connected together while drawing and editing a schematic and also by inadvertently assigning duplicated netlabels; 2) Check that the appropriate package has been assigned to each and every schematic symbol. Don't forget that different transistors, capacitors and even resistors may be in different packages in different locations in a schematic. Also check that components have been rated correctly as this may affect their package size (don't forget their height too!); 3) Check that the pin designations of the schematic symbol and the PCB package are the same. The pins on the schematic symbol for a bipolar transistor may be labelled B, C, and E but if the corresponding pins on the PCB footprint are labelled as 1, 2, and 3 then EasyEDA will flag this as an error when an attempt is made to convert the schematic into a PCB. It is simple to correct or - better - avoid this: change the labelling on the corresponding pins of the PCB footprint to B, C and E or change the labelling on the corresponding pins of the schematic symbol to 1, 2 and 3. To change the pin labelling in the schematic to match the PCB footprint: select the part, press the i key then edit the Names in the Edit Pin Map Information section of the Modify symbol information dialogue that opens and click OK when finished. To change the pin labelling in the PCB to match the schematic symbol: select each pin of the relevant part, then edit the pin Names in the right hand Properties panel. Note: do not confuse the schematic symbol pin numbering with the spice pins numbering. For more about this see: Schematic symbols: prefixes and pin numbers in: https://docs.google.com/document/u/1/d/1OWZVVFRAe_2NW3WratpkA_SGuHa5AcRow5ZRfvcoVTU/pub#h.pkwqa1 4) Check that the pin designations of the PCB footprint chosen for each and every device actually matches the pinout of the device that will be soldered to it. It is very easy to assign a SOT23 package to a BC846 bipolar transistor where the pin order is: Pin 1 = Base Pin 2 = Emitter Pin 3 = Collector and then to forget that the pin order for a MMBF5485 junction FET going round the same SOT23 package in the same order is: Pin 1 = Drain Pin 2 = Source Pin 3 = Gate To change the pin labelling in the schematic to match the PCB footprint: select the part, press the i key then edit the order of the PCB Pin information in the Edit Pin Map Information section of the Modify symbol information dialogue that opens and click OK when finished. To change the pin labelling in the PCB to match the schematic symbol: select each pin of the relevant part, then edit the pin Numbers in the right hand Properties panel. 5) Check that all necessary Bill of Materials information is present and correct. Correct it and add more if required, making sure that fields such as Description are consistently labelled so that they form a coherent column structure in the BoM; 6) Check that all PCB footprints are correct for the intended devices (yes: whether they have come from the library or you have created them yourself: check them thoroughly); 7) Check that silk screen markings such as the polarity markings for electrolytic capacitors and diodes are the right way round. Even if the pin names, numbering and sequence around tha package are correct, it can all go wrong if the footprint markings show the device in the wrong orientation. 9) Check that devices have been placed on the correct side of the board; 10) Refresh and check all the Components and Nets in the schematic Design Manager tab in the right hand panel; 11) Refresh and check all the Components, Nets and DRC Errors in the PCB Design Manager tab in the right hand panel; 12) Check connector and on-board pot and switch orientations; 13) Check the dimensions and locations of mounting holes and any components that have to line up with respect to these mounting holes or to apertures in an enclosure; 14) Check that the order of the top and bottom (and any inner layers) is correct; 15) Check that a Board Outline exists, is closed and that it is shaped and dimensioned correctly and is on the correct (Board Outline) layer; 16) Check that silk screen markings do not overlap pads; 17) Check that all required silk screen markings are present, in the correct locations on the correct layers, are within the recommended dimensions, are legible and and spelled correctly; 18) Check that any additional information such as notes about the PCB stackup etc., are present and on the correct (Documentation) layer; 19) Check that no board outline, silk screen or documentation layer information has accidentally been placed on any copper layers; 20) Having completed the layout, check that the assembled component heights do not foul any enclosure (At the time of writing (160922) this is not something that can be acheived directly in EasyEDA as there is no 3D viewer yet available so this must be checked by other means); 21) If copper areas are used with heat shunt spokes enabled, check that any tracks that join pins that are also joined by copper areas run within the area of a spoke. If they do not - for example a 45 degree diagonal track coming out of a pad with 90 degree heat shunt spokes - the track forms an extra spoke which increases the heat shunting to a pad and so may make soldering more difficult; 22) Check that all copper areas assigned to a net are joined by reasonable widths of copper, i.e. they are not just joined by thin slivers of copper; 23) Check that any tracks that require special routing considerations such as Kelvin connections to low value current sense resistors or increased clearances for high voltage traces have been correctly implemented; 24) Check clearances of copper on all layers and components on both sides to the edges of the board; 25) Check that no traces have been set to hidden in the Design Manager Nets list; 26) Use the Design Manager (the Design button in the left hand panel) to check that all components are present in both the schematic and the PCB and that all nets have at least two connection; 27) Use the Design Manager (the Design button in the left hand panel) to check, investigate and correct all DRC errors. A completed PCB design should have no DRC errors; 28) Check that the Gerbers to be generated are from the correct version of the PCB layout. It may have changed as a result of the above checks so always regenerate the Gerbers from the latest version unless there is a specific reason to use them from an earlier version. Putting a version number on the PCB helps but is not perfect as this has to be updated manually anyway; 29) Download and check items (6) to (24) in the Gerbers in either the EasyEDA Gerber Viewer: https://gerber-viewer.easyeda.com/ or using a 3rd party Gerber viewer such as the free and open source gerbv: https://sourceforge.net/projects/gerbv/files/gerbv/ 30) Check the order options such as number of boards, copper finish, silk screen colour, solder mask colour, panellisation, any solder paste mask requirement and so on; 31) Lastly, check that the order is being placed with the correct delivery option. The default delivery method is by express courier. This is the most expensive option but avoids the mistake of ordering boards that are needed urgently with a slow delivery method. #Skill#
example 2016-09-23 06:50:34 comment 1 0 Circuit Design
D move Hotkey not working in V3.7.2
BUG Concise problem statement: The D Hotkey no longer has any effect after updating to V3.7.2 Steps to reproduce bug: Press D key; Click on an object; Move mouse; Results: Nothing happens Expected results: Object should move without dragging attached wires etc. Browser: Chrome & Firefox in LinuxMint 17.2 KDE #BugReports#
example 2016-07-23 02:01:16 comment 1 0 Bug Reports
Wrong file exported or printed when exporting or printing saved WaveForm plots
BUG Concise problem statement: When exporting or printing saved WaveForm plots, a completely different file is exported or printed. Steps to reproduce bug: Run a sim; Save the WaveForm file (see also: https://easyeda.com/forum/topic/Problem_saving_waveform_plots-UJjTfdXiE) For example, this waveform: Do: Document > Export or Document > Print Results: Export as pdf: Print: Expected results: Export or print the waveForm plot. Browser: Chrome & Firefox in Linuxmint KDE 17.2 (based on Ubuntu 14.04) #BugReports#
example 2015-10-14 05:56:43 comment 3 0 Bug Reports
Problem saving waveform plots
BUG Concise problem statement: Saving a WaveForm plot under a target project creates a new Project with the name of the saved plot but (i) the plot is not saved as a file under the target project and (ii) the new Project created when saving the WaveForm plot does not contain a plot. Saved plots cannot then be found. Steps to reproduce bug: Run a sim then do: Document > Save to save the WaveForm plot; Name the plot file; Select the target project to save the plot file under. Results: New Project is created with the same name as the plot file but the plot file is not shown in either the new Project or the selected target project. Expected results: Saved plot file should be shown under selected target Project. Browser: Chrome & Firefox in Linuxmint KDE 17.2 (based on Ubuntu 14.04) #BugReports#
example 2015-10-14 05:43:26 comment 3 0 Bug Reports
Has Example's simulation limit been reduced or used up by another user?
BUG Concise problem statement: I have been running sims ([removed]
example 2015-10-08 06:25:04 comment 2 0 Bug Reports
Don't understand this error
BUG Hi Dillon, I don't think this is a bug. I think it is something I have forgotten or done wrong. Can you tell me what is my mistake? :) Here is my problem: When I first passed Tesseract into PCB it did not have any of the 4 off 3.5mm mounting holes in the PCB. I added 4 off 3.5mm holes to the PCB but then realised that every time I did Import changes, the holes were deleted because they were not in the schematic. So I created the symbol named unplated_M3_clearance_hole with a prefix of 3M5_H? and added 4 of them to the schematic and assigned them the footprint hole_3mm5. That fixed the problem with Import changes. But now there is a problem that when I try to generate a new PCB from the schematic, I get this error: Steps to reproduce bug: Create a schematic Place unplated_M3_clearance_hole Convert to PCB... Results: Get the error message. #BugReports#
example 2015-07-25 05:46:46 comment 2 0 Bug Reports
Cannot attach subckt to spice symbol using `Edit subckt...`
BUG Concise problem statement: Can no longer attach a subckt to a spice symbol using Miscellaneous > Edit subckt.... Can paste in a subckt and save symbol after Update subckt ok! message but once symbol is closed and reopened, doing Miscellaneous > Edit subckt... again shows no subckt in dialogue box. Steps to reproduce bug: Open Spice symbol for editing (for example, new symbol, CD4093EE); Do Miscellaneous > Edit subckt... and paste subckt of same name as symbol (CD4093EE) into Attach a spice subckt to this symbol box; Click OK; Observe Update subckt ok! message; Save spice symbol; Close symbol; Reopen symbol; Do Miscellaneous > Edit subckt... Results: Attach a spice subckt to this symbol is empty. Expected results: Attach a spice subckt to this symbol should contain the previously posted subckt. Browser: Chrome in W7 Pro Firefox in Kubuntu 12.04 LTS. #BugReports#
example 2015-07-10 06:15:01 comment 2 0 Bug Reports
Move pin name attribute corrupts pin start XY co-ordinates
BUG Concise problem statement: Moving the name attribute of a pin changes the XY co-ordinates of the pin Start-X and Start-Y. This should not happen. Steps to reproduce bug: New schematic symbol > place pin at Start-X = 0, Start-Y = 0 Observe that pin attribute shows Start-X = 0, Start-Y = 0 Move name attribute up by grid snap interval (10) Results: Observe that pin attribute now shows Start-X = -22, Start-Y = -7 However, actual pin start XY on canvas has not moved. This causes symbols to misalign when placed on schematic canvas but with no obvious reason. It is very confusing for users. Moving the name back to the default position, resets the Start-X and Start-Y to 0, 0. Expected results: Moving the name attribute should not affect the reported pin start XY co-ordinates. Browser: Chrome, Firefox. #BugReports#
example 2015-06-23 06:34:53 comment 0 0 Bug Reports
Share my works Short URL opens file, URL opens .png
BUG Concise problem statement: In the "Share my works" dialogue, Short URL allows the user to open the file in EE Editor. However, URL only allows the user to open a .png of the schematic/symbol/pcb/footprint. Is that correct? If yes, then I think the buttons should be renamed to Short URL and .png image #BugReports#
example 2015-06-23 05:43:07 comment 0 0 Bug Reports
URL links to files , updated to V2.6.6, are broken.
BUG Concise problem statement: Before V2.6.6, links to files looked like this: http://easyeda.com/file_view_Voltage-or-current-controlled-resistors_nztLFXewO.htm They now look like: https://easyeda.com/file_view_Voltage-or-current-controlled-resistors_nztLFXewO.htm with https in place of http However, the new link does not find the target file. Instead, there is a "Page not found message". There are a couple of examples here: https://easyeda.com/forum/topic/Time_controlled_switch-wxrlDx1xq where the links have been updated but no longer work. #BugReports#
example 2015-06-23 05:18:08 comment 0 0 Bug Reports
Moving files from one project to another loses files!
BUG Concise problem statement: To reduce the number of files in any one project, I just started moving files from "Spice simulation skills" to "Spice simulation skills 02". Moved files are gone from "Spice simulation skills": OK Moved files are NOT in "Spice simulation skills 02". Not OK They seem to have just disappeared! Because I have moved files before with no problems, I did not make a copy of them first and did not note the names of the files I was moving. Therefore I cannot search for them because I do not remember the names. The files do not appear in the Crash recovery lists so I appear to have lost about 5 or 6 files. Not happy. :( I think the problem is to do with the "02" at the end of the project name. If I move files between projects with completely different names, they move OK. Browser: Firefox. #BugReports#
example 2015-06-22 06:09:46 comment 3 0 Bug Reports
Net corruption in Design Manager?
BUG Concise problem statement: In: https://easyeda.com/editor#id=qoiASa4mE When I check the V- net in the Design Manager, it shows me that U3 pin 1 is connected to V- (the GND net). This not what the schematic shows. What the schematic shows is correct (i.e. it shows what I drew and what I intend) and what the Design Manager says is wrong. So there must be something getting corrupted. Can you spot the error? #BugReports#
example 2015-06-20 05:56:18 comment 1 0 Bug Reports
Footprint not listed in dropdown list
BUG Concise problem statement: Footprint not listed in dropdown list To work around the problem that it is not possible to search for anything like 6.35mm because the decimal point and everything to the right of it is discarded, I made two new footprints: 6dot35mm_switched_3_pole_jack_skt_w-mono_plug 6dot35mm_switched_3_pole_jack_skt_Neutrik_NMJ6HFD2 and a footprint: 6dot35mm_switched_3_pole_jack_skt_Neutrik_NMJ6HFD2 They are in andyfierman's My Parts and can be found using Shift+F. But, when I place them in a schematic and try to choose the 6dot35mm_switched_3_pole_jack_skt_Neutrik_NMJ6HFD2 footprint, this does not appear in the dropdown list. Even if I manually enter the 6dot35mm_switched_3_pole_jack_skt_Neutrik_NMJ6HFD2 footprint into the Package field, if I try to pass it through to PCB I get an error: This is an example: https://easyeda.com/editor#id=Vz4YSM4mE and this is the Tesseract circuit (which is the new project to help show off the new website) where I first found the problem: https://easyeda.com/editor#id=qoiASa4mE Could the problem be that the names I have given them are just too long? #BugReports#
example 2015-06-19 06:36:21 comment 4 0 Bug Reports
Unconnected pin on subpart but cannot see why.
BUG Concise problem statement: Unconnected pin on subpart but cannot see why. In: https://easyeda.com/editor#id=qoiASa4mE I have placed two TL084 multi=part devices. When I run the Design Manager it tells me that U3 pin 11 is unconnected. I cannot see why: I have moved the device to see if the wire is dragged, redrawn the wires and ground symbol, moved the power pins to a different sub part, deleted and replaced the sub part, checked everything is on-grid but it still reports that U3 pin 11 is unconnected. The thing that I really don't understand is that it's only pin 11 on U3 that is flagged as unconnected. Pin 11 on U1, the other TL084 is OK. Can you see what the problem is? #BugReports#
example 2015-06-19 06:12:43 comment 3 0 Bug Reports
Error in X-axis formatting in AC Analysis
BUG In a linear AC Analysis set up like this: ac lin 100 5k 25k in WaveForm, the X-axis is plotted from 100Hz to 100kHz on a LOG (Decade) scale. This is wrong. The X-axis should plot from 5kHz to 25kHz on a LINEAR frequency scale. This is illustrated in: https://easyeda.com/editor#id=cyrJ1jdvN Can this be corrected in WaveForm? :) Andy. #BugReports#
example 2015-05-14 00:11:40 comment 2 0 Bug Reports
How to search all topics in the Forum.
To search for any word or phrase in the title of any post. In the browser url bar, enter: https://easyeda.com/bbs_lists_0.htm to list all topics then CTRL+F To search for any word or phrase in the title or the content of any post: In the browser url bar, enter: site:easyeda.com [my search phrase] where [my search phrase] is whatever words or phrases you are looking for in the title or the content of any post. #Skill#
example 2015-04-15 22:35:48 comment 3 0 Circuit Design
EasyEDA upgraded: 9/9 V1.9.1
Now supports GitHub Flavored Markdown https://help.github.com/articles/github-flavored-markdown https://easyeda.com/language.php New language translate package, It is easier to translate and verify. New Tutorial file https://easyeda.com/Doc/Tutorial/ Open File Format https://easyeda.com/Doc/Open-File-Format/ https://github.com/dillonHe/EasyEDA-documents Github host all of our documents, If you like to contribute, try to fork. #GeneralDiscuss#
example 2015-04-01 16:24:08 comment 4 0 Others
Properties panel stuck open in Sandbox 2.3.1 in Chrome Version 41.0.2272.76 (64-bit)
When the Properties panel is hidden, the Toggle right bar is visible and can be used to open the panel. Once the panel is open, the Toggle right bar is no longer visible and so the Properties panel is stuck open. If a simulation is run then the panel auto hides. (The panel behaves the same if the Design Manager is selected.) #BugReports#
example 2015-03-10 21:55:32 comment 4 0 Bug Reports
Cannot move or resize Toolbars in Safari on iPad. V1.9.1 and V2.1.1
Can shade/unshade them and can open and close using Config tab but cannot slide them around. #BugReports#
example 2015-01-30 17:35:15 comment 11 0 Bug Reports
Sim runs with 4060EE model pasted in but not from model in library (V1.9.1 and V2.11)
Not sure what I have done wrong (or forgotten to do). http://sandbox.easyeda.com/editor#id=suB7D9rJD Is this because the symbol and sim are built in V2.1.1? #BugReports#
example 2015-01-30 04:34:09 comment 7 0 Bug Reports
Can no longer place netlabel on GND net (allowed in V1.9.1 but not in V2.1.1)
V2.1.1 does not allow placing netlabel on GND net. Why is this a problem? V1.9.1 allows placing a netlabel on the GND net. Like this: https://easyeda.com/editor#id=80AyvtrNn V2.1.1 does not. So to do what the first schematic shows in V2.1.1 we now have to do it like this: http://sandbox.easyeda.com/editor#id=h3s2ecaw5 This makes setting up the supplies for new logic devices when using hidden pins more complicated (but maybe it is more clear to the user this way?). #BugReports#
example 2015-01-23 00:14:06 comment 4 0 Bug Reports
Need to be able to run longer (more data) simulations
In trying to develop a UC3843 SMPS controller model (and almost anything else to do with SMPS and Class D amplifier with lots of switching) I keep hitting the simulation too large: display cut to 10k points limit. I know this is a cost issue because bigger sims use more memory/disk but users are asking for things like the UC3843 SMPS controller and the 4060 14 bit self oscillating counter so they will expect to be able to run much longer sims. The UC3843 and 4060 models are not public yet but I think we will need to find a way to increase simulation limits soon. For the moment I can do development of long sims at the netlist level on ngspice.com but it is hard to check things at the schematic level in EE because I can't see enough of a long sim. :) #FeatureRequests#
example 2015-01-22 20:55:54 comment 2 0 Feature Requests
Hidden pins problem with spice symbol in Sandbox V.2.1.1.
"Too few parameters for subcircuit type "half74hc74ee" (instance: xxu3)" error when using spice symbol with hidden pins in Sandbox V.2.1.1. Create a spice symbol with hidden power pins (example: VDD and VSS pins in HALF74HC74EE); Place it in schematic and connect it up; Run sim; Npgspice reports not enough connections to subckt: Too few parameters for subcircuit type "half74hc74ee" (instance: xxu3); Netlist shows no connections to VDD and VSS pins; Click on symbol and type I; Tick Hidden pins; Connect up hidden power pins, Run sim; Sim runs OK; Netlist shows connections to VDD and VSS pins. Note: untick Hidden pins after tick Hidden pins does not hide pins again. Examples: http://sandbox.easyeda.com/editor#id=eS0wqkd7p|h3s2ecaw5#Bug Reports#
example 2015-01-22 18:09:04 comment 0 0 Bug Reports
Edit prefix problem still present in Sandbox V2.1.1.
The text in-place prefix edit problem described in: http://sandbox.easyeda.com/bbs_view_2048.htm still occurs after I try to enter a prefix that has already been used in the schematic, even if the number is no longer in the schematic. Example: i) Place two voltage sources V1 and V2 in a schematic. ii) Edit V1' toV3`. That works OK. iii) Edit V3' back toV1`: the Prefix Conflict window pops up and says that the prefix I have chosen already exists. iv) The prefix is now showing V4. After that, I can only enter a prefix with a number greater than any I have already entered, even if no device with that prefix number exists in the circuit. It looks like a problem with the list of refoxes entered and used in the schematic. If I edit V4' toVpsu, and then editVpsutoV4then the Prefix Conflict window pops up and says that the prefix I have chosen already exists and the prefix becomesV5`. But if I then edit V5' back toVpsu`, then that works OK. #BugReports#
example 2015-01-22 17:51:45 comment 0 0 Bug Reports
Need better error reporting from ngspice
Please see: http://sandbox.easyeda.com/bbs_view_2108.htm #BugReports#
example 2015-01-22 17:30:57 comment 6 0 Bug Reports
Get "Simulation too large" warning but I don't think that is the problem.
BUG I'm hoping you can help me with a problem I'm having running a netlist. It is for a UC384x series SMPS converter, converted from LTspice to ngspice. http://sandbox.easyeda.com/editor#id=BHFfAy864 Running it, I get the "Simulation too large" warning but I don't think that is the problem. I have tried to run it in ngspice.com: http://www.ngspice.com/index.php?public_circuit=4P00Ya but that fails and gives me this error: "Can't use .control statements with ngspice.com." The problem there is that there are no .control statements in the copy that I have posted onto ngspice.com. I cannot spot anything that might be misinterpreted as a .control class of statement. This is why I think the problem may not be just because EasyEDA thinks the simulation is too large: I think there is something about the syntax that is wrong but I cannot see it and am not getting enough debug information to get any further. Here are the things I have done to try to debug the error: *I've put the whole netlist into different text editors to see if there are any hidden or mistranslated characters and found nothing. *I have tested the stuff in here: ******************************************************** * Quiescent current drain ******************************************************** Bqui1 vp 0 I=V(vcc_bad)*V(vp) / 30k + (1-V(vcc_bad))*V(vp) / 1.36k ******************************************************** * Supply for error amp gated with vcc_ok ******************************************************** *B2 0 ampvcc I=5 ; uncomment for amp frequency response test B2 0 ampvcc I=5*V(vcc_ok) ; comment out for amp frequency response test R3 ampvcc 0 1 C2 ampvcc 0 1p ******************************************************** * Uncomment the three lines below to carry out amp frequency response test *Btest1 0 half_ref I=V(ampvcc) / 2 *Rtest1 half_ref 0 1 *Ctest1 half_ref 0 1p ********************************************************* * SR latch, NOR gate (and Toggle flip flop for UCx844 / 5 devices only) ******************************************************** aadc1 [delcomp] [delcompd1] adc1 aadc2 [vcc_bad] [vcc_badd1] adc1 aadc3 [ref_bad] [ref_badd1] adc1 ** * SR latch (with all output states defined) * anorgate3 [osc_out PWM_Qp] PWM_Qn nor1 anorgate4 [delcompd1 PWM_Qn] PWM_Qp nor1 * apullup1 pullup pullup1 ; only used for UCx844 / 5 parts *atflop1 pullup osc_out null null null QNd1 tflop1 ; uncomment for UCx844 / 5 devices *anorgate1 [vcc_badd1 ref_badd1 osc_out PWM_Qn QNd1] updrvd1 nor1 ; uncomment for UCx844 / 5 devices anorgate1 [vcc_badd1 ref_badd1 osc_out PWM_Qn] updrvd1 nor1 ; comment out for UCx844 / 5 devices * adac1 [updrvd1] [updrv] dac1 ** * ADC bridge model * .model adc1 adc_bridge(in_low = 0.5 in_high = 0.5) ** * Pullup / down models * .model pullup1 d_pullup(load = 1p) ** * T Flip Flop model * .model tflop1 d_tff(clk_delay = 1n *+ set_delay = default 1n (unused) *+ reset_delay = default 1n (unused) + ic = 2 + t_load = 1p + clk_load = 1p + set_load = 1p + reset_load = 1p + rise_delay = 1n + fall_delay = 1n) ** * NOR gate model * .model nor1 d_nor(rise_delay = 1n + fall_delay = 1n + input_load = 1p) ** * DAC bridge model * .model dac1 dac_bridge(out_low = 0 out_high = 1 out_undef = 0.5 + input_load = 1p t_rise = 40n t_fall = 2n) ******************************************************** and each of the 8 subckts separately. They all work fine. (You can try the test jigs here: http://sandbox.easyeda.com/editor#id=lA6QK2kCw|hnTb5mEyQ|drDYkG2M8|qwqjd7pHZ|qKgasK2Wd|VJDVd7pGY|HJj2o2eAW|Ox7tPN97s|RWw6GEXxv) *I have also taken the whole netlist and removed or commented out each of the subckts in turn but the error persists. *I tried moving the .ends UC3843BEE statement so that the individual subckts were outside the main UC3843BEE subckt. Url: http://sandbox.easyeda.com/editor#id=BHFfAy864Browser:#Bug Reports#
example 2015-01-22 17:29:33 comment 1 0 Bug Reports