http://hackaday.com/2013/03/02/24-port-gpio-on-a-pci-card/
This hack involves hand soldering 24 tiny wires to a surface mount chip.
But it's an interesting idea.
"It’s a great build if you’d like some GPIO action without going
through the usual parallel port mess, and especially useful since the
Charles Steinkuehler writes:
>I'm really thinking more about the folks approaching LinuxCNC from the
>3D printing / Desktop CNC world, which seems to revolve around stepper
>motors, Polou microstep drivers, and Arduinos.
The RepRap folks are using the ATmega 644P, which has more I/O pins than
t
Jon Elson writes:
>> However, we still like to get a *real* one for rigid tapping ;-)
[...]
>But, in the US we have these cheap "mini mills" that are
>about 60 Kg and fit on a small desk. They have DC brush motor drives.
>I modified one to have an encoder on the spindle, and rigged a servo amp t
dave writes:
>A couple of years ago I tried the APT software on the wiki
Is this what you're talking about?
http://sourceforge.net/projects/aptos/
Or something else?
--
Try before you buy = See our experts in action
"Kent A. Reed" writes:
>On 1/25/2012 10:56 PM, Jon Elson wrote:
>> The BeagleBoard is a good candidate, about 2W with an SD card for
>> "disk", USB
>> ports, etc. No RTAI so far, but that might come soon.
>>
>> Jon
>>
>Jon:
>
>With respect to this list, it's now closing in on two years since yo
on Elson writes:
>I've already paid for one BeagleBoard and sent it to a developer who
>didn't make much progress
>with it. At least, he still isn't finished.
>
>One problem with the OMAP chip they use in the Beagle is the GPIO is
>only updated every 240 ns, although
>the CPU is about 40 times f
Kirk Wallace writes:
>It may be that an Arduino could do this, but my impression is that there
>aren't enough AVR pins coming out to where one could get to them. The
>price of the smaller Arduino's seems to fit my plan though.
The RepRap and MakerBot use a different AVR chip that has a dozen mor
Kirk Wallace writes:
>By the way, I got the ATmega32 version working, so I have eight bits of
>input now, plus a bunch of pins left over. Four PWM channels are
>advertised but they aren't fully independent of each other and share
>pins with other features, so the plot thickens.
You might want t
andy pugh writes:
>On 18 December 2010 20:41, Kirk Wallace wrote:
>>
>> Am I on acid?
>
>Considering Mesa's prices, quite possibly.
That depends on whether price is the primary consideration.
Sometimes hacking is its own reward.
---
Another OMAP-based board, said to be similar to the Beagleboard:
http://www.hawkboard.org/
http://elinux.org/Hawkboard
Of particular interest is the 100-pin expansion connector, with a whole
bunch of GPIO pins. I just heard about it yesterday, so I haven't had
time to look at it in any detail.
Jon Elson
>But, I think the difficulty of making your own boards for FPGAs, and
>then building them and
>testing them may have made this too complicated for the average
>tinkerer. Without a logic analyzer
>and an oscilloscope, if it doesn't work, it could be real hard to
>determine what is wrong
Jon Elson writes:
>Yup, few people use bare GPIO, and the documentation, all 3700 pages of
>it, has the info but it is REALLY hard to figure out how to set up the
>GPIO pins to use them.
I read somewhere (maybe on the Gumstix site) that the easiest way to set
them up is to recompile the bootload
Are the Beagleboard and the Gumstix Overo-Water similar enough that
the Beagleboard port is likely to run on the Overo?
I'm disappointed in the small number of GPIO pins available on the
Beagleboard. Oddly, I haven't been able to find a straightforward
breakout board for the OMAP 3530-- they al
Dave writes:
>The only way around this is to run your machine very slowly, which some
>would say, negates a lot of the benefits of CNC'ing your machine.
I would disagree, although it depends on what you're doing.
>At some point fixing the machine is more productive than trying to work
>around a
Jon Elson writes:
>NIST started on Sun Workstations, and then tried out some of the RT
>extensions to Windows NT, and found them to be horrible.
>Every hour, you could get interruptions up to a second or so. A total
>joke for real time control.
How does Mach3 handle this with current versions o
EBo writes:
>Other than that,
>there are a number of unix specific stuff that will probably require a LOT
>work to replace the underlying functionality.
Can you be more specific? What kinds of things are we talking about? I'm
not so much looking for a full explanation, but for pointers to which
Asking mostly out of curiosity at this point, but it seems like it would
be good to know:
What parts of EMC2 are specific to the Linux OS? Obviously the RTAPI
stuff, and the LibNML stuff. Anything else?
What parts of EMC2 are specific to the x86 CPU? HAL is obviously
hardware-specific. Anything e
Jon Elson writes:
>The Beagle has a 28-pin header with a scrambled bunch of GPIO pins. It
>was a little tricky to find 8 contiguous bits plus the necessary
control
>bits.
[...]
>I crashed the Linux OS a
>number of times before finding out what other GPIO pins in the same bank
>were used for ot
18 matches
Mail list logo
