Advanced Search

As usual, posting your hal and ini files will help to diagnose the issue.

First of all thanks for the great work. 

is it just me or is the link on the website wrong?
www.linuxcnc.org/iso/rpi-5-debian-bookwo...23-11-17-1520.img.xz
it say: LinuxCNC 2.9.2
but when I start it it say 2.9.1 

I thought I had an older one so I reinstalled today and still the same. 
Can I upgrade linuxCNC and GMOCCAPY?
i had some issues with GMOCCAPY now compared to when I was running the PI4 that I installed years ago.
One issue I had was when I pressed the aport button during a probing script, it did not stop but the GUI changed. 
I will try to reproduce. 
I copied my old config. Can that be the issue? I thought you could 
github.com/swepeter/PrintNC
Thanks all

Yes it does.
Use a DVM to measure the voltage at the drive inputs.
Are the stepper motors locked when powered on?
Is Enable wired to the drives? If yes, disconnect it till you get things working.
And do the tests with a finished configuration running LinuxCNC, not from wizards.

Are the encoders wired to drive/board with shielded cable?
Is the shielding grounded on the drive/board side?
What is the output voltage on the encoder pins?

Maybe a stupid question but, does a 7i96s board come pre-loaded with basic firmware?  I don't recall loading firmware on my previous 7i96.

I have a basic Axis config with one rotary axis on Step-0.

I can identify the board with the Mesa CT utility, just can't drive my stepper motor, as if Pul and Dir signal are not being sent. 

I would post your hal/ini files
runaway with FF2 doesn't make any sense
 

Hello folks I'm currently in the process of setting up Probe Basic.
My problem is that the emergency stop doesn't work it is always on.
When I try to reset the emergency stop, Probe Basic hangs for 5 seconds nothing happens after that. I've tried everything possible but I just can't get anywhere.

There is no external emergency stop linked

Does somebody has any idea. thank you in advance

I checked once more with P=1 and all other PID params = 0. Motor is soft but after half a turn it starts to resist and moves slightly back when released. Tried both ways.

Removed command-deriv and feedback-deriv connections.

Checked INI file - servothread is running at 2kHz.

About tuning under load - yes, I put the belt back on, motor is connected to machine. That is why I am nervous about this behavior.

The result I am getting now is that with jogging at 1m/min HalScope shows ferror of approximately 1 mm. I move in relatively small distances 10-20 mm, because overall travel is 150 mm (Z axis on Biesse machines usually have small distance of travel). And occasionaly at the start of the jog move I get runaway. I have made it to 3rd step of trying to add FF2. And I am trying really small values (P=1 and D=1.2, so I tried FF2=0.002). The feeling is that too much of FF2 cause the runaway. Does it make sense? With FF2=0 when adjusting D term I could make more than 10 jog moves and not get a runaway. Add FF2 = 0.01 and immediate runaway. Change to FF2=0.0001 and was fine. FF2=0.002 and immediate runaway. Could be pure coincidence, I have no idea.

I have set ferror limit to 5 mm and connected pid.2.enable to halui.machine.is-on so it gets disabled when ferror limit is tripped so I have managed to avoid any damage.

Any idea where to look? Should I search for flashdrive to get the config files and post them here?

stable is locked for the moment, any fixes will be done in the develop branch which pulls from the latest main branch when building, so try there for your updates. we are going to leave stable as is for several more weeks to give everyone a chance to succesully migrate to the develop branch on their own time line since a transition requires some heavy configuration work and we do not want to interupt anyones work flow unexpectedly.

If you get 0V/5V at the Mesa terminals, there is nothing wrong with Mesa nor LinuxCNC, so check the wiring and the controller, usually reversed dir pins on controller connector or wrong pin.
Sherline used some strange pin setup ...

Another wrench in the machine:
Mesa 7i73, RS422 use differential signaling, pretty sure there is no serial that can do that, but still could be done using some line drivers, that implies using intermediary boards, lots of wiring mess, ...
Normal serial ports do 115K as Cornholio mentined, ESP32 can do much more through USB to serial using it's built in whatever it uses.
Did anyone check if Mesa 7i73 can be made to communicate at lower speeds?
Aaaand arduino jumps in...
Do you have a 7i93 mentioned above?
Forgot what 7i93 does, so i'll go hide under a rock.

when we say updated we mean a serious update to be brought to compatibility with the latest changes in QtPyVCP, it would likely take a good bit. It is a bit too much to maintain both versions as they are completey distinct in their update requirements, really need a full time person to maintain it but no one seems to use it that wants to take on the responsibility unfortunately.

@Arciera,

From the document i found interesting line :
G1 X0 Y0 Z0 I-0.5 J0.5
K0.7071. For a properly defined vector

They use I,J,K for vector. But for G2, G3 that is not a valid gcode input. Preferr to use AB for the vector and use
C for the spindle orientation.

--
Basicly when using external rotary table, we could use this as axis u,v,w.
Where u=rotation around x, v=rotation around y, and w=rotary table clamp symetric axis.

Then we have a xyz, abc, uvw machine, 6 axis for tool, 3 axis for extern rotary table.

But this then is a single machine config that has valid kinematics for a few configurations like : xyz router,
xyz router + abc head. xyz router + abc head and a uvw rotary table.

So all other configurations, like xyzab, xyzac, xyza, etc need a different software approach.
And i think not all of these variants can use tooldirection optimalisation. Like xyza, where a is secondaire z axis.

So if i add selectors to the program config section :
1. xyzab
2. xyabc
3. xyz
4. xyza
5 xyzabc
6 xyzabcuvw

Then it should use correspondenting c++ function to translate gcode into the proper tcp, and other axis.
Like choosing kinematics.

What you think?







 

if you have a working configuration in axis, use the sim config ini file for probe_basic as a comparison for the bits and pieces required in probe basic.  I wish there was a better solution and maybe in the future we can sort out a more streamlined method, but it isn't too terribly difficult to get it going once you have a feel for linuxcnc'c configurations and how they work.  i need to make a new doc for the development version that recently released, but ive been completely covered with work.  in the interim just post up any questions here and we will see if we can get you fixed up.  and if you wouldn't mind noting anything along the way to perhaps help others that would be fantastic!

thanks,

Chris

  So hier einmal die gewünschte datei hoffentlich die richtige 

Ich habe keine qtvcpscreens

Habe aber paar verschiedene sim ausprobiert und nur bei plasmac tritt dieses problem auf.