UK diy (uk.d-i-y) For the discussion of all topics related to diy (do-it-yourself) in the UK. All levels of experience and proficency are welcome to join in to ask questions or offer solutions.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #41   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 39,563
Default Drawing a circuit diagram

NT wrote:
On Oct 15, 3:39 pm, robgraham wrote:
I've wired up a friend's garage and I would like to leave him a
straightforward drawing of how it was done so that he has a record for
any changes.

What would be the simplest PC package to do this on ?

Rob



What no-ones mentioned yet is that whatever format its in needs to be
usable in 50 years time. Probably almost none of today's data formats
will be in use then, or will have been for a couple of decades.

The one with the best chance of staying in use is plain text, .txt.
And simple circuits in ascii are easy to do. But personally I'd be
sure to print a copy too. Perhaps even stick it somewhere
permanentishly in the garage.


DXF format is virtually ASCII for vectors.
PLT format is even cruder for line drawings.
EPS is similar, and has bitmap capabilities. All of these are yonks old
and still going strong.



NT

  #42   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 39,563
Default Drawing a circuit diagram

Bill Wright wrote:
"Dave Plowman (News)" wrote in message
...
In article ,
Bill Wright wrote:
Oh - Coral Draw costs the thick end of 400 quid.

Does it buggery. You can get Corel 4 for almost nothing, and it's fine. No
need to get a later version because by the time 4 came out all the basics
were sorted.What came after was mostly luxuries.


And pirate 8,10,12 and 14 are readily available.
As are old copies of 8 upwards on Ebay.

Heh heh - reminds me of making up some logos using a very basic DTP
package. Nothing like improvising.


People sometimes send me photographs embedded in a Word doc, because 'I
don't know how to send pictures but I know how to put them into a Word
document and I know how to send them.' It beats me. If they can send .docs
why can't they send .jpgs?

Becaue the workplace sent them on a word course, but not on an outlook
express course.


This friend I have down south has just bought a new camera and she keeps
sending me examples of her photographic brilliance. Trouble is the camera
has massive resolution and the pics (which have no artistic or other value
and are mostly out of focus and/or have camera shake) are 4.5MB, and she
sends five at a time. Most of them are of her bloody cats as well.


wait till she gets a video.

Bill


  #44   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 2,580
Default Drawing a circuit diagram

"Mike Barnes" wrote in message
...
In uk.d-i-y, Clive George wrote:
"Bill Wright" wrote in message
. ..

People sometimes send me photographs embedded in a Word doc, because 'I
don't know how to send pictures but I know how to put them into a Word
document and I know how to send them.' It beats me. If they can send
.docs
why can't they send .jpgs?


For screenshots, embedded into a word doc works quite well if you're not
competent enough to generate a png. Word compresses them enough to make
them
not painful, and people can cope with "prt sc, then paste into a new word
document" if you want eg a picture of an error screen.


That must be some version of Word than I've never used. IME Word
*expands* images (as if jpg - bmp), and in the most recent version I've
used (2002) the tools that are supposed to compress them are well-hidden
and non-functional.


Word 2003, and I think the previous version too. Screenshot pasted in
without doing anything clever - 236,700 bytes in PNG, 254,976 in .doc.


  #45   Report Post  
Posted to uk.d-i-y
Rod Rod is offline
external usenet poster
 
Posts: 2,892
Default Drawing a circuit diagram

Clive George wrote:


Word 2003, and I think the previous version too. Screenshot pasted in
without doing anything clever - 236,700 bytes in PNG, 254,976 in .doc.


Memory may be faulty, but IIRC Word uses PNG as the internal format of
bitmaps. Even when Word would not actually accept PNGs themselves. So an
embedded PNG tends to have its size reflected in the total document size
but a BMP if often compressed to some extent.

Also, nasty problem was always getting images out of Word. Copy and
paste produced some bizarre effects. Then I read of the idea of saving
the Word document as HTML - and all the images end up in the underlying
folder.

--
Rod


  #46   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 3,565
Default Drawing a circuit diagram

On Oct 17, 9:21*am, The Natural Philosopher
wrote:
NT wrote:
On Oct 15, 3:39 pm, robgraham wrote:
I've wired up a friend's garage *and I would like to leave him a
straightforward drawing of how it was done so that he has a record for
any changes.


What would be the simplest PC package to do this on ?


Rob


What no-ones mentioned yet is that whatever format its in needs to be
usable in 50 years time. Probably almost none of today's data formats
will be in use then, or will have been for a couple of decades.


The one with the best chance of staying in use is plain text, .txt.
And simple circuits in ascii are easy to do. But personally I'd be
sure to print a copy too. Perhaps even stick it somewhere
permanentishly in the garage.


DXF format is virtually ASCII for vectors.
PLT format is even cruder for line drawings.
EPS is similar, and has bitmap capabilities. All of these are yonks old
and still going strong.

NT


Did any of them exist in the 1950s? AFAIK the only format in use today
that existed then is .txt. Maybe you haven't fully taken in how much
computers will change over the life of the garage, which will be a
good double that long.


NT
  #47   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 39,563
Default Drawing a circuit diagram

NT wrote:
On Oct 17, 9:21 am, The Natural Philosopher
wrote:
NT wrote:
On Oct 15, 3:39 pm, robgraham wrote:
I've wired up a friend's garage and I would like to leave him a
straightforward drawing of how it was done so that he has a record for
any changes.
What would be the simplest PC package to do this on ?
Rob
What no-ones mentioned yet is that whatever format its in needs to be
usable in 50 years time. Probably almost none of today's data formats
will be in use then, or will have been for a couple of decades.
The one with the best chance of staying in use is plain text, .txt.
And simple circuits in ascii are easy to do. But personally I'd be
sure to print a copy too. Perhaps even stick it somewhere
permanentishly in the garage.

DXF format is virtually ASCII for vectors.
PLT format is even cruder for line drawings.
EPS is similar, and has bitmap capabilities. All of these are yonks old
and still going strong.

NT


Did any of them exist in the 1950s? AFAIK the only format in use today
that existed then is .txt. Maybe you haven't fully taken in how much
computers will change over the life of the garage, which will be a
good double that long.



I don't think paper and ink existed 2000 years ago actually.

There are more documents being scanned into computers than there are
computer documents being archived onto papyrus.

Who amongst ye can still read an 8" floppy disk, txt or otherwise? By
the way .txt is a pure micro computer invention AFAICR. Text files on
other systems - ASCII text that is - had no extension, any extension you
care to mention, or any other combination

The density of information in a circuity digram cannot be conveyed in
ASCII anyway. a circuit diagram is NOT a load of letters, its is a DRAWING.

And, I can assure you, we used all the things at our disposal, dashed,
dotted, angled and variable thickness lines, to make them more easily
comprehensible.

DXF IS ascii, but ascii used to describe vectors, not alphabeticised words


Here, this is a bit of vettor graphics. You might be amused to see what
it says.

0
SECTION
2
HEADER
9
$ACADVER
1
AC1015
9
$ACADMAINTVER
70
6
9
$DWGCODEPAGE
3
ANSI_1252
9
$INSBASE
10
0.0
20
0.0
30
0.0
9
$EXTMIN
10
-315.1882
20
-34.3514
30
0.0
9
$EXTMAX
10
72.58
20
125.5146
30
0.0
9
$LIMMIN
10
0.0
20
0.0
9
$LIMMAX
10
12.0
20
9.0
9
$ORTHOMODE
70
0
9
$REGENMODE
70
1
9
$FILLMODE
70
1
9
$QTEXTMODE
70
0
9
$MIRRTEXT
70
1
9
$LTSCALE
40
1.0
9
$ATTMODE
70
1
9
$TEXTSIZE
40
0.2
9
$TRACEWID
40
0.05
9
$TEXTSTYLE
7
Standard
9
$CLAYER
8
0
9
$CELTYPE
6
ByLayer
9
$CECOLOR
62
256
9
$CELTSCALE
40
1.0
9
$DISPSILH
70
0
9
$DIMSCALE
40
1.0
9
$DIMASZ
40
0.18
9
$DIMEXO
40
0.0625
9
$DIMDLI
40
0.38
9
$DIMRND
40
0.0
9
$DIMDLE
40
0.0
9
$DIMEXE
40
0.18
9
$DIMTP
40
0.0
9
$DIMTM
40
0.0
9
$DIMTXT
40
0.18
9
$DIMCEN
40
0.09
9
$DIMTSZ
40
0.0
9
$DIMTOL
70
0
9
$DIMLIM
70
0
9
$DIMTIH
70
1
9
$DIMTOH
70
1
9
$DIMSE1
70
0
9
$DIMSE2
70
0
9
$DIMTAD
70
0
9
$DIMZIN
70
0
9
$DIMBLK
1

9
$DIMASO
70
1
9
$DIMSHO
70
1
9
$DIMPOST
1

9
$DIMAPOST
1

9
$DIMALT
70
0
9
$DIMALTD
70
2
9
$DIMALTF
40
25.4
9
$DIMLFAC
40
1.0
9
$DIMTOFL
70
0
9
$DIMTVP
40
0.0
9
$DIMTIX
70
0
9
$DIMSOXD
70
0
9
$DIMSAH
70
0
9
$DIMBLK1
1

9
$DIMBLK2
1

9
$DIMSTYLE
2
Standard
9
$DIMCLRD
70
0
9
$DIMCLRE
70
0
9
$DIMCLRT
70
0
9
$DIMTFAC
40
1.0
9
$DIMGAP
40
0.09
9
$DIMJUST
70
0
9
$DIMSD1
70
0
9
$DIMSD2
70
0
9
$DIMTOLJ
70
1
9
$DIMTZIN
70
0
9
$DIMALTZ
70
0
9
$DIMALTTZ
70
0
9
$DIMUPT
70
0
9
$DIMDEC
70
4
9
$DIMTDEC
70
4
9
$DIMALTU
70
2
9
$DIMALTTD
70
2
9
$DIMTXSTY
7
Standard
9
$DIMAUNIT
70
0
9
$DIMADEC
70
0
9
$DIMALTRND
40
0.0
9
$DIMAZIN
70
0
9
$DIMDSEP
70
46
9
$DIMATFIT
70
3
9
$DIMFRAC
70
0
9
$DIMLDRBLK
1

9
$DIMLUNIT
70
2
9
$DIMLWD
70
-2
9
$DIMLWE
70
-2
9
$DIMTMOVE
70
0
9
$LUNITS
70
2
9
$LUPREC
70
4
9
$SKETCHINC
40
0.1
9
$FILLETRAD
40
0.5
9
$AUNITS
70
0
9
$AUPREC
70
0
9
$MENU
1
..
9
$ELEVATION
40
0.0
9
$PELEVATION
40
0.0
9
$THICKNESS
40
0.0
9
$LIMCHECK
70
0
9
$CHAMFERA
40
0.5
9
$CHAMFERB
40
0.5
9
$CHAMFERC
40
1.0
9
$CHAMFERD
40
0.0
9
$SKPOLY
70
0
9
$TDCREATE
40
2455123.416881875
9
$TDUCREATE
40
2455123.375215208
9
$TDUPDATE
40
2455123.416881887
9
$TDUUPDATE
40
2455123.37521522
9
$TDINDWG
40
0.0000000116
9
$TDUSRTIMER
40
0.0000000116
9
$USRTIMER
70
1
9
$ANGBASE
50
0.0
9
$ANGDIR
70
0
9
$PDMODE
70
0
9
$PDSIZE
40
0.0
9
$PLINEWID
40
0.0
9
$SPLFRAME
70
0
9
$SPLINETYPE
70
6
9
$SPLINESEGS
70
8
9
$HANDSEED
5
77
9
$SURFTAB1
70
6
9
$SURFTAB2
70
6
9
$SURFTYPE
70
6
9
$SURFU
70
6
9
$SURFV
70
6
9
$UCSBASE
2

9
$UCSNAME
2

9
$UCSORG
10
0.0
20
0.0
30
0.0
9
$UCSXDIR
10
1.0
20
0.0
30
0.0
9
$UCSYDIR
10
0.0
20
1.0
30
0.0
9
$UCSORTHOREF
2

9
$UCSORTHOVIEW
70
0
9
$UCSORGTOP
10
0.0
20
0.0
30
0.0
9
$UCSORGBOTTOM
10
0.0
20
0.0
30
0.0
9
$UCSORGLEFT
10
0.0
20
0.0
30
0.0
9
$UCSORGRIGHT
10
0.0
20
0.0
30
0.0
9
$UCSORGFRONT
10
0.0
20
0.0
30
0.0
9
$UCSORGBACK
10
0.0
20
0.0
30
0.0
9
$PUCSBASE
2

9
$PUCSNAME
2

9
$PUCSORG
10
0.0
20
0.0
30
0.0
9
$PUCSXDIR
10
1.0
20
0.0
30
0.0
9
$PUCSYDIR
10
0.0
20
1.0
30
0.0
9
$PUCSORTHOREF
2

9
$PUCSORTHOVIEW
70
0
9
$PUCSORGTOP
10
0.0
20
0.0
30
0.0
9
$PUCSORGBOTTOM
10
0.0
20
0.0
30
0.0
9
$PUCSORGLEFT
10
0.0
20
0.0
30
0.0
9
$PUCSORGRIGHT
10
0.0
20
0.0
30
0.0
9
$PUCSORGFRONT
10
0.0
20
0.0
30
0.0
9
$PUCSORGBACK
10
0.0
20
0.0
30
0.0
9
$USERI1
70
0
9
$USERI2
70
0
9
$USERI3
70
0
9
$USERI4
70
0
9
$USERI5
70
0
9
$USERR1
40
0.0
9
$USERR2
40
0.0
9
$USERR3
40
0.0
9
$USERR4
40
0.0
9
$USERR5
40
0.0
9
$WORLDVIEW
70
1
9
$SHADEDGE
70
3
9
$SHADEDIF
70
70
9
$TILEMODE
70
1
9
$MAXACTVP
70
64
9
$PINSBASE
10
0.0
20
0.0
30
0.0
9
$PLIMCHECK
70
0
9
$PEXTMIN
10
1.000000000000000E+20
20
1.000000000000000E+20
30
1.000000000000000E+20
9
$PEXTMAX
10
-1.000000000000000E+20
20
-1.000000000000000E+20
30
-1.000000000000000E+20
9
$PLIMMIN
10
0.0
20
0.0
9
$PLIMMAX
10
12.0
20
9.0
9
$UNITMODE
70
0
9
$VISRETAIN
70
1
9
$PLINEGEN
70
0
9
$PSLTSCALE
70
1
9
$TREEDEPTH
70
3020
9
$CMLSTYLE
2
Standard
9
$CMLJUST
70
0
9
$CMLSCALE
40
1.0
9
$PROXYGRAPHICS
70
1
9
$MEASUREMENT
70
0
9
$CELWEIGHT
370
-1
9
$ENDCAPS
280
0
9
$JOINSTYLE
280
0
9
$LWDISPLAY
290
0
9
$INSUNITS
70
4
9
$HYPERLINKBASE
1

9
$STYLESHEET
1

9
$XEDIT
290
1
9
$CEPSNTYPE
380
0
9
$PSTYLEMODE
290
1
9
$FINGERPRINTGUID
2
{75FED100-D318-4940-A29C-8C3ED4DAFC40}
9
$VERSIONGUID
2
{FAEB1C32-E019-11D5-929B-00C0DF256EC4}
9
$EXTNAMES
290
1
9
$PSVPSCALE
40
0.0
9
$OLESTARTUP
290
0
0
ENDSEC
0
SECTION
2
CLASSES
0
CLASS
1
ACDBDICTIONARYWDFLT
2
AcDbDictionaryWithDefault
3
ObjectDBX Classes
90
0
280
0
281
0
0
CLASS
1
VISUALSTYLE
2
AcDbVisualStyle
3
ObjectDBX Classes
90
4095
280
0
281
0
0
CLASS
1
SCALE
2
AcDbScale
3
ObjectDBX Classes
90
1153
280
0
281
0
0
CLASS
1
DICTIONARYVAR
2
AcDbDictionaryVar
3
ObjectDBX Classes
90
0
280
0
281
0
0
CLASS
1
ACDBPLACEHOLDER
2
AcDbPlaceHolder
3
ObjectDBX Classes
90
0
280
0
281
0
0
CLASS
1
LAYOUT
2
AcDbLayout
3
ObjectDBX Classes
90
0
280
0
281
0
0
ENDSEC
0
SECTION
2
TABLES
0
TABLE
2
VPORT
5
8
330
0
100
AcDbSymbolTable
70
1
0
VPORT
5
29
330
8
100
AcDbSymbolTableRecord
100
AcDbViewportTableRecord
2
*Active
70
0
10
0.0
20
0.0
11
1.0
21
1.0
12
10.42990654205607
22
4.5
13
0.0
23
0.0
14
0.5
24
0.5
15
0.5
25
0.5
16
0.0
26
0.0
36
1.0
17
0.0
27
0.0
37
0.0
40
9.0
41
1.972972972850329
42
50.0
43
0.0
44
0.0
50
0.0
51
0.0
71
0
72
100
73
1
74
3
75
0
76
0
77
0
78
0
281
0
65
1
110
0.0
120
0.0
130
0.0
111
1.0
121
0.0
131
0.0
112
0.0
122
1.0
132
0.0
79
0
146
0.0
0
ENDTAB
0
TABLE
2
LTYPE
5
5
330
0
100
AcDbSymbolTable
70
1
0
LTYPE
5
14
330
5
100
AcDbSymbolTableRecord
100
AcDbLinetypeTableRecord
2
ByBlock
70
0
3

72
65
73
0
40
0.0
0
LTYPE
5
15
330
5
100
AcDbSymbolTableRecord
100
AcDbLinetypeTableRecord
2
ByLayer
70
0
3

72
65
73
0
40
0.0
0
LTYPE
5
16
330
5
100
AcDbSymbolTableRecord
100
AcDbLinetypeTableRecord
2
Continuous
70
0
3
Solid line
72
65
73
0
40
0.0
0
ENDTAB
0
TABLE
2
LAYER
5
2
330
0
100
AcDbSymbolTable
70
2
0
LAYER
5
10
330
2
100
AcDbSymbolTableRecord
100
AcDbLayerTableRecord
2
0
70
0
62
7
6
Continuous
370
-3
390
F
0
LAYER
5
5E
330
2
100
AcDbSymbolTableRecord
100
AcDbLayerTableRecord
2
Layer 1
70
0
62
7
6
Continuous
370
-3
390
F
0
ENDTAB
0
TABLE
2
STYLE
5
3
330
0
100
AcDbSymbolTable
70
1
0
STYLE
5
11
330
3
100
AcDbSymbolTableRecord
100
AcDbTextStyleTableRecord
2
Standard
70
0
40
0.0
41
1.0
50
0.0
71
0
42
0.2
3
txt
4

0
ENDTAB
0
TABLE
2
VIEW
5
6
330
0
100
AcDbSymbolTable
70
0
0
ENDTAB
0
TABLE
2
UCS
5
7
330
0
100
AcDbSymbolTable
70
0
0
ENDTAB
0
TABLE
2
APPID
5
9
330
0
100
AcDbSymbolTable
70
2
0
APPID
5
12
330
9
100
AcDbSymbolTableRecord
100
AcDbRegAppTableRecord
2
ACAD
70
0
0
APPID
5
5D
330
9
100
AcDbSymbolTableRecord
100
AcDbRegAppTableRecord
2
ODA
70
0
0
ENDTAB
0
TABLE
2
DIMSTYLE
5
A
330
0
100
AcDbSymbolTable
70
1
100
AcDbDimStyleTable
0
DIMSTYLE
105
27
330
A
100
AcDbSymbolTableRecord
100
AcDbDimStyleTableRecord
2
Standard
70
0
340
11
0
ENDTAB
0
TABLE
2
BLOCK_RECORD
5
1
330
0
100
AcDbSymbolTable
70
1
0
BLOCK_RECORD
5
1F
330
1
100
AcDbSymbolTableRecord
100
AcDbBlockTableRecord
2
*Model_Space
340
22
0
BLOCK_RECORD
5
1B
330
1
100
AcDbSymbolTableRecord
100
AcDbBlockTableRecord
2
*Paper_Space
340
1E
0
BLOCK_RECORD
5
23
330
1
100
AcDbSymbolTableRecord
100
AcDbBlockTableRecord
2
*Paper_Space0
340
26
0
ENDTAB
0
ENDSEC
0
SECTION
2
BLOCKS
0
BLOCK
5
20
330
1F
100
AcDbEntity
8
0
100
AcDbBlockBegin
2
*Model_Space
70
0
10
0.0
20
0.0
30
0.0
3
*Model_Space
1

0
ENDBLK
5
21
330
1F
100
AcDbEntity
8
0
100
AcDbBlockEnd
0
BLOCK
5
1C
330
1B
100
AcDbEntity
67
1
8
0
100
AcDbBlockBegin
2
*Paper_Space
70
0
10
0.0
20
0.0
30
0.0
3
*Paper_Space
1

0
ENDBLK
5
1D
330
1B
100
AcDbEntity
67
1
8
0
100
AcDbBlockEnd
0
BLOCK
5
24
330
23
100
AcDbEntity
8
0
100
AcDbBlockBegin
2
*Paper_Space0
70
0
10
0.0
20
0.0
30
0.0
3
*Paper_Space0
1

0
ENDBLK
5
25
330
23
100
AcDbEntity
8
0
100
AcDbBlockEnd
0
ENDSEC
0
SECTION
2
ENTITIES
0
SPLINE
5
5F
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
8
71
3
72
16
73
12
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
0.3333333333333333
40
0.3333333333333333
40
0.3333333333333333
40
0.3333333333333333
40
0.6666666666666666
40
0.6666666666666666
40
0.6666666666666666
40
0.6666666666666666
40
1.0
40
1.0
40
1.0
40
1.0
10
-309.824
20
72.512
30
0.0
10
-309.824
20
72.512
30
0.0
10
-309.824
20
123.9465
30
0.0
10
-309.824
20
123.9465
30
0.0
10
-309.824
20
123.9465
30
0.0
10
-309.824
20
123.9465
30
0.0
10
-277.6708
20
68.2556
30
0.0
10
-277.6708
20
68.2556
30
0.0
10
-277.6708
20
68.2556
30
0.0
10
-277.6708
20
68.2556
30
0.0
10
-277.6708
20
123.9701
30
0.0
10
-277.6708
20
123.9701
30
0.0
0
SPLINE
5
60
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
8
71
3
72
16
73
12
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
0.3333333333333333
40
0.3333333333333333
40
0.3333333333333333
40
0.3333333333333333
40
0.6666666666666666
40
0.6666666666666666
40
0.6666666666666666
40
0.6666666666666666
40
1.0
40
1.0
40
1.0
40
1.0
10
-179.576
20
-24.0048
30
0.0
10
-179.576
20
-24.0048
30
0.0
10
-179.576
20
27.4297
30
0.0
10
-179.576
20
27.4297
30
0.0
10
-179.576
20
27.4297
30
0.0
10
-179.576
20
27.4297
30
0.0
10
-147.4228
20
-28.2612
30
0.0
10
-147.4228
20
-28.2612
30
0.0
10
-147.4228
20
-28.2612
30
0.0
10
-147.4228
20
-28.2612
30
0.0
10
-147.4228
20
27.4533
30
0.0
10
-147.4228
20
27.4533
30
0.0
0
SPLINE
5
61
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-266.3168
20
124.5888
30
0.0
10
-266.3168
20
124.5888
30
0.0
10
-210.8813
20
124.5888
30
0.0
10
-210.8813
20
124.5888
30
0.0
0
SPLINE
5
62
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-237.9712
20
123.9296
30
0.0
10
-237.9712
20
123.9296
30
0.0
10
-237.9712
20
67.2384
30
0.0
10
-237.9712
20
67.2384
30
0.0
0
SPLINE
5
63
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-158.208
20
121.2928
30
0.0
10
-158.208
20
121.2928
30
0.0
10
-158.208
20
63.9272
30
0.0
10
-158.208
20
63.9272
30
0.0
0
SPLINE
5
64
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
8
71
3
72
12
73
8
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
0.5
40
0.5
40
0.5
40
0.5
40
1.0
40
1.0
40
1.0
40
1.0
10
-121.952
20
64.6016
30
0.0
10
-92.9472
20
61.0858
30
0.0
10
-87.0145
20
91.1892
30
0.0
10
-120.6336
20
94.9248
30
0.0
10
-120.6336
20
94.9248
30
0.0
10
-130.0291
20
95.9687
30
0.0
10
-139.7504
20
123.7196
30
0.0
10
-110.0864
20
123.285
30
0.0
0
SPLINE
5
65
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
8
71
3
72
12
73
8
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
0.5
40
0.5
40
0.5
40
0.5
40
1.0
40
1.0
40
1.0
40
1.0
10
-63.2832
20
65.7592
30
0.0
10
-63.2832
20
65.7592
30
0.0
10
-41.8672
20
125.248
30
0.0
10
-41.8672
20
125.248
30
0.0
10
-41.8672
20
125.248
30
0.0
10
-41.8672
20
125.248
30
0.0
10
-14.5024
20
63.9746
30
0.0
10
-14.5024
20
63.9746
30
0.0
0
SPLINE
5
66
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-53.1701
20
93.1241
30
0.0
10
-53.1701
20
93.1241
30
0.0
10
-26.9681
20
93.1241
30
0.0
10
-26.9681
20
93.1241
30
0.0
0
SPLINE
5
67
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
8
71
3
72
12
73
8
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
0.5
40
0.5
40
0.5
40
0.5
40
1.0
40
1.0
40
1.0
40
1.0
10
-236.2672
20
-26.8024
30
0.0
10
-236.2672
20
-26.8024
30
0.0
10
-214.8512
20
32.6864
30
0.0
10
-214.8512
20
32.6864
30
0.0
10
-214.8512
20
32.6864
30
0.0
10
-214.8512
20
32.6864
30
0.0
10
-187.4864
20
-28.587
30
0.0
10
-187.4864
20
-28.587
30
0.0
0
SPLINE
5
68
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-226.1541
20
0.5625
30
0.0
10
-226.1541
20
0.5625
30
0.0
10
-199.9521
20
0.5625
30
0.0
10
-199.9521
20
0.5625
30
0.0
0
SPLINE
5
69
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
8
71
3
72
20
73
16
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
0.25
40
0.25
40
0.25
40
0.25
40
0.5
40
0.5
40
0.5
40
0.5
40
0.75
40
0.75
40
0.75
40
0.75
40
1.0
40
1.0
40
1.0
40
1.0
10
-315.0976
20
26.368
30
0.0
10
-315.0976
20
26.368
30
0.0
10
-294.0032
20
-19.776
30
0.0
10
-294.0032
20
-19.776
30
0.0
10
-294.0032
20
-19.776
30
0.0
10
-294.0032
20
-19.776
30
0.0
10
-280.8192
20
13.184
30
0.0
10
-280.8192
20
13.184
30
0.0
10
-280.8192
20
13.184
30
0.0
10
-280.8192
20
13.184
30
0.0
10
-263.68
20
-21.0944
30
0.0
10
-263.68
20
-21.0944
30
0.0
10
-263.68
20
-21.0944
30
0.0
10
-263.68
20
-21.0944
30
0.0
10
-249.1776
20
29.0048
30
0.0
10
-249.1776
20
29.0048
30
0.0
0
SPLINE
5
6A
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
8
71
3
72
12
73
8
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
0.5
40
0.5
40
0.5
40
0.5
40
1.0
40
1.0
40
1.0
40
1.0
10
-69.8752
20
26.368
30
0.0
10
-69.8752
20
26.368
30
0.0
10
-104.1536
20
-3.9552
30
0.0
10
-104.1536
20
-3.9552
30
0.0
10
-104.1536
20
-3.9552
30
0.0
10
-104.1536
20
-3.9552
30
0.0
10
-72.512
20
-27.6864
30
0.0
10
-72.512
20
-27.6864
30
0.0
0
SPLINE
5
6B
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-105.578
20
31.6695
30
0.0
10
-105.578
20
31.6695
30
0.0
10
-105.366
20
-30.3511
30
0.0
10
-105.366
20
-30.3511
30
0.0
0
SPLINE
5
6C
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-40.8704
20
29.0048
30
0.0
10
-40.8704
20
29.0048
30
0.0
10
-40.8704
20
-30.3232
30
0.0
10
-40.8704
20
-30.3232
30
0.0
0
SPLINE
5
6D
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-40.2112
20
-0.6592
30
0.0
10
-40.2112
20
-0.6592
30
0.0
10
-20.4352
20
-0.6592
30
0.0
10
-20.4352
20
-0.6592
30
0.0
0
SPLINE
5
6E
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-40.2112
20
28.3456
30
0.0
10
-40.2112
20
28.3456
30
0.0
10
-9.8594
20
28.3456
30
0.0
10
-9.8594
20
28.3456
30
0.0
0
SPLINE
5
6F
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
-41.5296
20
-30.9824
30
0.0
10
-41.5296
20
-30.9824
30
0.0
10
-7.1499
20
-30.9824
30
0.0
10
-7.1499
20
-30.9824
30
0.0
0
SPLINE
5
70
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
31.6416
20
-29.0048
30
0.0
10
31.6416
20
-29.0048
30
0.0
10
31.6416
20
30.3232
30
0.0
10
31.6416
20
30.3232
30
0.0
0
SPLINE
5
71
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
24
71
3
72
8
73
4
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
1.0
40
1.0
40
1.0
40
1.0
10
72.512
20
-34.2784
30
0.0
10
72.512
20
-34.2784
30
0.0
10
32.96
20
2.6368
30
0.0
10
32.96
20
2.6368
30
0.0
0
SPLINE
5
72
330
1F
100
AcDbEntity
8
Layer 1
62
250
370
20
100
AcDbSpline
210
0.0
220
0.0
230
1.0
70
8
71
3
72
12
73
8
74
0
42
0.0000000001
43
0.0000000001
40
0.0
40
0.0
40
0.0
40
0.0
40
0.5
40
0.5
40
0.5
40
0.5
40
1.0
40
1.0
40
1.0
40
1.0
10
32.3008
20
30.3232
30
0.0
10
45.0453
20
26.8075
30
0.0
10
69.5861
20
32.834
30
0.0
10
70.5344
20
19.776
30
0.0
10
70.5344
20
19.776
30
0.0
10
71.9213
20
0.678
30
0.0
10
45.9242
20
9.2288
30
0.0
10
33.6192
20
3.9552
30
0.0
0
ENDSEC
0
SECTION
2
OBJECTS
0
DICTIONARY
5
C
330
0
100
AcDbDictionary
281
1
3
ACAD_GROUP
350
D
3
ACAD_LAYOUT
350
1A
3
ACAD_MLEADERSTYLE
350
76
3
ACAD_MLINESTYLE
350
17
3
ACAD_PLOTSETTINGS
350
19
3
ACAD_PLOTSTYLENAME
350
E
3
ACAD_SCALELIST
350
3B
3
ACAD_TABLESTYLE
350
75
3
ACAD_VISUALSTYLE
350
2A
3
AcDbVariableDictionary
350
73
0
DICTIONARY
5
D
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
0
DICTIONARY
5
1A
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
3
Layout1
350
1E
3
Layout2
350
26
3
Model
350
22
0
DICTIONARY
5
76
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
0
DICTIONARY
5
17
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
3
Standard
350
18
0
DICTIONARY
5
19
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
0
ACDBDICTIONARYWDFLT
5
E
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
3
Normal
350
F
100
AcDbDictionaryWithDefault
340
F
0
DICTIONARY
5
3B
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
3
A0
350
3C
3
A1
350
3D
3
A2
350
3E
3
A3
350
3F
3
A4
350
40
3
A5
350
41
3
A6
350
42
3
A7
350
43
3
A8
350
44
3
A9
350
45
3
B0
350
46
3
B1
350
47
3
B2
350
48
3
B3
350
49
3
B4
350
4A
3
B5
350
4B
3
B6
350
4C
3
B7
350
4D
3
B8
350
4E
3
B9
350
4F
3
C0
350
50
3
C1
350
51
3
C2
350
52
3
C3
350
53
3
C4
350
54
3
C5
350
55
3
C6
350
56
3
C7
350
57
3
C8
350
58
3
C9
350
59
3
D0
350
5A
3
D1
350
5B
3
D2
350
5C
0
DICTIONARY
5
75
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
0
DICTIONARY
5
2A
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
3
2dWireframe
350
2F
3
3D Hidden
350
31
3
3dWireframe
350
30
3
Basic
350
32
3
Brighten
350
36
3
ColorChange
350
3A
3
Conceptual
350
34
3
Dim
350
35
3
Facepattern
350
39
3
Flat
350
2B
3
FlatWithEdges
350
2C
3
Gouraud
350
2D
3
GouraudWithEdges
350
2E
3
Linepattern
350
38
3
Realistic
350
33
3
Thicken
350
37
0
DICTIONARY
5
73
102
{ACAD_REACTORS
330
C
102
}
330
C
100
AcDbDictionary
281
1
3
CANNOSCALE
350
74
0
LAYOUT
5
1E
102
{ACAD_REACTORS
330
1A
102
}
330
1A
100
AcDbPlotSettings
1

2
none_device
4

6

40
0.0
41
0.0
42
0.0
43
0.0
44
0.0
45
0.0
46
0.0
47
0.0
48
0.0
49
0.0
140
0.0
141
0.0
142
1.0
143
1.0
70
688
72
0
73
0
74
5
7

75
16
147
1.0
148
0.0
149
0.0
100
AcDbLayout
1
Layout1
70
1
71
1
10
0.0
20
0.0
11
12.0
21
9.0
12
0.0
22
0.0
32
0.0
14
1.000000000000000E+20
24
1.000000000000000E+20
34
1.000000000000000E+20
15
-1.000000000000000E+20
25
-1.000000000000000E+20
35
-1.000000000000000E+20
146
0.0
13
0.0
23
0.0
33
0.0
16
1.0
26
0.0
36
0.0
17
0.0
27
1.0
37
0.0
76
0
330
1B
0
LAYOUT
5
26
102
{ACAD_REACTORS
330
1A
102
}
330
1A
100
AcDbPlotSettings
1

2
none_device
4

6

40
0.0
41
0.0
42
0.0
43
0.0
44
0.0
45
0.0
46
0.0
47
0.0
48
0.0
49
0.0
140
0.0
141
0.0
142
1.0
143
1.0
70
688
72
0
73
0
74
5
7

75
16
147
1.0
148
0.0
149
0.0
100
AcDbLayout
1
Layout2
70
1
71
2
10
0.0
20
0.0
11
0.0
21
0.0
12
0.0
22
0.0
32
0.0
14
0.0
24
0.0
34
0.0
15
0.0
25
0.0
35
0.0
146
0.0
13
0.0
23
0.0
33
0.0
16
1.0
26
0.0
36
0.0
17
0.0
27
1.0
37
0.0
76
0
330
23
0
LAYOUT
5
22
102
{ACAD_REACTORS
330
1A
102
}
330
1A
100
AcDbPlotSettings
1

2
none_device
4

6

40
0.0
41
0.0
42
0.0
43
0.0
44
0.0
45
0.0
46
0.0
47
0.0
48
0.0
49
0.0
140
0.0
141
0.0
142
1.0
143
1.0
70
1712
72
0
73
0
74
0
7

75
0
147
1.0
148
0.0
149
0.0
100
AcDbLayout
1
Model
70
1
71
0
10
0.0
20
0.0
11
12.0
21
9.0
12
0.0
22
0.0
32
0.0
14
-315.1882
24
-34.3514
34
0.0
15
72.58
25
125.5146
35
0.0
146
0.0
13
0.0
23
0.0
33
0.0
16
1.0
26
0.0
36
0.0
17
0.0
27
1.0
37
0.0
76
0
330
1F
331
29
0
MLINESTYLE
5
18
102
{ACAD_REACTORS
330
17
102
}
330
17
100
AcDbMlineStyle
2
Standard
70
0
3

62
256
51
90.0
52
90.0
71
2
49
0.5
62
256
6
BYLAYER
49
-0.5
62
256
6
BYLAYER
0
ACDBPLACEHOLDER
5
F
102
{ACAD_REACTORS
330
E
102
}
330
E
0
SCALE
5
3C
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:1
140
1.0
141
1.0
290
1
0
SCALE
5
3D
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:2
140
1.0
141
2.0
290
0
0
SCALE
5
3E
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:4
140
1.0
141
4.0
290
0
0
SCALE
5
3F
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:5
140
1.0
141
5.0
290
0
0
SCALE
5
40
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:8
140
1.0
141
8.0
290
0
0
SCALE
5
41
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:10
140
1.0
141
10.0
290
0
0
SCALE
5
42
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:16
140
1.0
141
16.0
290
0
0
SCALE
5
43
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:20
140
1.0
141
20.0
290
0
0
SCALE
5
44
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:30
140
1.0
141
30.0
290
0
0
SCALE
5
45
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:40
140
1.0
141
40.0
290
0
0
SCALE
5
46
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:50
140
1.0
141
50.0
290
0
0
SCALE
5
47
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1:100
140
1.0
141
100.0
290
0
0
SCALE
5
48
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
2:1
140
2.0
141
1.0
290
0
0
SCALE
5
49
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
4:1
140
4.0
141
1.0
290
0
0
SCALE
5
4A
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
8:1
140
8.0
141
1.0
290
0
0
SCALE
5
4B
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
10:1
140
10.0
141
1.0
290
0
0
SCALE
5
4C
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
100:1
140
100.0
141
1.0
290
0
0
SCALE
5
4D
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1/128" = 1'-0"
140
0.0078125
141
12.0
290
0
0
SCALE
5
4E
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1/64" = 1'-0"
140
0.015625
141
12.0
290
0
0
SCALE
5
4F
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1/32" = 1'-0"
140
0.03125
141
12.0
290
0
0
SCALE
5
50
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1/16" = 1'-0"
140
0.0625
141
12.0
290
0
0
SCALE
5
51
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
3/32" = 1'-0"
140
0.09375
141
12.0
290
0
0
SCALE
5
52
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1/8" = 1'-0"
140
0.125
141
12.0
290
0
0
SCALE
5
53
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
3/16" = 1'-0"
140
0.1875
141
12.0
290
0
0
SCALE
5
54
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1/4" = 1'-0"
140
0.25
141
12.0
290
0
0
SCALE
5
55
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
3/8" = 1'-0"
140
0.375
141
12.0
290
0
0
SCALE
5
56
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1/2" = 1'-0"
140
0.5
141
12.0
290
0
0
SCALE
5
57
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
3/4" = 1'-0"
140
0.75
141
12.0
290
0
0
SCALE
5
58
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1" = 1'-0"
140
1.0
141
12.0
290
0
0
SCALE
5
59
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1-1/2" = 1'-0"
140
1.5
141
12.0
290
0
0
SCALE
5
5A
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
3" = 1'-0"
140
3.0
141
12.0
290
0
0
SCALE
5
5B
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
6" = 1'-0"
140
6.0
141
12.0
290
0
0
SCALE
5
5C
102
{ACAD_REACTORS
330
3B
102
}
330
3B
100
AcDbScale
70
0
300
1'-0" = 1'-0"
140
12.0
141
12.0
290
0
0
VISUALSTYLE
5
2F
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
2dWireframe
70
4
71
0
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
0
66
257
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
0
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
31
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
3D Hidden
70
6
71
1
72
2
73
2
90
0
40
-0.6
41
-30.0
62
5
63
7
74
2
91
2
64
7
65
257
75
2
175
1
42
40.0
92
0
66
257
43
1.0
76
1
77
6
78
2
67
7
79
3
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
0
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
30
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
3dWireframe
70
5
71
0
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
0
66
257
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
0
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
32
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Basic
70
7
71
1
72
0
73
1
90
0
40
-0.6
41
-30.0
62
5
63
7
74
0
91
4
64
7
65
257
75
1
175
1
42
1.0
92
8
66
7
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
36
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Brighten
70
12
71
2
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
8
66
7
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
50.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
3A
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
ColorChange
70
16
71
2
72
2
73
3
90
0
40
-0.6
41
-30.0
62
5
63
8
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
8
66
8
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
34
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Conceptual
70
9
71
3
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
2
91
2
64
7
65
257
75
1
175
1
42
40.0
92
8
66
7
43
1.0
76
1
77
6
78
2
67
7
79
3
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
0
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
35
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Dim
70
11
71
2
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
8
66
7
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
-50.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
39
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Facepattern
70
15
71
2
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
8
66
7
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
2B
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Flat
70
0
71
2
72
1
73
1
90
2
40
-0.6
41
30.0
62
5
63
7
74
0
91
4
64
7
65
257
75
1
175
1
42
1.0
92
8
66
7
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
13
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
2C
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
FlatWithEdges
70
1
71
2
72
1
73
1
90
2
40
-0.6
41
30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
0
66
257
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
13
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
2D
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Gouraud
70
2
71
2
72
2
73
1
90
2
40
-0.6
41
30.0
62
5
63
7
74
0
91
4
64
7
65
257
75
1
175
1
42
1.0
92
0
66
7
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
13
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
2E
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
GouraudWithEdges
70
3
71
2
72
2
73
1
90
2
40
-0.6
41
30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
0
66
257
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
13
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
38
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Linepattern
70
14
71
2
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
7
175
7
42
1.0
92
8
66
7
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
33
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Realistic
70
8
71
2
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
1
91
0
64
7
65
257
75
1
175
1
42
1.0
92
8
66
8
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
13
44
0.0
173
0
291
0
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
VISUALSTYLE
5
37
102
{ACAD_REACTORS
330
2A
102
}
330
2A
100
AcDbVisualStyle
2
Thicken
70
13
71
2
72
2
73
0
90
0
40
-0.6
41
-30.0
62
5
63
7
74
1
91
4
64
7
65
257
75
1
175
1
42
1.0
92
12
66
7
43
1.0
76
1
77
6
78
2
67
7
79
5
170
0
171
0
290
0
174
0
93
1
44
0.0
173
0
291
1
45
0.0
1001
ACAD
1000
AcDbSavedByObjectVersion
1070
0
0
DICTIONARYVAR
5
74
102
{ACAD_REACTORS
330
73
102
}
330
73
100
DictionaryVariables
280
0
1
1:1
0
ENDSEC
0
EOF

NT

  #48   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 14,085
Default Drawing a circuit diagram

On Sun, 18 Oct 2009 10:01:44 +0100, The Natural Philosopher wrote:

Here, this is a bit of vettor graphics. You might be amused to see what
it says.

0
SECTION
2
HEADER
9
$ACADVER
1
AC1015
9
$ACADMAINTVER
70


And assuming you can extract the data from the medium on which it
stored you can, do the ASCII transaltion on each byte, print it out,
read it and plot by hand. Not so easy to do with a binary format...

--
Cheers
Dave.



  #49   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 2,397
Default Drawing a circuit diagram

NT wrote:

Did any of them exist in the 1950s? AFAIK the only format in use today
that existed then is .txt. Maybe you haven't fully taken in how much
computers will change over the life of the garage, which will be a
good double that long.


Weren't most of the computers back then IBM or similar mainframes,
running EBCDIC not ASCII?

Paint it on the garage wall.

Andy
  #50   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 4,341
Default Drawing a circuit diagram

On Sun, 18 Oct 2009 14:40:05 +0100, Andy Champ wrote:

NT wrote:

Did any of them exist in the 1950s? AFAIK the only format in use today
that existed then is .txt. Maybe you haven't fully taken in how much
computers will change over the life of the garage, which will be a
good double that long.


Weren't most of the computers back then IBM or similar mainframes,
running EBCDIC not ASCII?

Paint it on the garage wall.

Andy


Take a photograph of it on film - that lasts for a while and is easily
read.
--
Peter.
The head of a pin will hold more angels if
it's been flattened with an angel-grinder.


  #51   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 105
Default Drawing a circuit diagram

On Thu, 15 Oct 2009 07:39:14 -0700 (PDT), robgraham
wrote:

I've wired up a friend's garage and I would like to leave him a
straightforward drawing of how it was done so that he has a record for
any changes.

What would be the simplest PC package to do this on ?

Rob



MS Visio
--

blackbat /\x/\
  #52   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 3,565
Default Drawing a circuit diagram

On Oct 18, 2:40*pm, Andy Champ wrote:
NT wrote:


Did any of them exist in the 1950s? AFAIK the only format in use today
that existed then is .txt. Maybe you haven't fully taken in how much
computers will change over the life of the garage, which will be a
good double that long.


Weren't most of the computers back then IBM or similar mainframes,
running EBCDIC not ASCII?

Paint it on the garage wall.

Andy



EBCDIC is fairly well known, but even basic plain text wasnt
standardised back then. Hence the ASCII standard. But I believe ASCII
was based on existing practice rather than a new completely
incompatible standard, and that there were mainly 2 trends, ebcdic
being not the only one.

As well as IBMs with EBCDIC there were all sorts of oddities. The
soviets played with trinary logic, and decimal and hexadecimal were no
strangers to computing at the hardware level. Relay logic was also
used at the budget end, leading to probably the worlds slowest ever
computer:
http://en.wikipedia.org/wiki/WITCH_(computer)

There was even a series of very successful fluid based computers...
http://en.wikipedia.org/wiki/MONIAC_Computer

I presume EBCDIC is still readable by some piece of software somewhere


NT
  #53   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 3,565
Default Drawing a circuit diagram

On Oct 18, 10:01*am, The Natural Philosopher
wrote:

The density of information in a circuity digram cannot be conveyed in
ASCII anyway. a circuit diagram is NOT a load of letters, its is a DRAWING.


I've never found it hard to do simple circuit diagrams in ascii art.


NT
  #54   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 268
Default Drawing a circuit diagram

On Sun, 18 Oct 2009 18:07:06 -0700 (PDT), NT wrote:
On Oct 18, 2:40Â*pm, Andy Champ wrote:
NT wrote:


Did any of them exist in the 1950s? AFAIK the only format in use today
that existed then is .txt. Maybe you haven't fully taken in how much
computers will change over the life of the garage, which will be a
good double that long.


Weren't most of the computers back then IBM or similar mainframes,
running EBCDIC not ASCII?

Paint it on the garage wall.

Andy



EBCDIC is fairly well known, but even basic plain text wasnt
standardised back then. Hence the ASCII standard. But I believe ASCII
was based on existing practice rather than a new completely
incompatible standard, and that there were mainly 2 trends, ebcdic
being not the only one.


In the '50 and '60s (maybe even the '70s, too) the most widespread
electronic text format was the 5 bit Baudot code used by Telex and
teleprinter machines.
  #55   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 568
Default Drawing a circuit diagram

On Mon, 19 Oct 2009 09:19:40 GMT, pete wrote:



EBCDIC is fairly well known, but even basic plain text wasnt
standardised back then. Hence the ASCII standard. But I believe ASCII
was based on existing practice rather than a new completely
incompatible standard, and that there were mainly 2 trends, ebcdic
being not the only one.


In the '50 and '60s (maybe even the '70s, too) the most widespread
electronic text format was the 5 bit Baudot code used by Telex and
teleprinter machines.



Bzzzt,

Not sure what you mean by "Teleprinter machine". where was that used .

The American Telex system used Teletype KSR (or ASR) 33 machines which
were 7 bit (or 8 bit with parity) At one time I had a collection of
them plus Creed 3x tape printers and 7b page printer machines.

Derek



  #56   Report Post  
Posted to uk.d-i-y
Baz Baz is offline
external usenet poster
 
Posts: 280
Default Drawing a circuit diagram


"The Natural Philosopher" wrote in message
...
NT wrote:
On Oct 17, 9:21 am, The Natural Philosopher
wrote:
NT wrote:
On Oct 15, 3:39 pm, robgraham wrote:
I've wired up a friend's garage and I would like to leave him a
straightforward drawing of how it was done so that he has a record for
any changes.
What would be the simplest PC package to do this on ?
Rob
What no-ones mentioned yet is that whatever format its in needs to be
usable in 50 years time. Probably almost none of today's data formats
will be in use then, or will have been for a couple of decades.
The one with the best chance of staying in use is plain text, .txt.
And simple circuits in ascii are easy to do. But personally I'd be
sure to print a copy too. Perhaps even stick it somewhere
permanentishly in the garage.
DXF format is virtually ASCII for vectors.
PLT format is even cruder for line drawings.
EPS is similar, and has bitmap capabilities. All of these are yonks old
and still going strong.

NT


Did any of them exist in the 1950s? AFAIK the only format in use today
that existed then is .txt. Maybe you haven't fully taken in how much
computers will change over the life of the garage, which will be a
good double that long.



I don't think paper and ink existed 2000 years ago actually.

There are more documents being scanned into computers than there are
computer documents being archived onto papyrus.

Who amongst ye can still read an 8" floppy disk, txt or otherwise? By the
way .txt is a pure micro computer invention AFAICR. Text files on other
systems - ASCII text that is - had no extension, any extension you care to
mention, or any other combination

The density of information in a circuity digram cannot be conveyed in
ASCII anyway. a circuit diagram is NOT a load of letters, its is a
DRAWING.

And, I can assure you, we used all the things at our disposal, dashed,
dotted, angled and variable thickness lines, to make them more easily
comprehensible.

DXF IS ascii, but ascii used to describe vectors, not alphabeticised
words


Here, this is a bit of vettor graphics. You might be amused to see what it
says.

0
SECTION
2
HEADER
9

SNIP

Very childish!
Baz


  #57   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 268
Default Drawing a circuit diagram

On Mon, 19 Oct 2009 11:23:06 +0100, Derek Geldard wrote:
On Mon, 19 Oct 2009 09:19:40 GMT, pete wrote:



EBCDIC is fairly well known, but even basic plain text wasnt
standardised back then. Hence the ASCII standard. But I believe ASCII
was based on existing practice rather than a new completely
incompatible standard, and that there were mainly 2 trends, ebcdic
being not the only one.


In the '50 and '60s (maybe even the '70s, too) the most widespread
electronic text format was the 5 bit Baudot code used by Telex and
teleprinter machines.



Bzzzt,

Not sure what you mean by "Teleprinter machine". where was that used .

The American Telex system used Teletype KSR (or ASR) 33 machines which
were 7 bit (or 8 bit with parity) At one time I had a collection of
them plus Creed 3x tape printers and 7b page printer machines.


Yes, the Teletype Corporation machines were 7 or 8 bit, but the Creed telex
machines that I've seen (the 54.5 Baud / 80 Volt types) had a 5 bit
plus start/stop bit format. Their paper tape rummages around in loft
was 5-hole plus a sprocket.
  #58   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 3,348
Default Drawing a circuit diagram

On Mon, 19 Oct 2009 11:27:13 +0000, pete wrote:

Yes, the Teletype Corporation machines were 7 or 8 bit, but the Creed
telex machines that I've seen (the 54.5 Baud / 80 Volt types) had a 5
bit plus start/stop bit format. Their paper tape rummages around in
loft was 5-hole plus a sprocket.


I once had a job with Advance Linen (the roller towel people) in their
computer room. All depot stock levels came in on Telex 5-track tape, and
every evening we had to feed it all in.

The program was awful - it required a double check that the date on the
tape was correct. We had to enter the date, backwards, in octal, on the
operator console before each tape...

It was written a long time before by the guy who was then chief
programmer. No one dared to complain...



--
Use the BIG mirror service in the UK:
http://www.mirrorservice.org

  #59   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 1,053
Default Drawing a circuit diagram

Derek Geldard wrote:
On Mon, 19 Oct 2009 09:19:40 GMT, pete wrote:



EBCDIC is fairly well known, but even basic plain text wasnt
standardised back then. Hence the ASCII standard. But I believe ASCII
was based on existing practice rather than a new completely
incompatible standard, and that there were mainly 2 trends, ebcdic
being not the only one.


In the '50 and '60s (maybe even the '70s, too) the most widespread
electronic text format was the 5 bit Baudot code used by Telex and
teleprinter machines.



Bzzzt,

Not sure what you mean by "Teleprinter machine". where was that used .

The American Telex system used Teletype KSR (or ASR) 33 machines which
were 7 bit (or 8 bit with parity) At one time I had a collection of
them plus Creed 3x tape printers and 7b page printer machines.

Proper teleprinters as used for Telex used a 5-bit code, so unbzzzt!
They mostly ran at 50 baud too, half the speed of KSR/ASR33
teleprinters. The operators had to limit their typing to that speed
which was distinctly slower than an expert typist could manage *and*
they had to do it at a constant inter-character speed, the telex
machine wouldn't accept characters closer together, no buffering of
any sort.

I remember watching teleprinter operators using them when I worked in
far away places in the 1970s so the above is right on that front too.

Just to add another oddity I worked on DEC PDP-8 and PDP-12 machines
in the 1970s and 1980s, they used a cut down 6-bit code (a sub-set of
ASCII) to fit two characters in each of their 12-bit words.

--
Chris Green

  #60   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 1,668
Default Drawing a circuit diagram

On Mon, 19 Oct 2009 11:37:44 +0000, Bob Eager wrote:
The program was awful - it required a double check that the date on the
tape was correct. We had to enter the date, backwards, in octal, on the
operator console before each tape...


Having done the move across the Pond, I can sympathise - I don't think
I'll ever get used to writing dates backwards

On a serious note, it's funny how bad computer interfaces often used to
be. I don't mean CLI or Unix commands etc. as they make a lot of sense
(and just require some up-front learning rather than being
point-and-drool) - but outside of environments with really restricted
resources there was just no excuse for how bad some of the interfaces
were...

cheers

Jules



  #61   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 39,563
Default Drawing a circuit diagram

NT wrote:
On Oct 18, 10:01 am, The Natural Philosopher
wrote:

The density of information in a circuity digram cannot be conveyed in
ASCII anyway. a circuit diagram is NOT a load of letters, its is a DRAWING.


I've never found it hard to do simple circuit diagrams in ascii art.

My diagrams were not simple.


NT

  #62   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 1,668
Default Drawing a circuit diagram

On Sun, 18 Oct 2009 18:07:06 -0700, NT wrote:
As well as IBMs with EBCDIC there were all sorts of oddities. The
soviets played with trinary logic


Logic and machine state can impact on the program side, but I think it's
largely irrelevant to storage of data - the use of trinary doesn't mean
that the interface that the user sees has to be something completely alien.

strangers to computing at the hardware level. Relay logic was also used
at the budget end, leading to probably the worlds slowest ever computer:
http://en.wikipedia.org/wiki/WITCH_(computer)


I don't think you can really use a term such as "budget end" for anything
that old (in a computing context)... there was only very expensive and
really expensive :-)

I presume EBCDIC is still readable by some piece of software somewhere


Yeah; no problem. Off the top of my head, four ways to make data
survive long-term:

1) Make the format simple (so someone can pick them apart and figure
them out even without documentation),
2) Make the format self-documenting (e.g. such as XML, where there's a
lot of semantic context embedded),
3) Preserve the format specification (often difficult),
4) Keep refreshing the data, converting it to the most-recent standard
as time goes on.

.... of those I think the first two are really the most viable; people
don't refresh data often enough (or it falls out of sight), and similarly
data specification documents have a nasty habit of vanishing or becoming
separated from the data itself.

cheers

Jules



  #64   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 1,668
Default Drawing a circuit diagram

On Mon, 19 Oct 2009 18:36:33 +0100, Andy Champ wrote:
ICL 1900 had a 24-bit word, and used a 6 bit character set too. I bet
they were all different ones.


I think the Elliott 803 was 39 bits... but I also suspect it was
pre-dating any concept of attaching a filename to a piece of data or
program by at least a decade (not to say that there wasn't some form of
meaningful label in there, though).

Jules might like to think how hard XML would be to pick apart if he
didn't know the character set.


Can I pass? No, on a serious note it's certainly not perfect - but
it's better than nothing in some circumstances (the main issue of course
being the amount of space 'wasted' by the semantic information - which is
half the reason I loathe things like HTML-based emails!) For the purpose
of my comment I was making the assumption that it was at least in ASCII or
some flavour of double-byte charset - albeit not necessarily English for
the human-readable part.

cheers

Jules

  #65   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 3,565
Default Drawing a circuit diagram

On Oct 19, 3:04*pm, The Natural Philosopher
wrote:
NT wrote:
On Oct 18, 10:01 am, The Natural Philosopher
wrote:


The density of information in a circuity digram cannot be conveyed in
ASCII anyway. a circuit diagram is NOT a load of letters, its is a DRAWING.


I've never found it hard to do simple circuit diagrams in ascii art.


My diagrams were not simple.


I'd be very surprised if garage wiring were too complex for ascii art.
But who knows, people have isntalled stranger things.


NT


  #66   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 3,565
Default Drawing a circuit diagram

On Oct 19, 3:07*pm, Jules
wrote:
On Sun, 18 Oct 2009 18:07:06 -0700, NT wrote:


As well as IBMs with EBCDIC there were all sorts of oddities. The
soviets played with trinary logic


Logic and machine state can impact on the program side, but I think it's
largely irrelevant to storage of data - the use of trinary doesn't mean
that the interface that the user sees has to be something completely alien.

  #67   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 5,175
Default Drawing a circuit diagram

On 19 Oct, 18:36, Andy Champ wrote:

Jules might like to think how hard XML would be to pick apart if he
didn't know the character set.


Piece of cake - it's part of the design of XML to make such things
easy.

My day job consists largely of sight-reading pages of garbage and
telling that the consuitants have encoded their Bulgarian as
ISO-8859-3 when they meant to use ISO-8859-5, then not being allowed
to brand them with a red-hot clueiron that says UTF-8.

I keep a clueiron under my desk, just in case.
Along with my rubber stamps for "UTF-8" and "It's on the wiki"
  #68   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 1,668
Default Drawing a circuit diagram

On Mon, 19 Oct 2009 15:21:13 -0700, NT wrote:
I'd be very surprised if garage wiring were too complex for ascii art.
But who knows, people have isntalled stranger things.


Ours featured a big ol' knife switch and a pair of 30A time-delay
fuses in a cabinet full* of dead ladybirds - I'd have a heck of a job
doing that in ASCII

* until I opened it and the whole bloody lot cascaded into my face, anyway.



  #69   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 39,563
Default Drawing a circuit diagram

NT wrote:

1) Make the format simple (so someone can pick them apart and figure
them out even without documentation),
2) Make the format self-documenting (e.g. such as XML, where there's a
lot of semantic context embedded),
3) Preserve the format specification (often difficult),
4) Keep refreshing the data, converting it to the most-recent standard
as time goes on.

... of those I think the first two are really the most viable; people
don't refresh data often enough (or it falls out of sight), and similarly
data specification documents have a nasty habit of vanishing or becoming
separated from the data itself.

cheers

Jules



The trouble with 2&3 is that over time it often ceases to be worth
picking it apart, or finding compatible hardware to install the OS to
install the app to read the data. One of the many beauties of plain
text is that's just never an issue.


Good lord. You really dont know much about computers, do you?

What OS do you need to read your blessed ASCII then?

VMS?


NT

  #70   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 39,563
Default Drawing a circuit diagram

Jules wrote:
On Mon, 19 Oct 2009 15:21:13 -0700, NT wrote:
I'd be very surprised if garage wiring were too complex for ascii art.
But who knows, people have isntalled stranger things.


Ours featured a big ol' knife switch and a pair of 30A time-delay
fuses in a cabinet full* of dead ladybirds - I'd have a heck of a job
doing that in ASCII

* until I opened it and the whole bloody lot cascaded into my face, anyway.



Be careful not to photograph it.

Who knows whether next years Windows 7.3 will be able to read a JPEG?



  #71   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 14,085
Default Drawing a circuit diagram

On Mon, 19 Oct 2009 15:31:36 -0700 (PDT), NT wrote:

I presume EBCDIC is still readable by some piece of software

somewhere

Yeah; no problem.


Òêëó@ëó@

Certainly easy enough to code (assuming that something doesn't mangle
it...)

* 1) Make the format simple (so someone can pick them apart and

figure
* * *them out even without documentation),
* 2) Make the format self-documenting (e.g. such as XML, where

there's
a*lot of semantic context embedded),
* 3) Preserve the format specification (often difficult),
* 4) Keep refreshing the data, converting it to the most-recent
standard*as time goes on.


The trouble with 2&3 is that over time it often ceases to be worth
picking it apart, or finding compatible hardware to install the OS to
install the app to read the data.


Why on earth do you need an OS or the orginal app to read the data?
All you need is suitable hardware to extract the bit stream from the
storeage media. In the case of magnetic media that could be a bottle
of "edivu" and a microscope, with a CD/DVD/Blu_Ray just a microscope.

Once you have the bit pattern you need number 3 to decode it, the
simpler the format specification the easier that is.

One of the many beauties of plain text is that's just never an issue.


er you are forgetting that machines don't know anything about "plain
text" they just handle 0's and 1's in blocks called bytes which can
also be joined into words. The number of bits in a byte and/or the
number of bytes in a word can vary and ASCII is just *a* way of
encoding a given character to a bit pattern, using 7 bits per
character.

--
Cheers
Dave.



  #72   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 384
Default Drawing a circuit diagram

On 18 Oct, 14:40, Andy Champ wrote:
NT wrote:

Did any of them exist in the 1950s? AFAIK the only format in use today
that existed then is .txt. Maybe you haven't fully taken in how much
computers will change over the life of the garage, which will be a
good double that long.


Weren't most of the computers back then IBM or similar mainframes,
running EBCDIC not ASCII?

Paint it on the garage wall.


Engrave it into the garage wall. Possibly using an angle grinder.

--
Halmyre
  #73   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 2,040
Default Drawing a circuit diagram

Halmyre wrote:
On 18 Oct, 14:40, Andy Champ wrote:
NT wrote:

Paint it on the garage wall.


Engrave it into the garage wall. Possibly using an angle grinder.


What would have happened if we got a time machine going, and teleported
an angle grinder and everlasting atomic power pack back to the stone
age. What fantastic wall engravings we'd be looking at!

;-)

--
Adrian C
  #74   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 307
Default Drawing a circuit diagram

Adrian C wrote:

What would have happened if we got a time machine going, and teleported
an angle grinder and everlasting atomic power pack back to the stone
age. What fantastic wall engravings we'd be looking at!


That's yet to come. There's a chap down the road uses an angle grinder
and diamond discs to carve Easter Island-style heads and faces from
granite beach boulders. Wherever they end up after the next Ice Age,
they'll probably start a new religion.



--
Ian White
  #75   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 3,235
Default Drawing a circuit diagram

On Oct 19, 3:07*pm, Jules
wrote:



I presume EBCDIC is still readable by some piece of software somewhere


Yeah; no problem. Off the top of my head, four ways to make data
survive long-term:

* 1) Make the format simple (so someone can pick them apart and figure
* * *them out even without documentation),
* 2) Make the format self-documenting (e.g. such as XML, where there's a
* * *lot of semantic context embedded),


Irrelevant if you can't decode the ASCII, EBCDIC, or whatever the XML
is stored in, or read the data from the media it is stored on.

MBQ



  #76   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 3,235
Default Drawing a circuit diagram

On Oct 19, 11:31*pm, NT wrote:

The trouble with 2&3 is that over time it often ceases to be worth
picking it apart, or finding compatible hardware to install the OS to
install the app to read the data. One of the many beauties of plain
text is that's just never an issue.


How do you propose to handle plain text without an "app" to render it
into human readable form? What "OS" do you use for that "app"?

Plain text is just one special case of (almost invariably) binary
data.

MBQ
  #77   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 2,988
Default Drawing a circuit diagram

On Tue, 20 Oct 2009 03:20:30 -0700 (PDT), Owain
had this to say:

On 20 Oct, 11:00, Adrian C wrote:
What would have happened if we got a time machine going, and teleported
an angle grinder and everlasting atomic power pack back to the stone
age. What fantastic wall engravings we'd be looking at!


"I've been over to Stonehenge and Ælfric the mason says he's got a
nice chunk of Ordovician dolerite you can turn into fireplaces, going
cheap but you've to cut it up yourself. The whole site's going to be
cleared for some executive mud-huts apparently so see if there's
anything else you can scrounge while you're up there"


Like stone pots of WD-40?

Or car body filler...

--
Frank Erskine
  #78   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 299
Default Drawing a circuit diagram


"robgraham" wrote in message
...
I've wired up a friend's garage and I would like to leave him a
straightforward drawing of how it was done so that he has a record for
any changes.

What would be the simplest PC package to do this on ?

Rob



Visio ... no learning curve, drop, drag, draw ... and thousands of free
templates to use.

  #79   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 299
Default Drawing a circuit diagram


"Mike Barnes" wrote in message
...
In uk.d-i-y, Bill Wright wrote:
This friend I have down south has just bought a new camera and she keeps
sending me examples of her photographic brilliance. Trouble is the camera
has massive resolution and the pics (which have no artistic or other value
and are mostly out of focus and/or have camera shake) are 4.5MB, and she
sends five at a time. Most of them are of her bloody cats as well.


Persuade her to upload them to the web and mail you a link. I think
automatic thumbnail creation is a feature of some sites, so you would
know what was on the pics, and you could download them (or not) as
desired.



yep ... give here a link to Humyo, esnips or Photbucket ... then it's only
links of her out of focus cats

  #80   Report Post  
Posted to uk.d-i-y
external usenet poster
 
Posts: 1,668
Default Drawing a circuit diagram

On Tue, 20 Oct 2009 08:51:37 +0100, Dave Liquorice wrote:

On Mon, 19 Oct 2009 15:31:36 -0700 (PDT), NT wrote:

I presume EBCDIC is still readable by some piece of software

somewhere

Yeah; no problem.


Òêëó@ëó@


You have me curious there. I think only a couple of those have direct
translations to ASCII, do they not? (unless usenet or my newsreader's
munging something in the transfer/display - I get the sequence: D2 EA EB
F3 40 EB F3 40 0A)

.... and if it's a machine-interpreted sequence rather than something
meaningful to a human, what's it from/do?

Certainly easy enough to code (assuming that something doesn't mangle
it...)

Â* 1) Make the format simple (so someone can pick them apart and

figure
Â* Â* Â*them out even without documentation), Â* 2) Make the format
self-documenting (e.g. such as XML, where

there's
aÂ*lot of semantic context embedded),
Â* 3) Preserve the format specification (often difficult), Â* 4) Keep
refreshing the data, converting it to the most-recent
standardÂ*as time goes on.


The trouble with 2&3 is that over time it often ceases to be worth
picking it apart, or finding compatible hardware to install the OS to
install the app to read the data.


Why on earth do you need an OS or the orginal app to read the data? All
you need is suitable hardware to extract the bit stream from the
storeage media. In the case of magnetic media that could be a bottle of
"edivu" and a microscope, with a CD/DVD/Blu_Ray just a microscope.


I think NT's point (and mine in part) is access to "suitable hardware".
Getting the data onto a modern system is often easy in comparison to
interpreting it - and sometimes the least painful* way is to find an
example of the original hardware/software combination and use it to
extract the data onto a modern platform in such a way that it is easy to
interpret.

* expense and/or time.

er you are forgetting that machines don't know anything about "plain
text" they just handle 0's and 1's in blocks called bytes which can also
be joined into words. The number of bits in a byte and/or the number of
bytes in a word can vary and ASCII is just *a* way of encoding a given
character to a bit pattern, using 7 bits per character.


Agreed. I think NT was trying to say that it's a lot easier for people
(after the fact) to understand data that's been stored in a
primarily human-readable format than it is for data stored in a primarily
machine-readable one.

e.g. (to take email as an example) I'd feel a lot happier if the world
used mbox format for message storage rather than some undocumented and
encoded Microsoft (or Sun, or whoever) format that made sense to a
specific email app but nothing else. A few decades down the line, I bet
it's going to be a lot easier to access the data in the former than the
latter, because it's essentially "plain text" and a human could look at
the file contents, figure out how it's put together, and extract
individual messages relatively easily.

Of course to get at the data at that level, you may need to access
individual files. To access individual files, you may need to understand
the filesystem. To understand the filesystem, you may need to understand
how the filesystem is stored on the media as a raw sequence of bits.
(And even then you may need to know how the raw sequence of bits
translates to variations on the media - e.g. flux transitions for
floppies and hard discs). Picking all that apart when presented with some
kind of 'alien' media can be challenging (albeit fun) - which is why it's
sometimes far easier just to access things using the original equipment!

cheers

Jules

Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Circuit Diagram help John UK diy 42 April 16th 09 03:21 PM
WANTED: Circuit Diagram the_constructor Electronics Repair 1 August 31st 07 11:08 PM
Circuit diagram [email protected] Electronics Repair 2 April 23rd 06 11:18 AM
circuit diagram brother 290 mc SISC Electronics Repair 0 August 1st 05 11:10 PM
KVM switch circuit diagram news.new Electronics Repair 1 April 7th 05 01:36 AM


All times are GMT +1. The time now is 10:16 PM.

Powered by vBulletin® Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 DIYbanter.
The comments are property of their posters.
 

About Us

"It's about DIY & home improvement"