Peter C. Wallace wrote:
I wasted 2 days fscking around with those cards (NetMos = MOSChip 9805 based)
I had no trouble getting them into EPP mode, they just dont work right in EPP
mode. I got write to work but they seem to sample the read data on the
leading
edge of the strobe, this is
error with hostmot2 and 7i43 board
Peter C. Wallace wrote:
I wasted 2 days fscking around with those cards (NetMos = MOSChip 9805 based)
I had no trouble getting them into EPP mode, they just dont work right in EPP
mode. I got write to work but they seem to sample the read data
Peter C. Wallace wrote:
With the 9805, I can see that the strobe ends in response to my wait signal,
but the data is sampled somewhere around the falling (leading) edge of the
strobe. I thought about an error caused by the port seeing /wait asserted too
early so even tried putting a fair
: [Emc-users] Write error with hostmot2 and 7i43 board
Peter C. Wallace wrote:
With the 9805, I can see that the strobe ends in response to my wait signal,
but the data is sampled somewhere around the falling (leading) edge of the
strobe. I thought about an error caused by the port seeing
Peter C. Wallace wrote:
With the 9805, I can see that the strobe ends in response to my wait signal,
but the data is sampled somewhere around the falling (leading) edge of the
strobe. I thought about an error caused by the port seeing /wait asserted too
early so even tried putting a fair
Sebastian Kuzminsky wrote:
I signed up for an account at MosChip.com, after that they let me see
their docs. Their FAQ for the 9805 says this:
MosChip 9805 FAQ:
An additional problem exists with EPP Mode. We have identified a timing
problem
in the chip that affects reading data from
error with hostmot2 and 7i43 board
Peter C. Wallace wrote:
With the 9805, I can see that the strobe ends in response to my wait signal,
but the data is sampled somewhere around the falling (leading) edge of the
strobe. I thought about an error caused by the port seeing /wait asserted too
Peter,
That is good news, at least as far as finding a problem and having a
probable solution. What do I need to do from here? Please feel free to
contact me off list.
BTW, regarding the EMC 2.3.7 + 7i43... thread, I also have a box with a VIA
mini-ITX motherboard
-users] Write error with hostmot2 and 7i43 board
Peter,
That is good news, at least as far as finding a problem and having a
probable solution. What do I need to do from here? Please feel free to
contact me off list.
OK overnight with 1 foot cable, no errors = 24 billion EPP operations error
@lists.sourceforge.net
Subject: Re: [Emc-users] Write error with hostmot2 and 7i43 board
Peter,
That is good news, at least as far as finding a problem and having a
probable solution. What do I need to do from here? Please feel free to
contact me off list.
OK overnight with 1 foot cable, no errors
error with hostmot2 and 7i43 board
NetMos cards that do _not_ work. They dont sample read data on the correct
strobe edge so would be almost impossible to make work with HostMot2 (that
has
read-side effects). They may be fine for bit I/O but they suck for EPP. They
also have open drain control
Peter C. Wallace wrote:
OK overnight with 1 foot cable, no errors = 24 billion EPP operations error
free. I think that one is licked. Trying 12 foot flat cable now, 360
million EPP ops with no errors so far...
I will send out new bitfiles and send replacement (patched) 7I43s.
Peter sent
Peter,
I found something interesting while checking to get your answers. Presiously
I was only jogging X and Y, and did not get any errors. This time I tried Z
as well. When I jog the Z axis I get the TRAM write error. That would
explain why I get the error when running a G-Code program, but
-users] Write error with hostmot2 and 7i43 board
Peter,
I found something interesting while checking to get your answers. Presiously
I was only jogging X and Y, and did not get any errors. This time I tried Z
as well. When I jog the Z axis I get the TRAM write error. That would
explain why I
Peter,
At this point I am just working out the configuration. I am not connected to
anything as far as hardware. There is nothing connected to the P3 and P4
connectors.
Regards,
Eric
Well thats fairly weird. If there is no configuration difference, Is it
possible that there is a electrical
-users] Write error with hostmot2 and 7i43 board
Peter,
At this point I am just working out the configuration. I am not connected to
anything as far as hardware. There is nothing connected to the P3 and P4
connectors.
Regards,
Eric
Thats even more bizzare
I bought a D945GCLF2 to test
Sebastian, et al,
I am getting a strange error using the hostmot2 driver and the 7i43 board.
The error is hm2/hm2_7i43.0: TRAM write error! (addr=0x1000, size=8,
iter=68373). The error occurs when running a g-code program but not while
jogging, at least initially.
If I bring the system up from a
] Write error with hostmot2 and 7i43 board
Sebastian, et al,
I am getting a strange error using the hostmot2 driver and the 7i43 board.
The error is hm2/hm2_7i43.0: TRAM write error! (addr=0x1000, size=8,
iter=68373). The error occurs when running a g-code program but not while
jogging
Peter,
What EPP mode are you using and what type and length of cable do you have
between the 7I43 and Parallel port?
The available parallel port modes in the BIOS are Output only,
Bi-directional, EPP and ECP. It is set to EPP, but I do not see a further
selection for mode of EPP. I think we
-users] Write error with hostmot2 and 7i43 board
Peter,
What EPP mode are you using and what type and length of cable do you have
between the 7I43 and Parallel port?
The available parallel port modes in the BIOS are Output only,
Bi-directional, EPP and ECP. It is set to EPP, but I do not see
Peter C. Wallace wrote:
On Thu, 4 Dec 2008, Eric H. Johnson wrote:
I am getting a strange error using the hostmot2 driver and the 7i43 board.
The error is hm2/hm2_7i43.0: TRAM write error! (addr=0x1000, size=8,
iter=68373). The error occurs when running a g-code program but not while
Peter C. Wallace wrote:
On Thu, 4 Dec 2008, Eric H. Johnson wrote:
I am using the servo-thread for read and write. I also tried slowing down
the servo thread, although I could try slowing it down more. I was using 1ms
(100).
1 ms should be fine (I think 100Usec is the approximate
22 matches
Mail list logo
