Advanced Search

I haven't wired them up yet, but the fuse issue also happened when the power amplifiers were connected.

I would venture a guess at wrong wiring, so first check if analog grounds are wired correctly, from your explanation this seems to be the reason.

forum.linuxcnc.org/10-advanced-configura...to-example-mesa-7i77

The lower LED is slightly dim. I adjusted the voltage; it was 4.6V, now it's 5.1V. When I move the axis, the fuse trips immediately, but the wire only deforms slightly more. Is 1A too low, or is the Mesa fuse defective?

If I remember correctly, I've checked this back then and the the column R showed 0.0000 for G54 and other offsets. Clearing and saving the offsets did not help. Only G10 L2 P1 R0 resolved the issue. But since then, everything works fine. I will let you know, in case it happens again.

Here is a version, which creates a surfacemap.yml so the parameters persist throughout sessions. The variables like probe fast feed rate are still independent from the standard PB probing parameters. Maybe this can be aligned in a future version of this interface.

Hello everyone!

I am struggling with the implementation of my servo drives. I set up the pncconf wizard and did some adjustments, checked the Output Offset and scaled the Encoder. Now I want to start the machine an make some PID tuning, but if i toggle the Machine Power Button the Servos directly starts to turn. After a few secs i got an following error (make sens) and the Servos stops.

What is wrong in my config? Is this an Servo Controller Problem or an Mesa Setup Problem? What should i do next?

I am using the Linux CNC (2.9.4), a MESA 7I92TM connected via Ethernet and a 7i77 at Port P2 for the Servo Drive Control. My Servo Drives (Yaskawa SGDV-7R6A01A) run with +-10V and Encoder Signal to the Linux CNC.

Attached you can find some pictures and files of my config.
Thanks a lot and all the best wishes from Germany
JanCNC

active setup is faar miles in front of everything... it is very interesting stuff 

please reupdate repo /configs with scurve_example.hal and .ini files config for easy setup for other users as it was 1.1.2026 for testing ...

 

Most of my testing was on 5 axis, need some help with the performance on a cloud of points, but it is not half bad in my testing, I compared with a commercial 6 axis robot on same point cloud, and well maybe we are half the way there, which is not too bad IMO

多谢杨阳

thanks a lot, Yang Yang!

Testing is at different architectures(because there is some differences at hardware level and in instruction set) with different G code types... It will influence calculations and produce jitter 

Most of us is running 3axis therefore i started there.. 

Then I will move to 6axis setup and do same for multiaxis movement

Then I will move to hardware benchtop setup and then to real iron... 

I am not in the shop and I can not share more or any code.. then later

is there this folder?
~/linuxcnc/nc_files/examples/remap_lib/python-stdglue/python

does that folder have these files?
remap.py
toplevel.py

is this link valid in that folder?
stdglue.py

is there this path?
~/linuxcnc/nc_files/examples/remap-subroutines/qt_auto_probe_tool.ngc

LinuxCNC 2.94
Qt_dragon_hd

Unable to change tools in QT Dragon using the command T2 M6 or any tool number. Debug shows the following

Ran the auto tool sim and that works, compared the .ini and .hal files to find no differences. Thought it wasnt getting to the qt_auto_probe_tool.ngc found in "/usr/share/linuxcnc/ncfiles/remap-subroutines:\"  so I added it to the subroutines which didnt work either

Thank you, by the way all coding was done by 杨阳 aka YangYang, most of the credits go to him, not sure what account he has here on the forum, I did the on field testing feedback, and I now ported to master.
Excited to see your testing results, if you show me your testing methods, I will try to reproduce on my end.

Finally i found the reason for preview disappearing sometimes, while program execution. I was watching call level, current subroutine depth, and preview only works with value 0, not in a subroutine.

 

in your config folder there will be a set of folders: qtvcp/screens/qtdragon_hd/
in that last folder add the file 'qtdragon_hd_handler.py' that I have uploaded here.

It will give you the pins you asked for.

The developed version will be in master branch.
as for 2.9 - I think 2.9.8 was just released.

If you are using an installed version, it should be update-able.