|
DataMuseum.dkPresents historical artifacts from the history of: RC3500 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about RC3500 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 6912 (0x1b00)
Types: TextFileVerbose
Notes: RCSL-52-AA-102, RCSL-52-AA-1027, RCSL-52-AA-1035
Names: »relinf«
└─⟦a41ae585a⟧ Bits:30001842 SW-save af projekt 1000, Alarm-system
└─⟦72244f0ef⟧
└─⟦this⟧ »relinf«
>fo RCSL 52-AA 1027~LEC RC3500 SOFTWARE REVISION 3~RELEASE INF. >a1 LEC RC3500 SOFTWARE, REVISION 3 The 3rd revision of the RC3500 Software is to be generated from the first file of the magnetic tape mtdq3500: att s all xx run load mtdq3500.1 att s call 10 mtdq3500 start i revision3 The file revision3 generates 4 RC3500 binary user files: fepbin conbscbin congcibin tccbin This will last about 35 minutes. During this period, messages will be output currently. The mnemonics are: fep = frond end processor@@@@@@@@@@ (level 1) con = concentrator@@@@@@@@@@@@@@@@@ (level 2) tcc = terminal cluster concentrator (level 3) bsc = block synchronous controller gci = general communication interface From these 4 files boot- and autoload-files can be created for autoloading of RC3500/RC3503 via FPA or paper tape. You create the bootfile for FEP in this way: rc3500boot = punch16 mode.boot fpabootbin fepbin An autofile for FEP is created like this: auto3500fep = punch16 mode.auto fepbin Similar auto-files for autoloading the CON- and TCC-machines via paper tape can be created: auto3500bsc = punch16 mode.auto conbscbin auto3500gci = punch16 mode.auto congcibin auto3500tcc = punch16 mode.auto tccbin The file rc3500boot is to be placed on the autodisc (when ready for this: Rename it to "boot3500") and the remaining files are to be punched for paper tape loading (burning of ASL-programs). Notice, that rc3500boot contains the same RC3500-program as auto3500fep, and only differs in the way they are loaded. The programs should be placed in the RC3500s as indicated by the node description on the next page. >np >np Notice, that revision 3 is not compatible with revision 2, i.e. all RC3500s in the cluster must be changed at the same time. This is due to the way the RC3500s are identified. In rev. 2, the RC3500s were established with a predefined identification. In rev. 3, the RC3500s/RC3503s are identified by the level (level 1 = FEP, level 2 = CON, level 3 = TCC) and the number of the communication line, which connects the computers. The identifiers are the first letter in the CATS35-name (the remaining two letters are unaltered) and as there are two lines (BSC or GCI) to each office, all computers have two identifiers (except for the front-end) >ul internally@in@the@RC3500-system. The identifiers sent to the RC8000s are unique. Messages on the status printers use these unique letter identifications, too. The node description on the previous page uses these unique letters to identify the nodes. Notice also, that the identifiers are both capital and small letters. In the ISO - 7 bits representation you have: A=65, B=66, ....., Y=89, @Z=90, a=97, b=98, ....., y=121, z=122. The files auto3500xxx are ready to be punched with the commands headpunch headpunch auto3500xxx tpe = copy auto3500xxx with the replacement of the xxx by fep, bsc, gci or tcc. The file rc3500boot should be implemented on the autodisc by the command: autodisc = initboot device.27 sys3500.rc3500boot.168.336 >a1 HARDWARE REQUIREMENTS >ul Channels 32 I/0-channels are necessary on all RC3500s and RC3503s. >ul Real@Time@Clock@frequency RTC gives an interrupt every 20 msecs on all RC3503 computers and every 16 msecs on all RC3500s, (interrupt level 1). >ul Memory >nf FEP: 64 kb (8 memory modules on RC3500) CON: 48 kb (6 memory modules on RC3500) TCC: 24 kb (3 memory modules on RC3500) >fi >a1 FEP LAM ENTRIES The ports of the LAM multiplexer on the Frond End Processor are set up in this way: 0: 300 bps main console for RC8000a 1: 300 bps main console for RC8000b 2: 300 bps main console for RC8000c 3: 600 bps TTY programming terminal 4: 600 bps TTY programming terminal 5: 600 bps TTY programming terminal 6: 600 bps TTY programming terminal 7: 300 bps RC3500 statusprinter >a1 I/O CHANNEL LAYOUT >in-7 >ne 36 >nf >fd 3 12 26 41 56 68 >fb channel FEP GCICON BSCCON TCC >fb 0 software software software software 1 timer timer timer timer 2 FPA xmt (a) GCI read (0) GCI read (0) GCI read 3 FPA rec (a) GCI wrt. (0) GCI wrt. (0) GCI wrt. 4 FPA xmt (b) GCI read (1) GCI read (1) Ontel 1 5 FPA rec (b) GCI wrt. (1) GCI wrt. (1) Ontel 2 6 FPA xmt (c) GCI read (FEP) Ontel 1 Ontel 3 7 FPA rec (c) GCI wrt. (FEP) Ontel 2 Ontel 4 8 LAM GCI read (FEP) Ontel 3 Ontel 5 9 BBM100 GCI wrt. (FEP) Ontel 4 Ontel 6 10 GCI read (8) Ontel 1 Ontel 5 Ontel 7 11 GCI wrt. (8) Ontel 2 Ontel 6 Ontel 8 12 GCI read (9) Ontel 3 Ontel 7 Ontel 9 13 GCI wrt. (9) Ontel 4 Ontel 8 Ontel 10 14 Ontel Ontel 5 Ontel 9 Ontel 11 15 BSC cntr (0) Ontel 6 Ontel 10 Ontel 12 16 BSC cntr (1) Ontel 7 Ontel 11 Ontel 13 17 BSC cntr (2) Ontel 8 Ontel 12 Ontel 14 18 BSC cntr (3) Ontel 9 Ontel 13 Ontel 15 19 BSC cntr (4) Ontel 10 Ontel 14 Ontel 16 20 BSC cntr (5) Ontel 11 Ontel 15 Ontel 17 21 BSC cntr (6) Ontel 12 Ontel 16 Ontel 18 22 BSC cntr (7) Ontel 13 Ontel 17 Ontel 19 23 BSC data (0) Ontel 14 Ontel 18 Ontel 20 24 BSC data (1) Ontel 15 Ontel 19 Ontel 21 25 BSC data (2) Ontel 16 Ontel 20 Ontel 22 26 BSC data (3) Ontel 17 BSC cntr (FEP) Ontel 23 27 BSC data (4) Ontel 18 BSC cntr (FEP) Ontel 24 28 BSC data (5) Ontel 19 BSC data (FEP) Ontel 25 29 BSC data (6) Ontel 20 BSC data (FEP) Ontel 26 30 BSC data (7) test810/ASL test810/ASL test810/ASL 31 software software software software >fe >fi >in 7 >a1 REFERENCES >tb 17 RCSL 52-AA 1026 MULTI RC8000 DQ SYSTEM >sp 0 Operating Guide. >tb 17 RCSL 52-AA 1035 LEC RC3500 SOFTWARE, Rev. 3 >sp 0 Programming Guide. «eof»