Advanced Search

I found my mistake. I was editing the wrong file. . . Please excuse me as I leave.

Thank you very much for your professional responses! I’ve decided to order another board along with a daughter card now to avoid a similar failure in the future. I’ll slowly work on repairing the current board, it will serve as a spare one, or I might sell it later. It seems that delivery across Europe will be quite fast using the link you provided. I’ll update you later on how my board recovery story ends.

In your case, you should have gotten a servo/stepper with brake for Z axis.
It is a hardware feature, so software can not help, but if the loop is closed in LinuxCNC at least it will know the position.
PCW's idea with enabling fast after fault and if loop is closed in LinuxCNC is very good.
As for your question, drive fault will disable the motor in the drive, so nothing LinuxCNC can do about it (except above), and so will LinuxCNC disable everything when it gets a fault error.

auto(int[, int]) run, step, pause or resume a program.

This is how I open then run a program in Flex GUI

github.com/jethornton/flexgui/blob/maste...exgui/actions.py#L13

github.com/jethornton/flexgui/blob/maste...xgui/actions.py#L296

assuming you're using a probe you can store the probe results in a file.

JT

I have built my CNC just this month so I have only conducted test cuts, and have not gotten a driver error while machining yet, i just thought such a setup would make more sense if it did happen.

How are errors on drivers on CNC mills usually set up.

I am using Motor Driver CL-HSS860 driver with nema 34 stepper motor.

unknown wrote:

Maybe if I stuck with Mach3 I wouldn't spend so much money, bugger I said the quiet part out load.

But lets face it you might have slashed your wrists by now....

Yes, standard = height set on probing up.
Yes, I saw that hesitation which I think is reducing velocity at probe height which is normal.
Early in the piece, I added a set screw to reduce float switch hysteresis to the barest of minimum.
the second video depends on the float switch to absorb over travel/inertia due to travel speeds.
Yes I don't think a float switch us necessary if you have reliable ohmic probing. In fact my float switch proximity sensor was broken for months and I didn't even know.

I'm not sure about the probing with ethercat, I know some commercial machines sense the material by torque. But if you have torque homing set up and working, perhaps you can use it for material sensing. Maybe you would use the probing function instead. It will be a good experimental project for someone like you

Yes, U22

Here is at least one source:

eu.mouser.com/ProductDetail/Texas-Instru...gQLk2CaRciYmIQ%3D%3D
 

This is dependent on the outputs and inputs of the stepper driver you are using. Can you share more?

Personally, I don't think you can achieve what you want.

But getting faults on the drive implies an incorrectly set up stepper. Fix that and the problem goes away.Try reducing the current on the drive.

Thank you for your quick responses!  Please tell me, am I correct in understanding that U22 refers to this chip? Could you also tell me where else in Europe it can be found, or any suitable equivalents? 

Hello!

I'm kind of a newbie with the LinuxCNC stuff. I enjoy working with this stuff. It's kinda fun...

But serious question now. I have a MESA board, 7i96s model and I want to make an automatic tool changer using the board I/O to control all the moving pieces and so. But I honestly have absolutely no clue ...

Can someone help me with anything to pull this thing off?

Thank you in advance!

Hi

Welche Versionen benutzt du gerade?
LCNC, Probe Basic und meine Routine

Hast du vielleicht in der Werkzeugtabelle noch die Pockets aktiv? Ich weiß nicht ob es relevant ist, ist jetzt erstmal nur eine Idee.

Muss gestehen, dass mir der Fehler neu ist.

Follow-on:

I'm working on a python program to check the levelness of my table.

I have several o<word> functions that are currently attached to buttons on the gmoccapy vcp, one to set zero_z, one to make the measurement and one to reset the spindle back to zero_z preparatory to the next measurement. All work as expected.

The python program is an attempt to automate the process measuring the four corners and the center of the table, then record the values into a spreadsheet. The hope is that overtime I can create run charts for each point to evaluate accuracy and precision.

Currently, the application moves to the Z height and sets zero_z calling the first .ngc function as expected. Next it moves the spindle to the first corner and calls the measurement.ngc. The spindle is lowered to the touch plate, but fails to move up and back down for the final measurement. It appears as though the function is failing to execute all of the commands before returning to the application complaining that the spindle failed to reach the touch plate.

I'm wondering if calling an o<word> function is limited to executing just one command when called by c.mdi("o<word>")?

Perhaps o<word> commands need to be processed with c.program_open. However, your previous response indicates that the code would be loaded but, not executed. 1) How do I get the file to execute after opening it, 2) Will loading a program preempt the execution of the running python program?

Any hints to get around this SNAFU?

Regards,

I am trying to call the Lcnc_Dialog widget from python code.

My code is as follows.

When the dialog pops up it lists all of the text in the msgdict variable and does not show the dialog as expected.

I know the issue is something simple I just can't seem to see the issue.

Thanks,

Can you reset the drive by disabling and immediately re-enabling the drive?
That is something that could be done in hal (at least for Z)

(assuming you have the drive enable connected)