wanted
Then
I wouldn't fight it. Our coutry needs young technicians to understand to read schematic.
But the same schematic with grayed out areas for two or more versions? I wouldn't do that.
wanted
Then
I wouldn't fight it. Our coutry needs young technicians to understand to read schematic.
But the same schematic with grayed out areas for two or more versions? I wouldn't do that.
your
you're
etc.,
faster
they're
Not really. There is always a time when you don't have computer access. for example when we had a main HV line arc over in WA state and power went for 23hrs. We could plug along. Although, after 2-3 hours the air in the building became so stale that we moved to my hotel room. Also no power, of course, but it had a fireplace and a sliding door that could be opened.
All you have to do is spool of the print job of a single page to a paused printer, and you will see that the print job's datagram size is huge on pdfs.
Not all Windows apps follow that page construction format. Nor do they need to.
Nope. Printers receive a finished page that gets formatted by the driver to contain the page start headers and page finish footer. That datagram gets assembled at the computer for a pdf. There are not very many that do post script any more, and even adobe does not default the pdf compiled page to post script.
I'd say that most any print job that is not using fonts at the printer, are passing completed pages to the printer whether it is a graphic or uses drawing functions. The driver is the only place where one sees true WYSIWYG previews. That is why CAD apps have the print drivers integrated so deeply into their print function application section. Also, finished pages sent to the print yields more ppm from the printer than when the print engine has to process the data sent to it further to achieve the finished datagram it feeds the drum with. I think drivers lean toward compiled, finished pages as opposed to a block of data that has to be further processed. Not all printers have huge memory sticks incorporated into them.
That's not what you said. You said "A pdf is a full bit map. Every pixel is defined and stored", which is not true.
similar
wanted
Then
The problem is that there is no way to assure the schematics stay in sync with each other. Everything is a manual and tedious process, thus prone to error. I don't like adding error prone processes into the flow.
Oh-oh, that's sound like there isn't a proper ECO process in place. Maybe that is where some fint-tuning needs to be done first ;-)
whens.
Once we formally release a letter rev of a schematic, we don't change it. The actual parts values and used/unused status is determined by a BOM (parts list) and any applicable ECOs. We can have multiple dash-number versions of a basic assembly, and fixes or customer specials can be ECOs of standard dash-number versions.
We know the history and status of every board, by serial number.
John
whens.
That's how it ought to be. Now you can calmly lean back and sip a coffee even when an auditor waltzes in out of the blue.
I try to work that way even as a consultant but of course I am not (officially ...) allowed to write ECOs. In my case I also keep a design history because in some markets that can be asked for in an audit.
whens.
Maybe you're not reading what I write (or I'm not writing what I mean). ;-)
The ECO process is fine. We can build the widgets just fine. The boss wants schematics to match the different products, built from the same boards (actually two different revisions, but that is an unrelated ECO process problem). The schematic reflects the board (max population). Each of the three products is a make from, off that schematic, with a different BOM at the higher level. Since the schematic reflects the max-populated board, which doesn't exist, it's "too confusing" for service.
Again, it's not an ECO problem. It is a documentation "problem", since there isn't a schematic that matches the product BOMs. To generate those schematics would be a labor intensive and error prone project.
on
that
your
you're
hierarchy.
translation
etc.,
small
otherwise
tech
faster
R265
they're
If we have no power, we have no lights or soldering irons either.
If you boss decides your guys really do need those three separate schematics, you can point out to him that upgrading to Capture CIS (that supports variant views and BOMs directly) is quickly cheaper than the labor to do all this manually...
We have one seat of CIS. The layout guy is the only one who has the license, so maybe I'll point that out to the boss. ;-) No idea why he has it. Before my time.
on
that
your
you're
hierarchy.
translation
etc.,
small
otherwise
tech
faster
R265
they're
This was in the northern part of WA state. Most folks lived in the boonies, the outdoors types, quite well prepared. Inverters, generators,
12V irons, several Weber barbies, propane fridges, beer, you name it, they've got it. No matter whether there is power or not :-)
whens.
Proper documentation would be a requirement for me to sign on the dotted line of an ECO. Drove some folks crazy, but ...
If the schematic is clearly marked, for example with dashed lines around certain areas and some text like "not installed on XYZ version", then it's ok. Else there has to be a matching schematic even if that means more work.
how
app is=20
("rip")=20
end"=20
Any printer that can take PostScript or HP-PCL input directly does not require the computer to do any graphics primitives.
up
I think not. In Linux there are other tools at least as good, and neither one works in wine.
--=20 Transmitted with recycled bits. Damnly my frank, I don't give a dear
----------
on
that
your
you're
AFAIK
hierarchy.
translation
etc.,
small
otherwise
tech
faster
R265
they're
Laptop w/12V auto/air brick.
It seems popular to denigrate Adobe. However I have no problems with it other than later version are overloaded with "features", and thus, slow.
v4 and v5 serve me exquisitely, v7 I use to view recently-created stuff.
And no crashes... that's only a Joerg domain problem... but you have to give him some slack... he still has trouble figuring out how to receive TV ;-)
...Jim Thompson
Not so. Was on the phone with a client last Friday. Sent me a PDF, loaded it ... ka-crumble. Told the client engineer I'd have to put the phone down for a sec to do the CTRL-ALT-DEL and he said "Do you use Acrobat? Happens here all the time". Their for-pay stuff may be better but with this kind of reliability track record I'm not going to.
As for TV I am also in good company. Some people are outright livid about it. So far so that channel 40 now felt compelled to air ads from their own tech director saying "Please have patience, we will adjust DTV to full power on August-14". Except that they don't seem to understand that signal strength is not the problem, not at all. The selected modulation scheme seems to suck.
Do OTA digital stations have a choice of modulation scheme?
I've noticed a decided improvement since OTA digital. I used to have some bleed-thru from OTA into my cable, causing "ghost" images... some runs exceed 80' from my distribution amplifier. But that's now completely gone, because they're now UHF.
...Jim Thompson
Have something to add? Share your thoughts — no account required.
Ask the community — no account required