Hi Tim,
I did quick test Stretch + Axis, just turn on without run the milling with
default gcode.
a) MachineKit - memory leakage
b) LinuxCNC - no leakage
Regards,
KL Chin
On Tuesday, 14 August 2018 00:09:23 UTC+8, KL Chin wrote:
>
> Hi Tim,
>
> I tested 2 version.
>
Hi Tim,
FYI, the Stretch + Axis + MK memory leak is about 1MByte per min.
Not sure what the differents for Axis under LinuxCNC and MachineKit.
Regards,
KL Chin
On Tuesday, 14 August 2018 10:02:24 UTC+8, KL Chin wrote:
>
> Hi Tim,
>
> I did quick test Stretch + Axis, just turn on
, 15, 16, 18, 22, 37, 13 };
Can you verify it
rpi2_pins 38, 40, 15, 16 should be 38, 15, 40, 16
Regards,
KL Chin
On Monday, 18 June 2018 00:06:02 UTC+8, Timothy March wrote:
>
> Having trouble getting gipo's to work can get all to show up as outputs
> but when I load com
Hi Tim,
I had using stretch for about 12hrs already.
I do not experience memory leak. Without zooming and hence the CPU about
70+%.
Could it be leakage during high CPU usage or/and large GCode file?
Regards,
KL Chin
On Sunday, 12 August 2018 21:34:42 UTC+8, Timothy March wrote:
>
>
steps, cannot return to origin location after
complete milling (G00 X0.000 Y0.000 z10.000)
it took about 1.45 hrs
Regards,
KL Chin
On Thursday, 9 August 2018 22:04:14 UTC+8, Timothy March wrote:
>
> Thank you KL Chin
>
> Tim
>
--
website: http://www.machineki
Hi Tim,
I tested 2 version.
a) RealtimePi + MachineKit (ver 0.1)
b) RPi Stretch + LinuxCNC (2.8.1-Pre)
So far, both no memory leakage.
Maybe I will try without running the code.
Regards,
KL chin
On Monday, 13 August 2018 21:04:10 UTC+8, Timothy March wrote:
>
> To KL Chin
> I j
,
Under RealtimePi I can get the stepper motor back to origin after complete,
still testing.
But not under RPi Stretch (Tested LinuxCNC and Machinekit), even with
6-8mm/min velocity.
Will try to with Jessie soon.
Regards,
KL Chin
On Sunday, 12 August 2018 03:43:23 UTC+8, Timothy March wrote
Hi Tomp,
Here the edited hal_gpio.c, it required 2 files from MachineKit, copy it to
linuxcnc/src/hal/drivers folder.
then u can start build it.
Pls. check the Makefile also, search for hal_gpio.
Regards,
KL Chin
On Friday, 17 August 2018 10:03:25 UTC+8, TJoseph Powderly wrote:
>
>
Hi Tim,
Ya. I think that the reason. I had added this param for my last build.
Regards.
KL Chin.
On Tuesday, 28 August 2018 18:40:31 UTC+8, Timothy March wrote:
>
> KL Chin the cmdline.txt isolcpus=2,3 is what limits cores to 0,1 if only
> using two cores latency will be lowe
Hi Tim,
TQVM.. With latency-histogram —nobase, the latency look good under
LinuxCNC.
Regards,
KL Chin
On Wednesday, 29 August 2018 01:02:30 UTC+8, Timothy March wrote:
>
> KL Chin I do believe the difference between latency test are LinuxCnc has
> both Base thread and Servo threa
change few lines of the
hal_gpio.c.
Regards,
KL Chin
On Tuesday, 28 August 2018 03:42:31 UTC+8, Timothy March wrote:
>
> KL Chin why are you using LinuxCnc instead of Machinekit? The hal_gipo
> only works with Machinekit there is no gipo driver for LinuxCnc.
>
> Tim
>
OK. Will try it.
BTW, other then Axis memory leakage issue ans more Lite version,
what other reasons to use Jessie to build RT image?
As I still new to Linux environment.
Regards,
KL Chin
On Tuesday, 28 August 2018 03:36:08 UTC+8, Timothy March wrote:
>
> KL Chin also start with Jessi
ome minus value.
Suddenly somehow after running few time of LinuxCNC the system not able to
shutdown
and finally the whole SD image cannot boot-up and had to rebuild.
Regards,
KL Chin
On Sunday, 29 July 2018 08:25:13 UTC+8, Timothy March wrote:
>
>
> Mung Kie said, "They messag
Hi Schooner
TQVM. With the "latency-test 50us 1m" the result show much accurate
results also with glxgear.
Regards,
KL Chin
On Wednesday, 29 August 2018 16:37:17 UTC+8, Schooner wrote:
>
> If you run a dummy base thread, but don't actually connect anything to it,
> it
14 matches
Mail list logo
