Advanced Search

Hi
Now I use Linuxcnc V.2.9.4

I have a problem when Post G-code from Fusion360
If I post 1 post 1 command (Adaptive clearing) it's No jerk
but When I post  3 command in Gcode  
1. Adaptive clearing (tool 16)  Not jerk
2. Face  (tool 15)  Not jerk
3. Adaptive clearing (tool 16) Jerking

Step 3 my machine will jerk  when entering a curve and Velocity move slow down to 10-30 % feed , And will back to 100% speed when back to linear move .

My post I use
G64
G64 with P
G64 with PQ
Same problem can't solved .


 


I try
Post Gcode only Step 3. Adaptive clearing  it's not have a problem can run full speed and machine not jerk 

How I can fix this problem ?

Thank you
Asis

meister wrote:

never trired OpenOCD, but you can send me the error mesage of the openfpgaloader.

with openocd you should make sure that it is written to the flash and not just to the ram, otherwise everything will be gone again after a restart

You can see whether it has worked by the flashing LED

btw, the default ip is '192.168.10.194'

the w5500 module has a little power led on the bottom, there is no jumper to power on/off this module.


not realy shure what you mean with the mapping,

the bob pins are mapped 1:1, if you need P17 (relais) on the BOB, you can use 'LEFT:P17' in your config.

 

if your BOB is connected to the other connector on the right, then you need to use 'RIGHT:P17'

 
So for a standard 3 axis mill, is the below scheme for wiring somewhat right.  I have no idea how to make a config for a lathe Though!  The second image has a funny output as marked

Guten Morgen Peter, 

vielen Dank für deine Hilfe

beim booten erhalte ich folgende Meldung

(1 of 2) Job logrotate.service/start running (43s / no limit)
(2 of 2) Job ifupdown-pre.service/start running (45s / 3min)

Den von dir vorgeschlagenen Befehl habe ich ausgeführt einmal direkt nach dem booten ausgeführt. Sobald der Fehler nochmals auftritt werde ich auch diese Log Datei hochladen. 

Den Inhalt der Log kann ich leider nicht interpretieren. Auf was muss man achten? 
Am Ende sind die zuletzt aufgetretenen Operationen? 

Im "normalen" Betrieb habe ich folgende tmax Werte (Maschine läuft schon eine Weile)

cnc@cnc:~$ halcmd show param *.tmax
Parameters:
Owner   Type  Dir         Value  Name
    36  s32   RW              0  hm2_7i96s.0.read-request.tmax
    36  s32   RW        2563480  hm2_7i96s.0.read.tmax
    36  s32   RW         529484  hm2_7i96s.0.write.tmax
    29  s32   RW         134036  motion-command-handler.tmax
    29  s32   RW         166416  motion-controller.tmax
    39  s32   RW          27492  pid.s.do-pid-calcs.tmax
    39  s32   RW          29268  pid.x.do-pid-calcs.tmax
    39  s32   RW          28128  pid.x2.do-pid-calcs.tmax
    39  s32   RW          27220  pid.y.do-pid-calcs.tmax
    39  s32   RW          26944  pid.z.do-pid-calcs.tmax
    30  s32   RW        2727116  servo-thread.tmax
 

Ich habe noch eine neue SSD gekauft um eine unabhängige Neuinstallation durchführen zu können. Vielleicht liegt der Fehler auch irgendwo in einer der vielen Anpassungen? 

Grüße
Erwin 
 

I understand this is the process of installing qtpyvcp and the Basic probe. In my case, it all works. Probably, I did not correctly identify the problem! I also correctly installed qtdesigner5 with linuxcnc widgets. But the problem is that the folder with the installed (vcp template) is not correctly configured for further editing! That is, I want to try to make my own graphical interface. I tried to create a GUI through flex gui, which was created by John, and it is very cool and quite clear. But I also want to study and try to create my GUI through qtpyvcp, but I encountered the problem that I described above!
Or you can start creating your own GUI without this step: www.qtpyvcp.com/tutorials/basic_vcp/basic_vcp_01.html

Was thinking about this today.......Very interested

Hi Andy,

Output of dpkg --list | grep libgpiod
I did a quick load of hal_gpio, didn't run a config, but it loads ok.
spix works fine even with my cobbled together 7c81 clone

Linuxcnc complains about /usr/bin/kill not being there but it's under /bin/kill which might have to do with debian having /bin /sbin & /lib being links to /usr/bin /usr/sbin & /usr/lib/ and Devuan not taking that road.

I'm actually Devuan to make this post.

I've only made a RPi5 image ATM but would you like an RPi4 image made ?

I am liking the look of this board. Did you do this in easyeda?

Suggestion, add the rpi 40pin header. Aside from being able to add stuff rpi side, I find it valuable for debugging the MCU/FPGA side of the board using a regular rpi without having to keep removing a cm module and you can use it as a backup incase you damage the 100pin hirose connectors or theres another RPi/chip shortage

Thanks! I'll try!

Will keep the smart serial cards in mind in the future. Thank you Andy.

Sorry, yes, I replaced the qtaxis.ui in my configuration folder/qtvcp/screens/qtaxis.ui (new), and then what must I do?.

Hi PCW,

Noted. Will look to the pncconf in depth next week. I tried the pncconf yesterday. I got to the point where you choose which mesa boards I am using. From gathering in the internet, i should be using the 5i25 since 6i25 is not in linuxcnc and 7i77 x 2 i guess...

As for the Analog I/O thank you for the clarification. So instead of ENAn+ and ENAn-, I should connect the servo drives to the 7i77's AOUTn and respective GND.

Thank you for your assistance.

UrKibin wrote:

As I have already purchased the Plug-N-Go Kit (7i77 + 6i25) from Mesa, I would like to use them.

If you already have the cards, then definitely stick with them, they will work fine.

You can expand to really rather a lot of IO by adding smart serial cards, if you need to.

You don't replace the original ui file, though that will work.
you put it in YOUR CONFIGURATION FOLDER/qtvcp/screens/qtaxis/qtaxis.ui
Qtvcp will see it there and use it instead of the original/

Normally the basic configuration is created by one of the two configuration utilities:
pncconf or MesaCT. These are GUI programs where you enter the intended interface hardware and
basic machine specifications (dimensions, encoder scaling etc) and I/O connections
(limit/home switches spindle controls etc)

Note that the analog out pins are AOUTn. The ENAn+ and ENAn- pins are a switch to enable the
drives (on when enabled)