| 00:00.53 | prpplague | T0mW: hmm |
| 00:01.11 | prpplague | T0mW: when doing values for like nWR you can't do lower case? |
| 00:02.26 | T0mW | no, I use "*" for the negation |
| 00:02.36 | T0mW | most people do |
| 00:03.58 | T0mW | prpplague: then, put a dot-pin on the input pin, rather then a straight-pin. |
| 00:04.28 | T0mW | "--O" shows the input is active low |
| 00:05.23 | prpplague | T0mW: a "dot-pin" ? |
| 00:05.42 | prpplague | hmm |
| 00:05.59 | prpplague | cramp this is too artisy |
| 00:06.41 | prpplague | T0mW: can i generically use the i/o designation for the pins or do i have to be very very specific? |
| 00:10.34 | prpplague | T0mW: like i have two clock pins do i need to use the "clkpin" on my symbol? |
| 00:11.31 | T0mW | you can use "i/o" if you are lazy. But, when you run the ERC (Electrical Rules Check) it will tell you that you have an I/O pin connected to POWER or GROUND or ??? |
| 00:11.53 | T0mW | prpplague: I try to use the correct one: I/O, INPUT, OUTPUT, POWER. |
| 00:12.38 | prpplague | T0mW: what about using the clkpin ? |
| 00:12.52 | T0mW | prpplague: that way, I can get the assist from the ERC to find out if I goofed and have two INPUTs wired together and forgot to put an OUTPUT pin on that net. |
| 00:13.08 | T0mW | prpplague: what about the clkpin? |
| 00:13.58 | prpplague | T0mW: do i need to use the "clkpin" pin for clk inputs? |
| 00:15.25 | T0mW | clkpin gives a nice symbol that shows it is a clock pin and then when someone reads the schematic, they can see that the pin is a clock without knowing the datasheet on the device. Same thing for dot-pins, straight-pins |
| 00:15.44 | T0mW | you are conveying information to the reader |
| 00:16.02 | prpplague | ahh ok, so it doesn't effect functionality, just viewability |
| 00:16.21 | T0mW | otherwise, they have to grab a databook to figure out what the pin is. remember that not only engineers read schematics, heh |
| 00:20.27 | prpplague | those dotpins seem hard to read |
| 00:27.48 | prpplague | T0mW: you usually draw you power and ground seperate? |
| 00:30.25 | T0mW | prpplague: yeah, I make a seperate symbol e.g. "vcc-gnd" or "vdd2-gnd3" ... |
| 00:30.37 | T0mW | where "vdd2" says it has two vdd pins |
| 00:31.23 | T0mW | then add that symbol to the device with the main symbol, and set the power symbol to a "request" instead of "next". |
| 00:31.51 | T0mW | this way, you can put all the power pins on a seperate sheet of the schematic |
| 00:31.54 | prpplague | hmm |
| 00:32.13 | prpplague | T0mW: how do you label the multiple VCC ? |
| 00:32.22 | prpplague | VCC1 VCC2 etc? |
| 00:32.23 | T0mW | vcc1 vcc2 vcc3 |
| 00:32.45 | T0mW | and, make it a POWER pin |
| 00:32.46 | prpplague | T0mW: ok one more question, the gnd's are power pins as well correct? |
| 00:33.03 | T0mW | correct, so is +3v3, -5v, etc |
| 00:33.16 | T0mW | it is a TYPE |
| 00:34.15 | T0mW | POWER goes to POWER of same base name. e.g. you will get a warning if you tie a VDD to a VCC POWER pin. But, you get an error if VDD is tied to an OUTPUT or I/O pin. |
| 00:34.20 | T0mW | etc. |
| 00:35.04 | T0mW | prpplague: hey, you could do like some of them do, ignore the netlist entirely and use the CAD package as an electronic easel. |
| 00:35.53 | T0mW | prpplague: seen a few guys screw boards doing it that way. You had no idea if they had the board wired as shown in the schematic |
| 00:36.35 | T0mW | prpplague: I had one A## Hole do a complex CPU board that way, he might as well just used mylar and taped it up. |
| 00:37.52 | T0mW | prpplague: I'm building a code translator to translate 8070 asm source code files into ARM asm. |
| 00:38.04 | T0mW | yuk |
| 00:40.29 | prpplague | hehe |
| 00:40.44 | prpplague | T0mW: i want one that would translate z80 code from the gb to arm |
| 00:41.17 | prpplague | T0mW: i didn't do the VCC and GND on seperates for this, as their is only 3 of each |
| 00:41.18 | T0mW | prpplague: you got the source? |
| 00:41.27 | prpplague | hehe, no |
| 00:41.33 | prpplague | T0mW: binary |
| 00:41.34 | T0mW | tough |
| 00:41.44 | prpplague | hehe yea |
| 00:41.58 | T0mW | you have to disassem first, then you can port it. |
| 00:42.09 | prpplague | yea i know just too lazy |
| 00:42.57 | *** join/#edev redblue (i=star@ppp149.109-253-207.mtl.mt.videotron.ca) |
| 00:45.16 | prpplague | ok symbol done |
| 00:49.03 | prpplague | hmm |
| 00:49.15 | prpplague | T0mW: how do you add that "name" "value" items? |
| 00:49.57 | T0mW | as text on layers "name" & "value" |
| 00:50.08 | T0mW | as text on layers "name" & "value" for the symbol |
| 00:50.24 | T0mW | as text on layers "topname" & "topvalue" for the package |
| 00:51.00 | T0mW | as text on layers "tnames" & "tvalues" for the package |
| 00:51.16 | prpplague | T0mW: is it just "NAME" or is it ">NAME" ? |
| 00:51.27 | T0mW | prpplague: best to look at another package to see how they did things, use the "Inquire" |
| 00:51.31 | T0mW | >name |
| 00:51.34 | T0mW | >NAME |
| 00:51.39 | T0mW | either |
| 00:52.09 | T0mW | prpplague: then, the Device you give the text for ">NAME" to go by. |
| 00:59.33 | prpplague | T0mW: ok all done |
| 00:59.39 | prpplague | T0mW: wonder if it will work |
| 01:01.00 | T0mW | prpplague: see if the magic smoke stays inside the chips? |
| 01:02.06 | prpplague | T0mW: hehe it will take atleast two months to answer that question :( |
| 01:02.58 | T0mW | prpplague: ah, so 2 months would be a "quick turn" for you then? |
| 01:03.02 | prpplague | T0mW: not to mention all the other items that might be an issue |
| 01:03.06 | prpplague | T0mW: oh yea |
| 01:03.14 | prpplague | T0mW: major quick |
| 01:03.44 | prpplague | T0mW: if i sent it off today, i probably won't see it for atleast 60 days probably 90 |
| 01:03.53 | T0mW | prpplague: you've got to get yourself one of those disreputable fisherman who will deliver the goods to you directly. heh |
| 01:04.21 | T0mW | prpplague: a fisherman with a Florida / Mexico POB |
| 01:04.28 | prpplague | no, i just need to get my f'n congressman to push our visa/greencard through |
| 01:04.41 | T0mW | prpplague: the slow-boat may be your fastest delivery :P |
| 01:07.45 | prpplague | T0mW: i'm think of doing the board in pieces first |
| 01:11.26 | prpplague | T0mW: you've got mail |
| 01:11.43 | T0mW | prpplague: I know, it is all spam |
| 01:11.49 | prpplague | hehe |
| 01:11.57 | prpplague | T0mW: mine too? |
| 01:14.36 | T0mW | prpplague: typically pin 1 is a square pad |
| 01:14.51 | T0mW | prpplague: for through hole that is |
| 01:15.02 | prpplague | T0mW: you talking about the plcc? |
| 01:15.18 | T0mW | package: pixter |
| 01:15.29 | T0mW | plcc's also |
| 01:15.42 | prpplague | T0mW: yea, the pixter isn't marked that way either |
| 01:15.48 | T0mW | so, when you flip the board over, you can spot pin 1 to orient yourself |
| 01:15.59 | prpplague | T0mW: all the plcc ones i looked it it didn't have one |
| 01:16.07 | prpplague | T0mW: i guess i could add one easy enough |
| 01:18.36 | T0mW | prpplague: you need a prefix for the devices: e.g. plcc would be "U", the connector could be "P", etc. |
| 01:18.59 | T0mW | prpplague: that way, your schematic gets "U1", "U2" etc, instead of "U$1" |
| 01:19.24 | prpplague | T0mW: oh how do i set that? |
| 01:20.12 | T0mW | prpplague: from the librarian, in the DEVICE, there is a button that says "PREFIX" |
| 01:20.20 | prpplague | ahh ok |
| 01:20.25 | T0mW | prpplague: staring right at you dummy |
| 01:20.28 | T0mW | sheesh |
| 01:20.29 | T0mW | heh |
| 01:20.56 | T0mW | prpplague: you get punchy doing this stuff, heh |
| 01:21.42 | prpplague | T0mW: just the wording |
| 01:21.59 | prpplague | T0mW: it feels very non-intuitive |
| 01:23.03 | prpplague | T0mW: so now all i lack is the TI TPS61027 chip |
| 01:23.07 | T0mW | prpplague: I wouldn't have put the power pins on the SL811HS, it won't hurt anything, but I like to create another symbol for those pins. then add both symbols (SL811HS + the power) to the DEVICE |
| 01:23.28 | prpplague | T0mW: yea thats what i gathered |
| 01:23.31 | T0mW | prpplague: as long as dimensions are ok, it should work for you. |
| 01:23.55 | T0mW | prpplague: did you check the solder and paste masks? |
| 01:24.18 | prpplague | T0mW: no, what am i looking for? |
| 01:25.02 | prpplague | T0mW: i don't see those listed |
| 01:25.27 | T0mW | prpplague: tstop, bstop and cream layers, cream == solder paste |
| 01:25.36 | prpplague | oh ok |
| 01:25.42 | prpplague | T0mW: what am i looking for? |
| 01:26.26 | T0mW | prpplague: open the package in the librarian (or the board with the layout) and make those layers visible |
| 01:26.36 | prpplague | done |
| 01:27.46 | prpplague | T0mW: what do i need to be looking for? |
| 01:27.51 | T0mW | prpplague: notice that the tssop has a cream layer and the others don't? that is how it should be, SMD parts have cream layers, through hole won't |
| 01:28.32 | T0mW | prpplague: you've read the sparkfun site about the solder paste stuff? |
| 01:29.17 | T0mW | prpplague: the cream layer gerber is what you send to pololu.com to have them laser cut a stencil for you. |
| 01:29.23 | prpplague | just briefly |
| 01:29.46 | prpplague | T0mW: why do they call it cream instead of pastemask? |
| 01:29.57 | T0mW | shrug |
| 01:30.20 | prpplague | see thats the kind of stuff thats kept me from being able to do this, heeh |
| 01:30.27 | T0mW | maybe because too many people associate the word "mask" with "soldermask"? |
| 01:30.41 | prpplague | T0mW: so everything looks good? |
| 01:30.45 | T0mW | yeah |
| 01:31.03 | prpplague | oh ok i thought you were trying to point out a mistake |
| 01:31.29 | prpplague | T0mW: hey, one the pixter connection |
| 01:31.41 | prpplague | T0mW: what distance do you calculate between those holes? |
| 01:34.18 | T0mW | prpplague: 75 X 100 |
| 01:34.45 | T0mW | prpplague: pin to pin is 100, row to row is 75 |
| 01:35.22 | prpplague | T0mW: yea thats what its suppose to be |
| 01:36.12 | prpplague | T0mW: http://www.jbevren.net/pixter/devboard.jpg |
| 01:36.21 | prpplague | T0mW: you can see the header there |
| 01:36.40 | T0mW | prpplague: you set the grid to 5mil, then drop a MARK insidet a hole center, then move you cursor to hover over another hole center. You'll see the () measurement change, the x,y within parens is the relative measurement: distance between MARK and cursor |
| 01:37.00 | prpplague | T0mW: yea, thats what i did, just making sure |
| 01:37.31 | prpplague | T0mW: that was originally a 68 pin scsi connector |
| 01:37.38 | prpplague | T0mW: hehe took me all night to find that |
| 01:40.20 | prpplague | T0mW: the only problem i have is i can't think of what kind of pins to use to connect that |
| 01:40.47 | prpplague | T0mW: the thru-holes on the pixter are too small for normal .030" square pins |
| 01:41.07 | prpplague | T0mW: looks like they are .025" round |
| 01:44.20 | T0mW | prpplague: it might be a custom connector made specially for them in China, like there is a guy with a small connector manufacturing plant and he doesn't know about making standard stuff, so he whips up whatever he dreams up. |
| 01:45.02 | T0mW | prpplague: or, they have a lot of campbell's soup cans and he has a brother with a metal shop... |
| 01:45.10 | T0mW | :D |
| 01:45.40 | prpplague | T0mW: hehe, naw, all the holes on the board appear to be either .025" or .020" drills |
| 01:45.52 | T0mW | prpplague: so, the extended family gets together for a week once a month and fills the Pixter order. |
| 01:46.18 | T0mW | dunno |
| 01:47.07 | prpplague | heheh |
| 01:47.18 | prpplague | T0mW: i've seen this before |
| 01:47.24 | T0mW | prpplague: you see http://openzipit.org yet? |
| 01:47.39 | prpplague | T0mW: its basically the same as the at isa connector |
| 01:48.11 | prpplague | neato |
| 01:48.21 | prpplague | T0mW: is the lcd a stn or tft? |
| 01:48.33 | T0mW | prpplague: looks like a tft |
| 01:49.01 | T0mW | prpplague: no shift logic chips on the lcd, so ... |
| 01:49.06 | prpplague | hehe wonder if you could hack the pixter lcd on it |
| 01:49.25 | T0mW | prpplague: probably could |
| 01:49.36 | T0mW | prpplague: the lcd supply would need to be changed |
| 01:50.39 | T0mW | prpplague: I registered that last weekend, then spent some time learning something about css (cascading style sheets) to make it work with konqueror and Internet Explorer. |
| 01:50.59 | prpplague | T0mW: oh thats your page? |
| 01:51.07 | T0mW | prpplague: yeah |
| 01:51.47 | prpplague | T0mW: cool |
| 01:51.56 | T0mW | nod |
| 01:51.59 | prpplague | T0mW: hmmm |
| 01:52.19 | T0mW | prpplague: I wanted to play with the itsy package stuff and needed a URL for it, so... |
| 01:52.22 | prpplague | T0mW: are most .1" pins .030" square or .025" ? |
| 01:52.42 | prpplague | itsy package stuff? |
| 01:52.49 | T0mW | prpplague: you cannot make a blanket statement about pinsizes |
| 01:53.30 | prpplague | T0mW: yea just trying to figure out what i have in my hand |
| 01:53.33 | T0mW | prpplague: I've seen any number of sizes, mostly I measure or use 0.040" holes to be safe, if it is 0.042 pins, oh well, I force them in |
| 01:54.20 | prpplague | hehe i have oneon the way |
| 01:55.19 | prpplague | they almost fit |
| 01:55.26 | prpplague | i could probably force them |
| 01:55.38 | prpplague | just didn't want to damage anything |
| 01:58.46 | T0mW | God gets Credit, all others pay cash |
| 01:59.34 | T0mW | prpplague: I hope to be able to recover the material costs of building those boards through some sales |
| 02:06.25 | prpplague | T0mW: pins like whats on a dip socket fit ok in these holes |
| 02:13.25 | *** join/#edev agaffney (n=agaffney@gentoo/developer/pdpc.active.agaffney) |
| 02:21.38 | prpplague | T0mW: having serious trouble deciding what to do first |
| 02:28.20 | T0mW | prpplague: what's that? |
| 02:29.52 | prpplague | T0mW: trying to decide what designs to do first |
| 02:31.15 | prpplague | T0mW: here are the items i want to do, a sd/mmc interface, a usb host interface, a nor flash interface, and jtag |
| 02:31.30 | prpplague | T0mW: just can't decide if i should do all at once, or one at a time |
| 02:32.05 | prpplague | T0mW: and i can't decide if i want to do it as a dev board first or go for the glory and go directly to some sort of upgrade board |
| 02:32.57 | T0mW | heheh |
| 02:34.14 | T0mW | prpplague: you just have to accept the fact that the first proto is never "right", either a problem with a footprint on the pcb, or you goofed on the wiring, or got the wrong part on the board.. |
| 02:34.25 | prpplague | yea |
| 02:34.35 | prpplague | i can't decide on what to do first though |
| 02:35.00 | T0mW | prpplague: If it were easy, anyone could do it, if it were fun, then everyone would do it, but since it isn't easy nor fun, we get paid to do it. |
| 02:35.25 | prpplague | T0mW: i disagree on the fun part, i find it totally enjoyable |
| 02:35.25 | T0mW | prpplague: it's a skill that has to be acquired. |
| 02:35.30 | T0mW | LOL |
| 02:35.34 | T0mW | sadist |
| 02:35.39 | prpplague | hehe |
| 02:36.17 | T0mW | I don't mind doing stuff I'm interested in, but some of the customer stuff is boring. |
| 02:37.11 | T0mW | prpplague: like this code translator, technically it is an interesting challenge, but, where would I ever need such a thing again? |
| 02:37.22 | prpplague | hehe |
| 02:39.43 | prpplague | T0mW: i think i'm gonna just do an adapter board first |
| 02:40.06 | prpplague | T0mW: convert that darn 75 x 100 to a 100x100 pins |
| 02:40.31 | T0mW | prpplague: once you can get someplace where you can get boards delivered to you in 7..10 days, get parts in 7 days, ... |
| 02:40.53 | prpplague | T0mW: yea |
| 02:41.10 | T0mW | prpplague: do your first board, then you'll see how easy it really is. |
| 02:57.07 | *** part/#edev flyback (i=flyback@c-67-165-88-141.hsd1.pa.comcast.net) |
| 03:56.19 | *** join/#edev tuxmaniac (n=aanjhan@unaffiliated/tuxmaniac) |
| 03:56.20 | *** join/#edev agaffney (n=agaffney@gentoo/developer/pdpc.active.agaffney) |
| 04:20.22 | T0mW | prpplague: I wrote: (^.*(["]+).*(["]+).*;)|(^[ \t]*;) |
| 04:20.29 | T0mW | prpplague: and I know what it meant! |
| 04:20.43 | T0mW | :P |
| 04:31.24 | *** join/#edev J4k3 (n=jsuter@lfkn-adsl-dhcp-72-26-13-176.consolidated.net) |
| 06:45.07 | *** join/#edev MonMotha (n=monmotha@cpe-71-65-44-42.indy.res.rr.com) |
| 07:04.55 | *** join/#edev tuxmaniac (n=aanjhan@unaffiliated/tuxmaniac) |
| 07:16.53 | *** join/#edev ThiefOfBaghdad (n=aanjhan@unaffiliated/tuxmaniac) |
| 08:03.17 | *** join/#edev J4k3 (i=jsuter@dhcp-12-197-128-60.intrastar.net) |
| 08:48.00 | *** join/#edev chouimat|Zzzz (n=dieu@r2351064.cidc.net) |
| 10:12.42 | *** join/#edev EvilDevil_ (n=miau@p54A6DB5A.dip.t-dialin.net) |
| 10:36.25 | *** join/#edev dfarnsworth (n=dfarnswo@216.208.38.107) |
| 11:14.36 | *** join/#edev redb1ue (i=star@ppp072.108-253-207.mtl.mt.videotron.ca) |
| 11:45.26 | *** join/#edev dyoung (n=dyoung@cpe-66-8-152-251.hawaii.res.rr.com) |
| 14:29.10 | *** join/#edev elvueno (n=elvueno@84.120.211.7) |
| 14:40.29 | *** join/#edev agaffney (n=agaffney@gentoo/developer/pdpc.active.agaffney) |
| 14:53.37 | CP|Laptop | BORING! |
| 15:04.19 | chouimat | morning |
| 15:07.46 | CP|Laptop | sigh - did you see the ATI/AMD rumors are back? |
| 15:08.02 | CP|Laptop | what an absolutely horriblye time to be an employee of AMD |
| 15:12.03 | chouimat | CP|Laptop: no ... |
| 15:15.39 | chouimat | CP|Laptop: reading slashdot right now ... ok are those rumors true? /me ducks |
| 15:15.57 | CP|Laptop | I dunno |
| 15:16.31 | chouimat | CP|Laptop: I bet it must be fun ... so how are the talks this year? |
| 15:17.10 | CP|Laptop | Ok, I guess |
| 15:17.17 | CP|Laptop | there have been some pretty boring and/or stupid ones |
| 15:17.41 | chouimat | stupid ones... cool about how to install linux on your toaster? |
| 15:17.57 | CP|Laptop | heh - not so far |
| 15:18.09 | CP|Laptop | usual Xen stuff |
| 15:18.18 | CP|Laptop | All the embedded stuff has been crap |
| 15:18.43 | chouimat | k i see ... who need a presentation about xen ... just rtfm :) |
| 15:19.06 | CP|Laptop | Xen is cool though |
| 15:19.42 | chouimat | it's cool I use it on 1 server ... |
| 15:19.50 | CP|Laptop | I'm watching a a Unionfs talk right now, but its not telling me anything I don';t know |
| 15:20.21 | chouimat | CP|Laptop: :) |
| 15:24.10 | CP|Laptop | most of the people here don't know unionfs though - they are asking basic questions |
| 15:24.32 | *** join/#edev J4k3 (i=jsuter@dhcp-12-197-128-60.intrastar.net) |
| 15:27.22 | chouimat | hmmm now I know why I hate debian ... the packagings .... |
| 15:32.20 | *** join/#edev davidc__ (n=davidc__@S01060002b360aacd.vc.shawcable.net) |
| 15:43.21 | CP|Laptop | Well, there I learned something new |
| 15:43.49 | CP|Laptop | mount something RW with unionfs, then make a new branch RW, remount the old branch RO, and it will sanpshot it |
| 15:44.10 | CP|Laptop | that would be useful for updatng the system |
| 15:44.42 | CP|Laptop | you could then overwrite files underneath without freaking out the system |
| 15:44.43 | chouimat | wow ... |
| 15:45.18 | chouimat | CP|Laptop: sound interesting ... and probably less scary than LVM2 or EVMS |
| 15:45.23 | CP|Laptop | definatley |
| 15:45.32 | CP|Laptop | I wouldn't touch LVM with a 10 foot pole |
| 15:46.39 | chouimat | I tried it ... it's interesting ... but one of the hdd died and I had fun to recover the remaining ones ... but now I understand how it work |
| 15:51.15 | *** join/#edev chouimat (n=dieu@kde/developer/chouinard) |
| 17:04.11 | *** join/#edev dfarnsworth (n=dfarnswo@OTWAON23-1177993857.sdsl.bell.ca) |
| 17:33.59 | *** join/#edev tuxmaniac (n=aanjhan@unaffiliated/tuxmaniac) |
| 17:48.15 | *** join/#edev ThiefOfBaghdad (n=aanjhan@unaffiliated/tuxmaniac) |
| 18:12.06 | *** join/#edev J4k3 (i=jsuter@201.sub-166-145-98.myvzw.com) |
| 18:58.49 | *** join/#edev dfarnsworth (n=dfarnswo@OTWAON23-1177993857.sdsl.bell.ca) |
| 19:10.30 | prpplague | T0mW: ping ping |
| 19:12.30 | T0mW | prpplague: yesss? |
| 19:12.31 | T0mW | heh |
| 19:13.48 | prpplague | T0mW: standard 1/4 watt thru hole resistor? |
| 19:13.57 | prpplague | T0mW: i can't seem to find that on eagle libs |
| 19:14.23 | T0mW | its there: rcl.lib |
| 19:14.33 | prpplague | but whats it called? |
| 19:14.39 | prpplague | the naming is driving me insane |
| 19:16.08 | T0mW | R_US_204/7 |
| 19:16.24 | T0mW | where "7" is the hole spacing: 7mm |
| 19:16.45 | prpplague | ahh ok |
| 19:18.38 | T0mW | 7mm ~= 0.3" |
| 19:19.32 | prpplague | T0mW: ok thanks |
| 19:38.18 | prpplague | T0mW: how do you normally indicate that bus continues on ? |
| 19:38.47 | prpplague | T0mW: most schematics have something like ------>>A[0..23] |
| 19:39.02 | prpplague | but i don't see a way to do that |
| 19:39.39 | T0mW | prpplague: "continues on"? |
| 19:40.25 | prpplague | T0mW: like if you are doing a schematic on three or four pages, and you want to indicate the bus continues |
| 19:43.02 | T0mW | prpplague: not "continues" but what you mean is that you want a specific bus to be on another sheet as well. I know what you mean, OrCad had their EXIT/ENTRY symbols for a sheet hierarchy where you had a main sheet, then child sheets, the interconnection between signals on child sheets had to be via the main sheet wiring (with those special symbols). |
| 19:43.12 | T0mW | prpplague: correct? that is what you mean? |
| 19:43.55 | T0mW | prpplague: in OrCad, if you did not specify (wire up) a signal between sheets, it would not interconnect them. |
| 19:44.02 | *** join/#edev davidc__ (n=davidc__@S01060002b360aacd.vc.shawcable.net) |
| 19:44.16 | prpplague | T0mW: yea, sorta just that i'm using a single sheet, do i have to draw a bus line or does it connect like nets do? |
| 19:46.39 | T0mW | prpplague: you can "airline" the signals, it is not necessary to "railroad" them |
| 19:47.32 | prpplague | T0mW: ok so i need to place some sort of symbol at the end of the bus to indicate that it connects somewhere else , like the -->> ? |
| 19:47.46 | T0mW | prpplague: in fact, "airline" is how you interconnect signals between sheets, just use the same netname for signals on two different sheets and it will assume they are on the same net |
| 19:47.53 | T0mW | prpplague: no |
| 19:48.10 | T0mW | prpplague: in my style of artwork, |
| 19:48.18 | prpplague | T0mW: ahh ok |
| 19:48.46 | T0mW | prpplague: I general put a text at the end of a dangling buss like this: ========= (sht2) |
| 19:48.57 | prpplague | ahh ok |
| 19:49.02 | prpplague | thats what i'll do |
| 19:49.10 | T0mW | "(sht2)" means it also goes to sheet 2, but it has no electrical meaning |
| 19:49.53 | prpplague | T0mW: ok i'll just gonna label the bus contents |
| 19:49.59 | prpplague | T0mW: i.e. A[0..23] |
| 19:50.09 | T0mW | prpplague: there is no "symbols" layer within an electrical context for a shematic. "symbols" layer is inert, it just looks pretty. |
| 19:50.37 | prpplague | yea |
| 19:51.29 | prpplague | hmm |
| 19:51.44 | prpplague | should i use a 2x30 or 2x40 header...... |
| 19:51.44 | T0mW | prpplague: right, name the bus "A[0..23]", draw it around where you need it, then select "net" (next to "bus" button) and click on the bus, a menu will popup listing the signal nets within the bus, choose one and do your wirinng |
| 19:52.07 | prpplague | T0mW: yea i was refering to the text at the end of the bus |
| 19:53.21 | T0mW | prpplague: I usually click on "ABC" (button below the "net" button), then click on the bus, "ABC" will set the visual label of the bus signals, you can then position that label wherever you want and drop it |
| 19:53.47 | T0mW | I find that signoff message of J4K3 offensive |
| 19:54.05 | T0mW | s/offensive/arrogant |
| 19:54.40 | prpplague | ahhhhh |
| 19:54.52 | prpplague | T0mW: yea |
| 19:56.29 | prpplague | T0mW: almost feel comfortable with it now |
| 19:56.40 | prpplague | T0mW: i'll speak to j4k3 about it |
| 19:57.21 | T0mW | prpplague: whatever |
| 19:57.44 | T0mW | prpplague: he is just warning people he is a jerk, heh |
| 19:58.41 | T0mW | prpplague: when you do your wiring, it is good practice to occasionally look at the layout to see if the desired effect on the nets has occured. |
| 20:01.48 | prpplague | ok |
| 20:05.51 | T0mW | prpplague: sold 4 addon boards, not a hot seller, but |
| 20:06.34 | T0mW | or over it |
| 20:07.13 | prpplague | hehe |
| 20:07.22 | prpplague | T0mW: 4 is a good start |
| 20:07.54 | prpplague | T0mW: slowly making progress with the schematic |
| 20:09.53 | prpplague | the layout is really gonna be the problem for me |
| 20:09.58 | prpplague | T0mW: running all those traces |
| 20:47.45 | prpplague | T0mW: do you like that symbol i used for the pixter connector? |
| 20:51.45 | T0mW | yes, it is ok |
| 20:51.57 | prpplague | i don't care for it |
| 20:52.10 | prpplague | just what was there for the scsi connector used |
| 20:52.15 | prpplague | i'm thinking about changing ti |
| 20:56.16 | prpplague | T0mW: all the pins are moveable, they're as part of one object |
| 20:56.35 | prpplague | T0mW: makes it easy on the schematic i guess |
| 20:56.44 | prpplague | T0mW: just doesn't look too good |
| 20:57.27 | T0mW | prpplague: smash it |
| 20:58.08 | T0mW | prpplague: if the device is made up of seperate peices as a whole, you can smash it into pieces and move the pieces around |
| 20:59.36 | prpplague | T0mW: yea, but see i don't want it smashed, it want it grouped |
| 21:01.35 | chouimat|movie | <PROTECTED> |
| 21:01.57 | prpplague | chouimat|movie: hehe, |
| 21:02.12 | prpplague | chouimat|movie: yea chandler had it a couple weeks ago |
| 21:02.17 | chouimat|movie | prpplague: I'm currently freezing :) |
| 21:06.01 | T0mW | finall! |
| 21:06.05 | T0mW | finally! |
| 21:06.59 | T0mW | prpplague: do you know how hard it is to process a comment when examining a line of code programmatically?! |
| 21:07.36 | T0mW | ; old comment ; oh I now did this see "foo" ; |
| 21:07.40 | T0mW | crap like that |
| 21:07.52 | T0mW | or, you have |
| 21:08.14 | T0mW | db "send it; and " ; message foo |
| 21:08.43 | T0mW | 10 hours to figure all the permutations out and handle them |
| 21:08.53 | prpplague | T0mW: yea, that is probably the most difficult part of any code parser, imho |
| 21:09.20 | T0mW | breaking the meat of the code apart into tokens is easier than comment parsing |
| 21:10.12 | T0mW | split/(\s*)?[a-zAZ]+(\s)+//2 |
| 21:12.48 | prpplague | T0mW: is there a way to permently group a set of symbols in a schematic? |
| 21:15.47 | *** join/#edev dfarnsworth (i=dfarnswo@conference/ols/session) |
| 21:15.54 | T0mW | prpplague: no |
| 21:16.08 | prpplague | bummer |
| 21:16.33 | T0mW | prpplague: you can use "group" to mark off a group, then move / delete enmass |
| 21:16.45 | T0mW | prpplague: you can use "group" to mark off a block, then move / delete enmass |
| 21:21.36 | prpplague | T0mW: yea, i know about that, just didn't know if i could group it permanenty |
| 21:23.13 | *** join/#edev J4k3 (i=jsuter@dhcp-12-197-128-60.intrastar.net) |
| 21:23.30 | prpplague | J4k3: hey bud |
| 21:23.48 | prpplague | J4k3: could you do us a favor and change your quit message |
| 21:36.00 | prpplague | T0mW: crap something is screwed up with my buss |
| 22:26.02 | *** join/#edev CP|OLS (n=nobody@67.70.253.242) |
| 22:44.48 | prpplague | T0mW: normal trace size is 10mil for places like pcbexpress? |
| 22:50.58 | T0mW | prpplague: 7mil is standard nowdays |
| 22:51.34 | T0mW | prpplague: I design with 8mil min trackwidth, 8mil spacing |
| 23:08.28 | prpplague | T0mW: ahh |
| 23:08.59 | prpplague | T0mW: 8mil spacing meaning the minium space between traces? |
| 23:12.56 | prpplague | T0mW: and your vias? |
| 23:13.25 | T0mW | 16 drill |
| 23:13.47 | prpplague | hmm 16 isn't listed, hmm |
| 23:14.14 | prpplague | T0mW: just enter the value of 16? |
| 23:14.52 | prpplague | T0mW: i see a diameter of 16, |
| 23:15.02 | prpplague | T0mW: but drill doesn't show a 16 |
