Been playing with the latest version for about a week of evenings and it looks pretty good to me .........it may be worth taking another look now.
Cheers, Bob.
Thanks Bob.
Take your time to see how you get on making components that are not RS website. It used to be a real pain in the a*se to make your own component ........ plus doing your own 3D modelling hardly/didn't work at the best of times.
Also before you spend too much time with DesignSpark, take a look at DipTrace, Target 3001 & Proteus. The pin limited versions of all of these are pretty cheap & I would prefer to use any of these over the previous version of DesignSpark anyday.
Been playing with the latest version for about a week of evenings and it looks pretty good to me .........it may be worth taking another look now.
Cheers, Bob.
Thanks Bob.
Take your time to see how you get on making components that are not RS website. It used to be a real pain in the a*se to make your own component ........ plus doing your own 3D modelling hardly/didn't work at the best of times.
Also before you spend too much time with DesignSpark, take a look at DipTrace, Target 3001 & Proteus. The pin limited versions of all of these are pretty cheap & I would prefer to use any of these over the previous version of DesignSpark anyday.
I use DesignSparkPCB simply because it doesn't have any artificial limitations, and initially because of the RS library. The RS library wasn't as useful as I hoped, so I ended up making most of my components' layouts - which I found easy and intuitive. N.B I haven't tried anything w.r.t. 3D modelling.
I now run it in Linux under Wine, so I don't even have to boot into Windoze any more.
FFI,
https://entertaininghacks.wordpress.com/2015/03/25/designing-pcbs-with-surface-mount-components/
Giving it a whirl this week. Absolute hell on earth so far. The potential is there to be awesome and well integrated with RS (who is who I order through 99.999% of the time already), but it fails so hard at every corner. I feel like I'm getting what I paid for haha.
Also, am I far beyond sleep deprived, or is there a quirk where diodes mysteriously change direction from schematic to PCB? I don't know whether it's a fault in Modelsource or what, but on the board I'm laying out right now every single diode is in the correct direction on the schematic, but has its markings reversed on the PCB. Good thing I'll be assembling myself, that'd let the smoke out pretty quick if nobody caught it.
Also, am I far beyond sleep deprived, ...
In which case it might be better to wait before fabbing (or posting)
We've all had mornings where we wish we had gone home two hours earlier the previous night.
Take your time to see how you get on making components that are not RS website. It used to be a real pain in the a*se to make your own component ........ plus doing your own 3D modelling hardly/didn't work at the best of times.
Also before you spend too much time with DesignSpark, take a look at DipTrace, Target 3001 & Proteus. The pin limited versions of all of these are pretty cheap & I would prefer to use any of these over the previous version of DesignSpark anyday.
Yes, that is a good plan - no point rushing at it. I used OrCad a bit in the distant past and I was not a fan - but that was dictated by job requirements so choosing one I don't end up hating will be worth the time taken
Cheers, Bob.
Also, am I far beyond sleep deprived, ...
In which case it might be better to wait before fabbing (or posting) We've all had mornings where we wish we had gone home two hours earlier the previous night.
That was more of a polite courtesy/joke. It wasn't a sleep thing, it was a Designspark thing. Diode markings were indeed reversed between schematic and board and I couldn't find a way to correct the mistake in the program (I guess I'll have to edit the parts manually but I haven't had time yet). They were diodes from Modelsource, next time I'm working in DS I'll try some other diodes and see if it happens with others.
Diode markings were indeed reversed between schematic and board and I couldn't find a way to correct the mistake in the program
Zener diodes are normally installed in "reverse". Did you choose a zener instead?
Also, you have to allocate the anode & the cathode to each side of the diode in your "pin allocation map". It might be that this allocation is reversed.
Design had a Zener and a couple plain old diodes, same problem with all. I think you're missing the point with the reverse thing, it's not confusion over which way diodes work.
Imagine there's a diode between point A and point B. On my schematic the anode is at point A and cathode is point B. As soon as I switch over to the PCB, the anode is now connected to point B and cathode to point A.
Thanks for he pin allocation tip, I'll check it out. Still, why on earth would the program be designed that way??!! Why wouldn't it just default to following what was drawn on the schematic?
Why wouldn't it just default to following what was drawn on the schematic?
The component "drawing" means little to DesignSpark. As far as it's concerned, it is just a combination of lines that have no intrinsic value.
What does matter is the number of pins & the pin numbers. It sounds like the pin mapping between the schematic part & the footprint have been reversed.
Let's hope so, as it is a quick remedy to swap them over.
Why wouldn't it just default to following what was drawn on the schematic?
The component "drawing" means little to DesignSpark. As far as it's concerned, it is just a combination of lines that have no intrinsic value.
That seems like a MASSIVE oversight to me.
Curiosity has got me now, I'm going to boot up the system and try this pin assignment thing. I'm also going to see if it happens with default library components (as I said before, these were parts from Modelsource so that could be the issue, I know the symbols for the op amps I've used from there are a joke)
Well, as the tree said to the lumberjack...
Opened up that last project and sure enough everything is assigned properly pin wise, but symbols are definitely inconsistent between schematic and board. Standard Designspark diodes work as they should though when I added them as a test, while the original Modelsource ones are messed up.
So out of curiosity I started a new project and added default Designspark diodes as well as the same Modelsource diodes used in the other project. Works fricken perfectly. Maybe I'm going crazy, or it's user error, right? So I open the original project back up and delete the traces to the diodes in question to see if I've somehow manually routed wrong (I know I didn't, because I remember majorly getting the shits about the symbols when I was routing and posting this rant, but let's assume I'm an idiot and messed up). Nope, the thing is still telling me to route them backwards. There is definitely something wrong here.
Ahh, the joys of software.
Well, as the tree said to the lumberjack...
Opened up that last project and sure enough everything is assigned properly pin wise, but symbols are definitely inconsistent between schematic and board. Standard Designspark diodes work as they should though when I added them as a test, while the original Modelsource ones are messed up.
So out of curiosity I started a new project and added default Designspark diodes as well as the same Modelsource diodes used in the other project. Works fricken perfectly. Maybe I'm going crazy, or it's user error, right? So I open the original project back up and delete the traces to the diodes in question to see if I've somehow manually routed wrong (I know I didn't, because I remember majorly getting the shits about the symbols when I was routing and posting this rant, but let's assume I'm an idiot and messed up). Nope, the thing is still telling me to route them backwards. There is definitely something wrong here.
Ahh, the joys of software.
... including models
I remember, back in 19
82 being asked to quote to freate HiLo models of 74xx devices. The client really, seriously, didn't care about their accuracy or correctness. The client was a salesman which a large sale pending on whether or not the simulator had 74xx devices. I think you can guess the rest.
Back to the present. You've piqued my interest. Can you let us know the precise modelsource model so that I can attempt to verify it? Probably necessary to have the Designspark version, although I'm not going to change my version.
Haha, oh man, sounds like a nightmare!
Sure, the diodes are RS part numbers 7087916 and 2513069. I'm in DS 7.0.2.
Haha, oh man, sounds like a nightmare!
No, not at all. We simply declined to quote.
Sure, the diodes are RS part numbers 7087916 and 2513069. I'm in DS 7.0.2.
Using DS 6.x, have a look at the attached schematic and pcb files.
It looks OK to me, apart from the lack of the schottky and zener diode indications on the schematic. That's unnecessarily sloppy to be true, but I don't see a connectivity error.
I'm not overly fond of the diode picture on the pcb, and would prefer that it was inside the outline, but it is pointing in the right direction.
Yeah it worked fine for me too in try fresh test project I created, weird. Still wrong in my original project though, so I don't know, some kind of data corruption maybe? Thanks for double checking mate.
I'm about to lay out another board with those same parts, let's see how this goes.
Installed it (easy enough on Win
added 3D lib (what I wanted in first place) and tryed it out
(now what was that part number?). What a disapointment that I can't search for SRAM, EEPROM, or Regulator. You have to know what the part number is that you want to use and I CAN'T/WONT keep that many numbers in my head so, it's back to Eagle for me