My ongoing troubles with using the ax5214h driver with an Acess DIO-48 card
may be of assistance to some others.
I checked the Axiom manual for the card, and discovered that the three
most significant bits of the 8255 control reg. were pre-empted in some way
on the board. This resulted in " do
I Dave
Glad you got it going. This reminds me of 8255 struggles from days long
gone.
Rayh
On Wed, 2007-09-26 at 06:30 -0500, [EMAIL PROTECTED] wrote:
> My ongoing troubles with using the ax5214h driver with an Acess DIO-48 card
> may be of assistance to some others.
> I checked the Axiom m
Can you please look over the following "diff" and tell me if it
expresses the same changes you made? If so, I'll make sure this change
is in emc 2.2.0 when it is released.
Jeff
--- hal_ax5214h.c 21 Jan 2007 17:00:16 - 1.14
+++ hal_ax5214h.c 26 Sep 2007 12:57:30 -
@@ -576
Yes Jeff, that looks like exactly what I did. -- Bearing in mind that it
was for a Acess PCI-DIO-48s board. I think that it
can be used with the Axiom board as well with 100% success ( I wish I had
one of their boards to test ) .
I think someone should test this before any changes are mad
Indeed -- I don't have such a card to test. (I didn't read your earlier
message closely enough and missed the fact that this is merely a card
similar to the axiom card)
I think I understand why the original configuration outb()s are written
in that order: In the new order, the outputs are enabled
Hi all,
Right after I successfully added a fourth (rotary) axis, I decided that
I would adjust the homing and limit settings to avoid interference
between the spindle and the new parts. So far, I've managed to break
both! (both the home and limit settings, that is...not the rotary axis
and t
Patrick Ferrick wrote:
>
> So here's my question: can I post a picture of my Y-axis, say,
> along with the appropriate part of my ini file? Or are there list
> members with dialup access who will object to the attachment?
>
It is better to avoid large posts on the list. For images, try
http
the new code mod is like this:
/* initialize hardware - all outputs high
(since outputs are active low) */
== ADDED THE FOLLOWING
outb(0xff, board->base_addr+0);
outb(0xff, board->base_addr+1);
outb(0xff, board->base_addr+2);
outb(0xff, boa
