From: Stefan Diercks <stefan@sdf.lonestar.org>
To: linux-msdos@vger.kernel.org
Subject: Interrupt jitter on Kuper Control RTMC48 Motion Control Card?
Date: Mon, 30 Mar 2009 00:22:08 +0200 [thread overview]
Message-ID: <8001f8cb0903291522q6ff3c0e8y3bc85a2ea76daa5c@mail.gmail.com> (raw)
Hi Group!
I am going to install dosbox on a linux system to use some old
proprietary control software that directly accesses an ISA-Card that
controls stepper motors.
Hardware: Pentium 233 or PentiumII 233 on ATX-Board with some
ISA-Slots and a "Kuper Control RTMC48" Card (used for Motion Control
applications)
on http://www.kupercontrols.com/Kuper/Products/Kuper2001/K2001.html is
a picture of its successor. It is used to control stepper motors.
I assume it is very important, to have very little interrupt jitter
with dosbox direct hardware access. I haven't seen the card itself (it
was built into an old computer on a Film Production Set) but I have
seen the system up and running. I will figure out its IRQ and IOPORT
and use DOSBOX's Direct hardware access.
Of cause it depends on how the card manages Timers, and in what manner
Interrupts are used. Is there anyone out there who got anything
comparable running satisfactory? I expect interrupt jitter to cause
the stepper timings to run out of range. Should I use a faster
Computer to start with? :D Hmm, maybe I should, but the jitter
question is the same. What are your suggestions and experiences?
Stefan Diercks
next reply other threads:[~2009-03-29 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 22:22 Stefan Diercks [this message]
2009-03-29 22:26 ` Interrupt jitter on Kuper Control RTMC48 Motion Control Card? Frank Cox
2009-03-29 23:00 ` Stefan Diercks
-- strict thread matches above, loose matches on Subject: below --
2009-03-30 16:41 Paul Crawford (at UoD)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8001f8cb0903291522q6ff3c0e8y3bc85a2ea76daa5c@mail.gmail.com \
--to=stefan@sdf.lonestar.org \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox