Advanced Search

Fehlermeldung?
Und mese die 5V an die Mesa karte, soll 4.75-5.25V sein

Quick question hopefully, I'm setting up my router with closed loop to the controller, apart from getting the scale right it's all working, my question is when you setup the scale in the pwm/dir config, it sets up the axis "scale in" to that, but leaves the scale out value at 1 or zero (can't remember exactly). At this value the axis will run away similar to having the encoder wires around the wrong way.

I can set it using the machine calibrate window within Linuxcnc but it gets overwritten every time setup is run. Then if you forget about it and an axis is close to end of travel, bad things can happen. 

I've most likely just missed where to put in the scale out value but I can't seem to find it.

Cheers.
Russell.

Hallo ich habe eine Mesa 7i96s und Linuxcnc 2.9.4Ich habe eine Installation Mesact  gemacht mit einbinden 3 Servos, 3 Endschalter, 1 Not-Aus, und WKZ Sensor. Ausgänge : Spindel out 0, out1 und RelaysWenn ich jetzt Linuxcnc starte , kann ich die die Maschine Einschalten bekomme ich eine Fehlermeldung und das Ehternet ist unterbrochen.
Auf der 7i76s blinkt LED init Rot, nur durch Neustarten der Hardware ist der Fehler weg.Meine Maschine ist mit 10.10.10.10 mit meiner Workstation verbunden.  

That's the easiest way, I think I mentioned that earlier, I like Network Manager as I can turn the wifi off whilst running a job.

If I have to use Windows it always feels like swimming against the current in a river of molasses

I installed network manager and both connections, 7i80 and internet are fine.

sorry, my bad, you should remove that -q in the command which makes your ping output quiet. try this:
sudo chrt 99 ping -i 0.001 10.10.10.10 -c 1800000 | grep -v time=0.

btw. are you still getting that error finishing read?

You could use an ngc remap to create a gcode for setting numbered parameters to the required offset values and another ngc remap to read the parameters and set one of the built in offset system. Arrange the parameters in blocks of 10, that way a 'p' word value can easily be used to reference which block to read/store the (x,y,z,..) offset values from/to.

Maybe you can write your own macro to load the offsets from a file

Use python to remap an unused Gcode to get the required offset values from a file and set one of the nine built in offset systems. Takes a bit more effort than the above solution.

I've wondered the same thing a few times. Wouldn't mind digging into code if no one has a solution.

thank you, that is very helpful.
By running "sudo lspci -v", I could confirm that the right driver is used (see attachment).

 

But when I try to run the modified ping command, the result is just the same as before. It doesnt filter out any packets over 1ms... again, see screenshot.
I guess the command has to be modified a bit...
 
Regards and thank you
Sebastian

I guess we had a power spike - I know we lost power because the computer had rebooted. But the message was about not being able to find a boot device. After MUCH futzing around - I THINK I may have had damaged my primary SATA port (weird). I could boot the system from a USB and view the drive contents, but I couldn't figure out how to rebuild the boot drive to boot it. I had made backups of the config files 'just in case' (I'm usually a much bigger risk taker and don't bother) and managed to pull them off the drive before I proceeded with a 'nuke and a repave'. When I couldn't get a new system laid down - I thought it WAS the hard drive then. I had an SSD kicking around that I put in and... same problem. That lead me to try a different SATA port and voila - new system installed. 

Within this new SSD based system I did the latency test (I was seeing a number like 71,000?) and then ran StepConf just to create the files. Once I had the files in place - I overwrote them with my backups and Bob's yer Uncle - my system was up and running. EXCEPT - when I try the fast move using the SHIFT key - all 3 axes move a random, short distance and then there is a sound like it's moving - but it's not. 

I tried to modify the MAX_ACCELERATION  in both the [AXOIS_X] and the [JOINT 0] sections of the .ini. But changing those resulted in a non-start on LinuxCNC. Even as I type this - I THINK the issue might be the stepper timing and not the acceleration. But I'm hoping that the brain trust on LinuxCNC here in the forums can point me in the right direction.

I've searching the online documentation and the 362 page Integrators manual - but there is really SO much underlying knowledge of the workings of Steppers, Servos and 'integration' terminology that just baffles me. I'm still plugging away!

Thanks in advance...

I tested your attached files (including install attached cia402, cia402_homecomp files, successfully) in current LinuxCNC.
with LC10E - EEPROM version V1.04

Power on is OK, Jog each axis is OK,
But X axis cannot stop when I pressed [Home All] button.

In Halshow window, cia402.0.opmode = 8 always.

What am I missing ?
Does anyone know any update for it ?

after installing the driver run this to check that it is the right one being used:
sudo lspci -v
under Realtek controller check Kernel driver in use, it should be r8168. (see attached screenshot)

to avoid problems i suggest to blacklist the r6169 driver completely in grub by adding: modprobe.blacklist=r8169

or, since your pc looks similar to mine you can add the whole my line to /etc/default/grub which through trial and error i found the most stable:

GRUB_CMDLINE_LINUX="irqaffinity=0-1 kthread_cpus=0-1 isolcpus=domain,managed_irq,2-3 rcu_nocb_poll pcie_aspm=off r8168.aspm=0 r8168.eee_enable=0 modprobe.blacklist=r8169,mei_txe"

don't worry it will not kill your pc  it just rebalance your cores to do different things. 

dont forget to run "sudo update-grub" to update grub configuration otherwise you won't see any changes after restart.

also check sudo dmesg for any errors during boot.

having 1.2ms ping once in a blue moon won't kill you. i suggest to add "grep -v time=0." to see how many actual pings you got over 1ms.

i normally run something like this:

sudo chrt 99 ping -i 0.001 -q 10.10.10.10 -c 1800000 | grep -v time=0. 

this will run ping for 30 minutes with 1ms pings and only show you the pings that took longer then 0.999 ms.

if you see only one or two 1.2 ms in 30 minutes it is not a problem, 8ms is super bad though. 

have fun!

I wonder how the were inserted? Thank You , I will try it tommorrow.

[TRAJ}Axis XAxis YDelete .ini from those lines.