For Micro-stepper systems, you will need to purchase a Motion Control pulse generator card, which can be any one of these:
..and your computer will need an available ISA/EISA slot for it.
For Half-step systems, you should have two or more available parallel ports, as these will be used to control the motor drives. The half-step systems do *NOT* need a Kuper card.
OPCS has a very powerful, flexible way to make your own custom home-sensing operations for each axis, both rotational and linear. See recommended engineering for more information.
Some customers use Mac scanning software, and connect the Mac to the OPCS system's IBM-PC to control the OPCS software via the IBM PC's serial port. For more information, see the OPCS documentation for the respond command.
However, you can use the motion control software available from Kuper Controls to do streaking. The OPCS and Kuper software can coexist on the same machine, and used interchangeably to run a printer.
cam 10 | Shoot 10 frames on the camera |
cam -10 | Shoot 10 frames in reverse |
rep 50 | Shoot 50 frame straight print |
seek >100 | Slew camera out to frame 100, camera capped |
seek >120 >100 | Slew projector and camera together with camera capped; projector to frame 120, camera to frame 100 |
pro 10 | Wind off 10x on the projector |
opn | Open the fader |
cls | Close the fader (cap) |
shu 50 | Open the shutter to 50 degrees |
fdi 12 | Setup a 12 frame fade in |
rat 2 1 rep 50 | 50 frame 2:1 step print |
fdi 12 cam 12 | Shoot 12x fade in on still projector image |
rat 1 1 fdi 12 rep 12 | Shoot 12x fade in on moving projector image (straight print) |
feed trackit.pos rep 120 | Shoot a 120 frame motion control file |
dxo 12 rep 12 pro >330 seek -12 dxi 12 rep 12 | 12x cross-dissolve between moving projector images |
do 200 dxo 8 rep 8 pro 8 seek -8 dxi 8 rep 12 | Shoot 200 8 frame cross-dissolves between every 8th frozen projector image |
fdi 12 cam 12 | Fade in to frozen projector image |
rat 1 1 fdi 12 rep 12 | Fade in, straight print |
C:\> attrib -S -H -R \msdos.sys |
C:\> edit c:\msdos.sys |
BootGUI=1 |
..and change it to read:
BootGUI=0 |
Example I used just after formatting a new C: drive. The file's contents had one line, ";FORMAT", so when editing this file, I removed that line and made the entire contents of the file to be:
[Options] BootGUI=0 Logo=0 BootDelay=0
C:\> attrib +S +H +R \msdos.sys |
See the section on the kuper card or the printed docs that come with the kuper card.
WARNING: You will LOOSE ALL DATA on the hard disk drive by doing these steps. We're assuming you want to make a NEW bootable hard disk.
1. Start with a bootable Win95 DOS disk that has the minimum tools on it: > command.com -- dos command shell > format.com -- use to format the C: drive > sys.com -- copies DOS operating system to a drive > fdisk.exe -- disk partitioning tool > edit.com -- to edit files > attrib.exe -- to change perms on MSDOS.SYS to edit it > ansi.sys -- OPCS will need this 2. Boot the floppy, and use "fdisk" to repartition the drive. This will let you pick a drive to work on, and repartition it and lets you choose which partition is the boot partition. The simplest configuration is to remove all existing partitions, create one single "primary" partition that is as large as DOS allows (2Gig), make it the 'Active' partition (the boot partition), and leave the rest of the disk unallocated. To do this: 2a. Run: fdisk 2b. Hit ENTER past questions about large disk report. 2c. The main menu will have these choices: -------------------------------------------- 1. Create DOS partition or Logical DOS Drive 2. Set active partition 3. Delete partition or Logical DOS Drive 4. Display partition information -------------------------------------------- 2d. Remove all existing partitions: * Use option '4' to display current partitions. * Use option '3' to delete the existing partitions (if any) 2e. Create a single new primary partition. Use option '1' to create a new primary partition 2f. Make the new partiton the 'active' (bootable) partition. Use option '2' to make the new primary parititon 'active' 2g. Verify the partition layout and quit fdisk. Use option '4' to display the disk info. It should look something like: ----------------------------------------------------------------- Current fixed disk drive: 1 Partition Status Type Volume Label Mbytes System Usage C: 1 A PRI DOS 2047 FAT 16 100% ----------------------------------------------------------------- Then quit fdisk. 3. Reboot from the floppy. (When you quit FDISK in the last step, it warns you to reboot, and you should.) On reboot, the C: drive should now exist, but since it hasn't been formatted yet, you won't be able to view it with DIR C: until you format it. For instance: A:\>DIR C: Invalid media type reading drive C Abort, Retry, Fail? Proceed to step 4 to format the drive so that you can actually pull up a directory listing. 4. Format the C: drive to be bootable. Use this command: format c: /s /v:MY_WIN95 5. After formatting, you should now be able to bring up a directory listing of the C: drive by running: dir c: Don't try to boot the C: drive yet. If you do, it may show a garbage screen. This is because it's trying to start the Windows GUI, which we don't need. 6. Modify the 'hidden' MSDOS.SYS file on the C: drive using the steps shown here. 7. Try booting the harddisk by ejecting the floppy, and letting the BIOS boot the hard drive. You should get a "C:\>" prompt. If it doesn't boot the hard drive correctly, you may need to use the "fdisk /MBR" command to make sure the hard drive boots correctly.
To mount one of the win95 or win98 full disk images on a linux machine: 1) Use this to determine the offset of the boot partition: # fdisk -l opcs-02-16-2022-backup.img Disk opcs-02-16-2022-backup.img: 3.74 GiB, 3997163520 bytes, 7806960 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes -------------------------------------. I/O size (minimum/optimal): 512 bytes / 512 bytes | Disklabel type: dos | Disk identifier: 0x00000000 | | Device Boot Start End Sectors Size Id Type | opcs-02-16-2022-backup.img1 * 8128 7806959 7798832 3.7G c W95 FAT32 (LBA) | ---- | |__________________________________________ | | | 2) Compute the offset in BYTES of the partition by multiplying the "Start" sector# | | by the "Sector size" in bytes, e.g. | | _____________________________________________________________________________| | | | | ____________________________________________________________________________________| | | \|/ \|/ v v 8128*512 = 4161536 bytes ---- --- ======= |_______________________________ | 3) Use the computed offset in the mount command: | _________________| | \|/ v mount -t msdos -o loop,offset=4161536 opcs-02-16-2022-backup.img /mnt/dos =======
I've found 'dd' works great for making byte-for-byte backups of CompactFlash cards as disk images. USB compact flash card readers like the Sony MRW62E card reader can be plugged into a linux or mac machine, and the CF drive plugged into that. Then to make a backup disk image: LINUX: dd if=/dev/sdb of=/var/tmp/opcs-backup-MM-DD-YY.img bs=1M MAC: dd if=/dev/rdisk2 of=/var/tmp/opcs-backup-MM-DD-YY.img bs=1m ----------- --------------------------- | | | Output image Fast raw disk device (faster than e.g. /dev/disk2) Note that to specify "megabyte" suffix for the dd command's block size (bs=), it needs to be a caps "M" on linux, and lowercase "m" on Mac. And on Macs, /dev/rdiskXX is much faster than /dev/diskXX. Note that to use dd properly, the disk has to be unmounted.
© Copyright 1997, Greg Ercolano. All rights reserved. To report documentation errors, send email to |