Re: [Machinekit] Which kernel is the fastest running Machinekit on BBB?

[Simon S]

Hi!

Sorry about beeing unclear. I know that I switched the underlaying RT os.

The jessie box runs: 
Linux beaglebone 3.8.13-xenomai-r83 #1 Thu Jan 5 01:32:32 UTC 2017 armv7l 
GNU/Linux

And on stretch:
Linux beaglebone 4.19.37-bone-rt-r33 #1stretch 
 PREEMPT RT Wed Jun 5 11:22:07 UTC 
2019 armv7l GNU/Linux

I switched all driver/config stuff to use the preempt rt stuff.

The jessie box is perfectly fine. The stretch based one is unusable. 
I am wondering how others use a stretch based image and if I am doing 
something wrong
and there is a "magic" kernel version that is fast enough to be used.

I did a simple benchmark opening a text engraving gcode file from fusion360.
On the Jessie box it takes ~20s from clicking load to display.
On the stretch base box takes around 4 minutes...

Or could it have something to do with the fact that the stretch image runs 
from SD and the jessie from internal flash?
Is there so much disk I/O involved?

Regards,
Simon

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/4200d6cb-fb91-44db-ba6b-65e2e4cd825a%40googlegroups.com.

Re: [Machinekit] Re: DE10 Nano suggested development environment?

[Michael Brown]

Not very easy from my cell phone here however:
In qsys there are 2 instances where you set up the timings for the screen
monitor. There should be some saved setups HD etc. Lastly you need to place
the correct screen settings in the device tree there is a HD example there
too. 1920 x1080. Sorry for not being online atm...

On Tue, 30 Jul 2019, 00.16 justin White  wrote:

> Yup still on the edge of understanding. dk beyond reason. I'm still on 1/2
>> gear .
>>
>
> That's OK, at the moment I'm just trying to make sure the hardware works
> OK for smart serial and maybe get you a little insight of the issue when
> you get around to looking at it. From what I gather ClockLowTag is what
> should be specified in the pinfile and ClockMed is I guess used internally
> to determine SS baud rate. Seems that somewhere in the firmware SS is not
> "connected", as in it should print "SmartSerial version 43" when
> instantiated rather that version 0 as does when I build with it. That's
> just the way I understand it so take it with a grain of salt.
>
> and you do know that mksocfpga only has an accelerated frame buffer and
>> still no real unlicenced GPU.
>>
>
> Yeah I know, I'm not trying to run 3D acceleration or anything, it's just
> since the FB is fixed the monitor must either display 1024x768 natively or
> scale it. Alot of smaller or obscure monitors don't seem to negotiate
> resolutions well or at all so the server side must do it, in this case it
> can't so I suppose the firmware needs to be built for whatever resolution
> is needed. If you can point me in the right direction I can try to build it
> myself..In the meantime I scooped up an older 4:3 LCD so I don't have
> to drag a monitor I use over to my mill when I need to try something.
>
> I had some time so I made up a standalone test GUI. I did sort out the ADC
> conversion stuff in hardware and HAL. Resistor dividers actually do work
> well, I initially didn't use correct values. I used the method I mentioned
> previously to scrub the 32bit integer and scale it to a useable voltage
> with hal components. It actually works very well this way but has a bit of
> noise. I gave a friend of mine some guidance on writing a single HAL
> component that can handle the conversion as well as digitally filter the
> output. I'll see how well that works before I go back and add more passives
> to try to filter the noise.
>
> [image: remmina_DE10-Nano MK VNC_192.168.1.125_2019729-53925.864069.png]
>
>
>
> --
> website: http://www.machinekit.io blog: http://blog.machinekit.io github:
> https://github.com/machinekit
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Machinekit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/machinekit/eVhvTnuhblE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> machinekit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/machinekit/dfe26639-27a7-4ba6-b9bf-344bd1d0da9e%40googlegroups.com
> 
> .
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/CAGKWNWPV48N-D8-ZEY6KgyfsOHbCt4rvhk%3D9x%3D%3D3_V%3Df-koPHA%40mail.gmail.com.

Re: [Machinekit] Which kernel is the fastest running Machinekit on BBB?

[cern]

Hello,
Aug 6, 2019, 11:07 AM by fishpep...@gmail.com :

> Hi!
>
> My old machinekit installation runs on a BBB under debian jessie with a 
> xenomai kernel.
> I start the axis gui via an SSH session using indirect OpenGL rendering.
> For normal CAM jobs this is reasonable fast and the gui is responsive.
> Only huge jobs with e.g. 3D cam operations take some time to load but then 
> they are fine as well.
> I want to switch to a more recent version because I can not get the XHC-HB04 
> pendant working under jessie
> (see https://github.com/machinekit/machinekit-hal/issues/209)
>
> So I  configured a second BBB using debian stretch.
> I tested various kernels but all seem to be way slower than the old kernel
> coming with my debian jessie image.
> Some kernels export the wrong cpu frequency settings and do not use the 
> maximum clock but even those who do are still slow.
> Opening a very basic CAM jobs in axis loads for a minute or more.
>
> Something seems wrong... When I open a second console via ssh
> while axis is running the console is laggy and unresponsive as well.
>
> Any hints?
>
I am not completely sure if you are talking about the latency of HAL instance 
or the general responsiveness of Linux OS. However, to use Debian 
Buster/Stretch with modern kernel version, you pretty much have to use 
Preempt_RT or Vanilla. The Xenomai currently in Machinekit is EOLed 
2.6.something version running in tandem with 3.something Linux kernel. To use 
4.19.something or 5.2.something kernel, you would need the Xenomai3 or EVL 
Core, for which support is currently not finished. 

Cern.


-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/Llbidjv--3-1%40tuta.io.

[Machinekit] Which kernel is the fastest running Machinekit on BBB?

[Simon S]

Hi!

My old machinekit installation runs on a BBB under debian jessie with a 
xenomai kernel.
I start the axis gui via an SSH session using indirect OpenGL rendering.
For normal CAM jobs this is reasonable fast and the gui is responsive.
Only huge jobs with e.g. 3D cam operations take some time to load but then 
they are fine as well.
I want to switch to a more recent version because I can not get the 
XHC-HB04 pendant working under jessie
(see https://github.com/machinekit/machinekit-hal/issues/209)

So I  configured a second BBB using debian stretch.
I tested various kernels but all seem to be way slower than the old kernel
coming with my debian jessie image.
Some kernels export the wrong cpu frequency settings and do not use the 
maximum clock but even those who do are still slow.
Opening a very basic CAM jobs in axis loads for a minute or more.

Something seems wrong... When I open a second console via ssh
while axis is running the console is laggy and unresponsive as well.

Any hints?

Regards,
Simon

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/7f7fdd0d-2447-4ad4-92dd-f182aefb96bb%40googlegroups.com.