Re: [Emc-developers] PCIe EPP parport issues

2022-09-07 Thread Bari

Sam,

I lowered the base thread to 25uS and the encoder error: rtapi_app: 
caught signal 8 - dumping core ,   is gone!


-Bari


Brand new setup using stepconf.   if I spin the spindle encoder 
quickly by hand I get: rtapi_app: caught signal 8 - dumping core


Even if the machine is still in e-stop.   Simple config using 
stepconf   LINUXCNC - 2.9.0~pre0 and 5.10 preempt_rt


All default settings other than manual edit of LPT base address and 
changed   setp encoder.0.position-scale 4000.00    Default is like 
100 vs 4000


Any ideas what causes this error?

https://forum.linuxcnc.org/media/kunena/attachments/1324/simple.ini

https://forum.linuxcnc.org/media/kunena/attachments/1324/simple.hal

The only mention of a similar error: 
forum.linuxcnc.org/24-hal-components/358...hercat-lcec?start=10


https://forum.linuxcnc.org/49-basic-configuration/46796-rtapi-app-caught-signal-8-dumping-core 



All the files are here.  ^^ 




___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] PCIe EPP parport issues

2022-09-07 Thread Sam Sokolik
one interesting thing...  If you crash out of 2.9 - the installed 2.8 won't
start until you re-launch and exit 2.9..  (no - linuxcnc is already running
- do you want to exit?)

I will get the error that comes up when you try to launch 2.8...

sam

On Tue, Sep 6, 2022 at 4:43 PM andy pugh  wrote:

> On Tue, 6 Sept 2022 at 22:34, Bari  wrote:
>
> > So it looks like an RTAI bug with 2.8 at least about the encoders
> > signals to spindle RPM GUI in Axis.
> >
> > Will go back and trace why preempt_rt has issues with LPT encoders in
> > LCNC 2.9.
>
> If there is a difference between the realtime versions then I would be
> looking in the rtapi code for different implementations of rtapi_inb
> https://linuxcnc.org/docs/stable/html/man/man3/rtapi_inb.3rtapi.html
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1912
>
>
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] PCIe EPP parport issues

2022-09-06 Thread andy pugh
On Tue, 6 Sept 2022 at 22:34, Bari  wrote:

> So it looks like an RTAI bug with 2.8 at least about the encoders
> signals to spindle RPM GUI in Axis.
>
> Will go back and trace why preempt_rt has issues with LPT encoders in
> LCNC 2.9.

If there is a difference between the realtime versions then I would be
looking in the rtapi code for different implementations of rtapi_inb
https://linuxcnc.org/docs/stable/html/man/man3/rtapi_inb.3rtapi.html

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] PCIe EPP parport issues

2022-09-06 Thread Bari

On 7/30/22 20:57, Jon Elson wrote:


On 7/16/22 22:05, Jon Elson wrote:

Well, the saga continues!  I thought I had this all working, but then 
rebooted today, and could not get the MCS9900 card to work properly.  
I could run my diag and see the boards respond, but then when I ran 
some tests, the parport would lock up, and lspci -vv would show 
"disabled" next to the port addresses.  The only way to clear it was a 
reboot.  Same thing happened with a Siig OXPCIe952 card.


It is pretty clear that either the driver or some other kernel module 
is taking control of the parport when I want to run at the "bare 
metal" level.  This appears to be new behavior with this kernel on the 
2.8.2 distro.


So, I gave up on PCIe cards, and swapped the hard drive into a Dell 
980 with a parport on the motherboard. All seems to work very well on 
that system.



Brand new setup using stepconf.   if I spin the spindle encoder quickly 
by hand I get: rtapi_app: caught signal 8 - dumping core


Even if the machine is still in e-stop.   Simple config using stepconf   
LINUXCNC - 2.9.0~pre0 and 5.10 preempt_rt


All default settings other than manual edit of LPT base address and 
changed   setp encoder.0.position-scale 4000.00    Default is like 
100 vs 4000


Any ideas what causes this error?

https://forum.linuxcnc.org/media/kunena/attachments/1324/simple.ini

https://forum.linuxcnc.org/media/kunena/attachments/1324/simple.hal

The only mention of a similar error: 
forum.linuxcnc.org/24-hal-components/358...hercat-lcec?start=10


https://forum.linuxcnc.org/49-basic-configuration/46796-rtapi-app-caught-signal-8-dumping-core

All the files are here.  ^^

I tested this on LCNC 2.8 and I can see encoder signals in halscope but 
nothing in the Axis GUI spindle rpm display.


And no signal 8 core dump with LCNC 2.8 and RTAI

OK tested LCNC 2.8 with preempt_rt and the encoder signals make it to 
the GUI using a preempt_rt kernel vs RTAI!


NO signal 8 core dump \0/

So it looks like an RTAI bug with 2.8 at least about the encoders 
signals to spindle RPM GUI in Axis.


Will go back and trace why preempt_rt has issues with LPT encoders in 
LCNC 2.9.



Another odd thing is that when also testing the CH382 LPT PCIe card the 
encoders signals are making it from encoder to BOB through the CH382 and 
I can see them in halscope BUT the steps generated do not make it out of 
the CH382 to the BOB. But CH382 debug is another project.


And today I see similar issues with ALL my other LPT controllers with 
2.9 and 5.x preempt_rt kernels





___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] PCIe EPP parport issues

2022-07-30 Thread Jon Elson

On 7/16/22 22:05, Jon Elson wrote:

Well, the saga continues!  I thought I had this all working, 
but then rebooted today, and could not get the MCS9900 card 
to work properly.  I could run my diag and see the boards 
respond, but then when I ran some tests, the parport would 
lock up, and lspci -vv would show "disabled" next to the 
port addresses.  The only way to clear it was a reboot.  
Same thing happened with a Siig OXPCIe952 card.


It is pretty clear that either the driver or some other 
kernel module is taking control of the parport when I want 
to run at the "bare metal" level.  This appears to be new 
behavior with this kernel on the 2.8.2 distro.


So, I gave up on PCIe cards, and swapped the hard drive into 
a Dell 980 with a parport on the motherboard. All seems to 
work very well on that system.


Jon



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


[Emc-developers] PCIe EPP parport issues

2022-07-16 Thread Jon Elson
I have been selling Syba SD-PEX10005 PCIe parallel port 
cards for several years, they seem to work well with most 
computers and LinuxCNC and my line of motion interfaces.  
Now, I have 2 Dell Optiplex 7010 computers that they do NOT 
work on.  It seems that both my diagnostic program and the 
hal_ppmc driver don't talk to it correctly.  These cards use 
the MOSCHIP MCS9900 or MCS9901 chip.  I have one remaining 
Siig card that uses the Oxford Semi chip and it works.  I 
thought I had this EPP weirdness pretty much solved, but now 
I'm up the creek without a paddle again.  Does anybody know 
anything about these PCIe-EPP issues?


Thanks in advance for any help!

Jon



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers