Tech Support

Be sure you have a file named "tcaudit" in your Kuper directory. There should be NO extension, such as ".txt" etc. If this file is not present, create it using the "copy con tcaudit" command or a text editor such as the DOS "Edit" text editor...contact Kuper for specific instructions. The contents of this file are not important, all that matters is its presence in the Kuper directory. Use the "ti" command to set the Kuper2001 timecode direction to in or out. The "th" command sets the hours, minutes, seconds, frames.

The time code common must be attached to pin 10 of the Kuper DB15 Accessory Connector, which is labeled "LTC TIMECODE-" on the connector drawing. Previous Kuper cards could accept time code common on any ground pin, but the time code signals on the Kuper2001 and KuperDat cards are electrically isolated such that only pin 10 can be used as the timecode common. If you are using a signal breakout box, please be certain that the time code common is ultimately routed to pin 10 on the Kuper Accessory Connector. If possible do not connect the timecode common to any other ground connection at the computer end of the cable.

The timecode signal should be at least 7/10 of a volt. For most professional audio and tape decks this requires the timecode signal to be recorded at not less than about -4db. For best results, record timecode at 0db. Automatic gain circuits on consumer decks usually prevent the signal from reaching more than 1/2 volt, so you may need to use an outboard line amplifier with a consumer deck. If a "logic level" timecode source is available, always use that. For best result the timecode should be received as a differential pair inside a shielded cable. Many audio professionals are used to working in electrically quiet environments and will send you single-ended timecode carried in RGxx cable, with the shield used as a timecode common. The chances of this working well near motor driver cables generating 400+ volt, high frequency spikes is slim indeed...whenever possible try to obtain timecode as a differential pair inside a shielded cable, per the SMPTE specification. In cases where you must use single-ended timecode, you may get better results by connecting the "TimeCodeIn-" pin on the Kuper accessory connector to that connector's GND pin.

Note that both the Kuper2001 and KuperDat cards can generate timecode that is exactly synchronized to the motion control. This is a good option for situations where "house" timecode is required. Use the "ti" command to set timecode direction to "Out", and the "th" command to set the timecode Hours:Minutes:Seconds:Frames. The timecode output is available on the DB15 accessory connector.

Please take a moment to see if your issue is covered in the list below. In any case feel free to give us a call. Experience has shown that technical issues are much easier to resolve on the telephone, than via email.
Telephone:	310-414-0701. Office hours, 9:00 Am ~ 6:00 PM, Pacific Time.
email:	techsupport@kupercontrols.com

*COMMON TECHNICAL SUPPORT ISSUES*
On my Kuper2001 or KuperDat system the Jogbox responds sluggishly when I type in numbers.
	This is a known bug which is fixed in the Kuper2001 software update to be released in February, 2005. If you would like this fix before then, please contact us. KuperDat owners please contact us for a software update.
I sometimes get move data corruption on certain axes.
	This is known problem on certain older versions of the Kuper software. This is corrected in all software versions now posted on this site. A minimum of 16 megabytes of RAM is required from for correct software operation.
My old RTMC16 Card doesn't work with the software I just downloaded.
	There is a specific version of the software for the RTMC16 card, which is available on this site's software page. For the RTMC16 Card only, you must also have a pragma file named "RTMC16" located in directory from which you run RTMC130.exe. This pragma file should have no extension, and only its presence is important, its content does not matter. You can copy some other small file such as "RTMC.env" to "RTMC16" to create the file. Contact us if you need help.
I can't read timecode on my Kuper2001 or KuperDat card.
	Be sure you have a file named *"tcaudit"* in your Kuper directory. There should be NO extension, such as ".txt" etc. If this file is not present, create it using the "copy con tcaudit" command or a text editor such as the DOS "Edit" text editor...contact Kuper for specific instructions. The contents of this file are not important, all that matters is its presence in the Kuper directory. Use the "ti" command to set the Kuper2001 timecode direction to in or out. The "th" command sets the hours, minutes, seconds, frames. The time code common must be attached to pin 10 of the Kuper DB15 Accessory Connector, which is labeled "LTC TIMECODE-" on the connector drawing. Previous Kuper cards could accept time code common on any ground pin, but the time code signals on the Kuper2001 and KuperDat cards are electrically isolated such that only pin 10 can be used as the timecode common. If you are using a signal breakout box, please be certain that the time code common is ultimately routed to pin 10 on the Kuper Accessory Connector. If possible do not connect the timecode common to any other ground connection at the computer end of the cable. The timecode signal should be at least 7/10 of a volt. For most professional audio and tape decks this requires the timecode signal to be recorded at not less than about -4db. For best results, record timecode at 0db. Automatic gain circuits on consumer decks usually prevent the signal from reaching more than 1/2 volt, so you may need to use an outboard line amplifier with a consumer deck. If a "logic level" timecode source is available, always use that. For best result the timecode should be received as a differential pair inside a shielded cable. Many audio professionals are used to working in electrically quiet environments and will send you single-ended timecode carried in RGxx cable, with the shield used as a timecode common. The chances of this working well near motor driver cables generating 400+ volt, high frequency spikes is slim indeed...whenever possible try to obtain timecode as a differential pair inside a shielded cable, per the SMPTE specification. In cases where you must use single-ended timecode, you may get better results by connecting the "TimeCodeIn-" pin on the Kuper accessory connector to that connector's GND pin. Note that both the Kuper2001 and KuperDat cards can generate timecode that is exactly synchronized to the motion control. This is a good option for situations where "house" timecode is required. Use the "ti" command to set timecode direction to "Out", and the "th" command to set the timecode Hours:Minutes:Seconds:Frames. The timecode output is available on the DB15 accessory connector.
The voltage outputs "roll over" between minimum to maximum.
	Kuper axes that must function as voltage outputs must be assigned as DAC outputs in the Kuper software. Click "MouseJog" then slick "PatchDAC". Note the 1 or 2 digits axis numbers to your left of each axis name. Click on this number to make it Yellow, this identifies the axis as a DAC axis to the software, and prevents roll over. If "ModeSet:Software Position Limits" set the minimum and maximum positions limits in the left 2 columns to the range of screen position units that should map the entire available voltage range of DAC output.
I can't change the pulses per camera frame using the AxisSetup Button.
	You must now use the new "pd" command, or click "HardSet", then "4 Perf / 8 Perf Parameters". Fill in the appropriate dialog box.
The screen goes blank when I run the Kuper Software.
	This is usually caused by the mouse not being plugged in, or if the mouse driver has not been loaded. The Kuper card may also be out of its bus connector, a common problem when the system has been recently moved. For ISA cards, run the setrtmc.exe program on the Kuper distribution disc, and verify that jumpers J10 and J11 on the Kuper card are set properly for the address and interrupt vector reported by setrtmc.exe. If you get a blank screen during installation it is probably caused by address conflicts with the computer's sound card or network card. If the factory settings of address 300 hex and interrupt line 5 do not work, try address 2c0 hex, and interrupt line 7. You must run setrtmc.exe each time you change the hardware jumper settings. If you experience installation problems, we recommend that you call us before making any address or interrupt vector changes.
The PUSH-IN, PUSH-OUT buttons don't work.
	The PUSH buttons only work when the Virtual Axes are turned on, and only work correctly when the Virtual Axes are properly calibrated.
PUSH-IN, PUSH-OUT speeds are too fast.
	Use the "pv" command to modify the overall speed. "pv 25" reduces the "pushing" speeds to 25% of normal.
I can't get timecode to work right with my RTMC48 Card.
	Try using a HumBucker audio line isolator, available from pro audio stores. The RTMC48 Card uses the system ground as the timecode common. It is possible that the timecode common trace has been burned out by a severe external ground loop, since timecode often comes from a location on a different ground. You can test for this by checking for continuity between pin 10 of the 15 pin Kuper accessory connector, and the metal case of the computer. After eliminating the ground loop, you may be able to restore timecode by changing the timecode common wire from the recommended pin 10 (TCODE-) to pin 1 (system ground) on the 15 pin Kuper accessory connector. You may also need to change the CA3140 or LM741 8-pin opamp on the RTMC48 Card. Contact us if you have a persistent timecode problem.
How do I program the Timecode Trigger Point?
	Use the "tt" command typed at the keyboard. Enter the desired Hours, Minutes, Seconds, Frames separated by spaces. Press Enter. Click the "start condition" box just above the "REV STOP FWD" boxes, until it reads "Start: TimeCode Trigger".
My Kuper program window is small, can I change its size?
	The Kuper program window has a default screen resolution setting of 640X480. It will look small on a higher resolution and bigger monitor screen. The program window will not get bigger than 640X480.
I plugged in a new device I just made, and smoke started coming out of the computer! Is this normal?
	Take a deep breath, call us, talk slowly and evenly. Next time consult with us first, plug later!