On 06/25/2018 08:47 PM, Jon Elson wrote:
On 06/25/2018 12:57 PM, andy pugh wrote:
On 25 June 2018 at 17:07, Jon Elson
wrote:
On 2.8.0~pre1 (I think I get this on 2.7.14 also) any
config that accesses
the parallel port produces
an error message on the Axis screen:
Using the hal_parport driver
On 06/25/2018 12:57 PM, andy pugh wrote:
On 25 June 2018 at 17:07, Jon Elson wrote:
On 2.8.0~pre1 (I think I get this on 2.7.14 also) any config that accesses
the parallel port produces
an error message on the Axis screen:
Using the hal_parport driver or using the ppmc driver?
It does NOT seem
On 25 June 2018 at 17:07, Jon Elson wrote:
> On 2.8.0~pre1 (I think I get this on 2.7.14 also) any config that accesses
> the parallel port produces
> an error message on the Axis screen:
Using the hal_parport driver or using the ppmc driver?
I wrestled with this a bit with the hm2_7i43 driver,
On 2.8.0~pre1 (I think I get this on 2.7.14 also) any config
that accesses the parallel port produces
an error message on the Axis screen:
linux parallel port @57360 not found
57360 decimal does equal 0xe010, which is my parport
address so it is just printing it as decimal, but why does
it s
OK, further info. On this Wheezy-preempt system, kernel
messages from RT components do NOT show up in dmesg!
But, if you run LinuxCNC from the command line, these
messages from RT components/drivers do show up in the
standard output.
So, although I get the par port not found error, the ppmc
