Advanced Search

Hallo zusammen, ich schon wieder.
Nachdem PCW mich dieser Tage mit dem Start meiner Linuxcnc 2.9 Config einer 7i96S gerettet hat, dass die überhaupt startet, der nächste Fehler:
Ich habe einen Mini PC namens Lenovo ThinkCentre Intel(R) mit core-i5-3470T CPU @ 2.90GHz und 8GB RAM. Der Latency Test zeigte max Servo Thread Werte um die 30.000, max um 1.000.000, (s.Foto)  ich habe den Wert im PnCconf Wizard auf 1.200.000 gestellt, dann auf 1.500.000 um auf Nr. Sicher zu sein. Leider bekomme ich nach Fertgigstellung meiner Config für eine 7i96S immer die Start Fehlermeldung dass es Probleme mit der Latency geben soll. Ist mein eingestellter Wert jetzt zu hoch oder muss ich noch höher gehen? Ich verstehe den Fehler nicht.
(Den XHC-WHB Fehler bitte ignorieren das ist schon gelöst)

Vielen Dank für Eure Hinweise!
Grüße, Arno

 

Endian, the issue you're experiencing with

dpkg: error processing package ethercat-dkms (--configure):
 installed ethercat-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of ethercat-master:
 ethercat-master depends on ethercat-dkms; however:
  Package ethercat-dkms is not configured yet.

Is because the ethercat-dkms package was recently broken it appears (July 26th)
The deb file is missing the fake_lib folder inside, but the Makefile/configure scripts are expecting it to still exist.
You can see this in the `/var/lib/dkms/ethercat-dkms/1.6.1/build/make.log`

I had to manually download the fake_lib from the origin `gitlab.com/etherlab.org/ethercat`
I then had to move it into `/var/lib/dkms/ethercat-dkms/1.6.1/source`, run `sudo make`, then run `sudo dpkg --configure ethercat-dkms` to forcibly re-configure the dkms package.

I then ran the standard linuxcnc-ethercat install and it no longer complained about the DKMS package.

For a more proper fix, you'll need to wait for the package maintainer to release a new package version without the issue.

Qtdragon uses a derivative of Verser's probe routines. It has diverged a lot code wise.

The tool probing measure routines are disabled in 2.9 (enabled in master).
The routines are there but I'm not sure if they are right - I'm sure master got more work done.

It's possible to enable them with a simple python file patch, but you would need to test very carefully. If you are interested in that, please open a subject in Qtvcp forum.

Maybe Verser can help us get the code better in the linuxcnc version.

Cant do this anymore bye all wrote:

Considering this is the second thread regarding the same issue......

Nope, it is the 5'th topic
forum.linuxcnc.org/forum/search?searchus...ritant&childforums=1

Considering this is the second thread regarding the same issue......

Honestly the topic heading has no relation to the issue at hand.

Having read the previous topics of the OP plenty have tried to answer, so help has been at hand. With a bit of levity thrown in.

You are not helping yourself.
Go back and read your posts, then come back and tell us they are OK.
You can not, as they are from extremely short with absolutely no information to go on, to plain ignoring what info we asked you to provide, to refusing to test what was proposed to you.

Hi, I am not getting any help on this forum

Well frankly, as somebody who has tried to help you several times on this very forum I find this a little hard to take. Instead of answering questions about your setup or following the advice you're given you just go and open a new topic asking the same question all over again. It's like yelling into a black hole.
I'm going to give this one more shot in the dark and then I'm done:

in your hal file change this:
to this:

waukeenahBob wrote:

Tried 0xd800 no change in behavior.... I hear the relay click...not sure why that is happening

OK that should confirm it is working, so set the base period to 100000 and step time and space to 10000 and try to jog the machine.

How to fix timeout error during uploading config for nvem board?
Ping 10.10.10.10 went OK 

Hi, I am not getting any help on this forum so I thought someone may have had this issue and hopefully found a cure.

The problem:
My new install seems okay but LinuxCNC will not turn the spindle (Bosch router) on. The info for my Probotix Unity controller says pin 14 is the spindle.
I select his and/or invert and it does not work and many others. I have attached the ini and hal files. The date on the file is when I started on this installation, pretty much full time. Right now I have it plugged into a power bar and I flip on and off.

I had a problem where the axis would not move. I was told the change the table size and it worked. So somehow the table size setting are interconnected with the ability to move.

Thanks
 

As far as I understand he has to comment out this line:

source /etc/network/interfaces.d/*

Best regards
Julian

As far as Gcode goes, it was done in conversational, long gone.I am not sure which version I am running but it is probably at least 2yr old. BTW I would like to thank all who have been a part of the plasmac interface development, I came from Mach3 to Plasmac, it was like going from riding an oxcart to driving a Mercedes. It is so easy to run and to learn, in the old mach3 days I would have a random torch dive and estop, sometimes wading thru thousands of lines of gcode to figure out where to restart, now I rarely ever have a thc issue and if there is a problem its easy as pushing rewind. Plus a Bucket list of other things that are way superiour. I have several miles of cutting logged on by now and very few issues. Thanks again.

Hi all, hi scotta,
I reflashed my EC500 with the newest firmware to check if the NVMPG now works.
After reflashing LinuxCNC doesn't connect anymore. The EC500 doesn't respond to pings either.
I wanted to erase the EC500 to reflash it from new, but erase doesn't work anymore.
Issuing this command:
pyocd erase --target mimxrt1050_quadspi --mass
returns this error message:
0000718 C No ACK received [__main__]
I use a DAP Link btw.

I flashed the newest firmware to a second EC500, and now this one seems to bricked also.
I can't erase nor re-flash both of them anymore.
How can I un-brick them?

regards, hanskuster
 

Hi,
Have some issue, cant make Probe height for current tool / Probe height and dia of the current tool working
all other functions works, but that 2 probing remain disabled

versaprobe is set and working
pi4 / linuxcnc 2.9.1 / qtdragonhd
Tool measure enabled
M6 remap done
toolsetter xyz set, speed, dia, rev speed seet

Hello,
these white connectors are to nonnect the steppers via such cables who fit in
by the way, did you got the endswitches/ref switches to work? i have now the second board and the signal is not coming through to linuxcnc, i have connected the 12V
do i need to use the GNDon the input pin blocks for the sensors somehow instead of the gnd i use for the step/dir signals?

Georg