Upgraded to 2.7.13 -- W T F --

Now over one hour and latency-histogram is running OK.
Will leave overnight and see if it freezes up or not,results in the morning here.

I think the system goes to deep sleep if no activity is going on.

tecno wrote:

Here are my errors I get, note this is only now when PC is connected in lathe to my 7i76e+7i85s

modprobe: ERROR: could not insert 'ip_tables': Operation not permitted
iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
hm2_eth: ERROR: Failed to create iptables chain hm2-eth-rules-outputhm2_eth: WARNING: Unable to restrict other access to the hm2-eth device.
This means that other software using the same network interface can violate
realtime guarantees.  See hm2_eth(9) for more information.

modprobe: ERROR: could not insert 'ip_tables': Operation not permitted
iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
hm2_eth: ERROR: Failed to execute '/sbin/iptables -A hm2-eth-rules-output -o enp3s0 -p icmp -j DROP'

I did this
forum.linuxcnc.org/38-general-linuxcnc-q...xcnc?start=10#112691

Are you using the cstate option mentioned earlier in this thread ? That might be the go, but I'm pretty sure the kernel was configured not to go into deep sleep.

Look thru the BIOS options as well.

isolcpus=2,3 intel_idle.max_cstate=1 i915.enable_rc6=0 i915.enable_dc=0

Will have a look tomorrow, bedtime here.

Good morning!
Latency-histogram was still running this morning after uptime of over 44000 seconds.

So it looks like 'no activity' = goes to deep sleep. Anyhow that is not a problem as long as system is ticking when LCNC is running, can be finished with one job and I do not want to loose my position even after several hours break to continue. Let it be a stop for toolchange or finished run.

No freezing so far with LCNC running, so it seems to be OK.

Now time to setup Gmoccapy so it functions as it supposed too.

Noticed that the gmoccapy setup is somewhat fucked-up. Take a look at scale_max_velocity value!
I can assure you that this scared the shit out of me when I tested to run 'lathe-pawn.ngc'


Maybe somebody ought to have a look at this as it is straight out of the box! It should be 1 not 1000!

I get some error messages still and would like to solve these if possible.



Is this message saying that

Running HAL shutdown script
task: 45326 cycles, min=0.000019, max=0.127551, avg=0.010016, 1 latency excursions (> 10x expected cycle time of 0.010000s)

P = 1000.0 and SERVO_PERIOD = 1000000 are set too short so P=1500 and SERVO_PERIOD = 1500000 could solve this issue?

I can run ngc files and get no error during running lathe_pawn.ngc, I can override feed to 200% = no problems.

P=1500 and SERVO_PERIOD = 1500000 seems to be working = no more pop up error message on screen.

Received my Gigabyt GB-BXBT-1900 today and installed Mint 18.3

Following 2 lines Error file not found or something like that
sudo apt-get install hostmot2-firmware-all mesaflash
sudo apt install glade3_3.8.6-1_amd64.deb >>>>>>>>>>>>>>>>> solved double click on package!

Running LCNC in SIM faults like this

bengt@CombiMll ~ $ linuxcnc
LINUXCNC - 2.7.14
Machine configuration directory is '/home/bengt/linuxcnc/configs/sim.axis'
Machine configuration file is 'lathe.ini'
Starting LinuxCNC...
Found file(lib): /usr/share/linuxcnc/hallib/core_sim.hal
Note: Using POSIX realtime
Found file(lib): /usr/share/linuxcnc/hallib/axis_manualtoolchange.hal
Found file(lib): /usr/share/linuxcnc/hallib/simulated_home.hal
Found file(lib): /usr/share/linuxcnc/hallib/lathe.hal
task: main loop took 0.012027 seconds
task: main loop took 0.012469 seconds
task: main loop took 0.021057 seconds
Unexpected realtime delay on task 0
This Message will only display once per session.
Run the Latency Test and resolve before continuing.
Unexpected realtime delay on task 0
This Message will only display once per session.
Run the Latency Test and resolve before continuing.

Did a short latency test and numbers are not good running all 4 cores = a bit disappointing.

Not good as you can see.