#PARALLEL PORT DRIVER#
#PARALLEL PORT SOFTWARE#
#PARALLEL PORT FREE#
#PARALLEL PORT WINDOWS#

I'm not sure why I'm getting this message.Įdited /etc/default/grub to include idle=poll and isolcpus=3(recommended for PREEMPT)

#PARALLEL PORT WINDOWS#

I have to run it for an hour with a million OpenGL windows open for it to go above 10000). There doesn't really seem to be a latency issue as far as I can tell. I haven't found anything online about any of my hardware being funky (it's a Dell Optiplex 3020). I've disabled all power management in BIOS, audio, fan-control etc, single-core, etc etc. I ran that through the spreadsheet and set my base_period to 32500. I've run latency-test five million times, and the worst case when I really push it is 30000us. All pins function fine, and then after a moment I get the dreaded 'Unexpected realtime delay on task 0' UPDATE: When running the pport tester from command line.

#PARALLEL PORT DRIVER#

Are you saying it has to do with how much current the driver is drawing, or voltage? Should I be worried if my parallel port is outputting slightly less than 5V? I assume you are suggesting that active low will still trigger if the voltage isn't quite high enough, whereas active high won't. I see nothing explicitly about active low anything for Step/Dir.Īs to the 2nd part of your reply.

Direction signal stabile state minimum allowed valid time after step signal active edge: 1usec' The step and direction inputs interface includes an analog and also a digital filter, these filters out short pulses and noise spikes. 'Step and Direction source signals are fed to the DG2S drive through built in high speed 10Mbit/sec optoisolators.

#PARALLEL PORT SOFTWARE#

'Step signal active and inactive edges can be configured in software by user.' (There is a USB diagnostic tool called 'servo-configurator' for these drives.) But, I searched the data sheet (linked above) really quickly: Please Log in or Create an account to join the conversation.

#PARALLEL PORT FREE#

I assumed that the COM for the Step/DIR would ground to the DB25 ground, and the 12V driver logic supply and the 5V encoder supply could be ground together.Īs always, I greatly appreciate the free help and advice that this forum provides, and thank you in advance for reading/responding. Not sure where all these GND's need to go. The other supplies are +5V for encoder and 12V for driver logic, and then there is the DB25 GND. I am, in particular worried that there is something I am missing about how all the GND's connect (or don't), though I should say that there IS NOT a ground loop between the drive power (40-45VDC), and anything else. I have a bunch of stuff, including a Mesa PCIe board, on the way in case I need it, but I would love to know if there is something critical I am missing here. After a (very) short period, it also seems to freeze up and the parallel port stops sending out the pulses. I am getting very strange 'crunchy' movement out of the motors where before it was smooth (with the Teensy). I'm using old DG2S drives from CNCDrive ( Am I being naive to connect the Step/DIR/COM pins of the driver directly to the pins on the Parallel Port (Pin 1 - Step, Pin2-DIR, and Pin 25-GND)? Please note: The driver is optically isolated, and the data sheet claims to 'buffer' the signals (whatever that means). My first step is to try to get a single axis moving the way I want through the parallel port.

Now I'm trying to get everything set up with LinuxCNC. I have all the servo drives / encoders functioning properly and I have managed to control everything with step/dir pulses generated off a Teens圓.6 micro-controller. I am rebuilding the controls for an old Precix CNC. Fairly straightforward noob question here.

Parallel port