Advanced Search

I just added:
/(PREVIEW,hide)
to a program and to see the difference in the graphics view (after each toggle) I had to reload the screen. Maybe that should be automatic?

I'm pretty sure you don;t need to reload for actual Gcode commands, but the options must be set before running.

For the other discussion it boils down to me realizing that I don't measure 0 to 200 Volts, but instead 0 to -200 Volts.
It works because it is truly floating, but it's not desirable the way I made it.
A quick test made me realize I am not an electronics engineer, but I'll get there. It will be put on the slow burner. I mean it works as is and it works good.

As for the grounding, it works fine so no change needed. All signals are by designed isolated, no ground loops I can think of. But if any noise problem develops, I know what you all do.

yea i have thanks but now have to clean up my ini dos corruptions i did not realise that notepad from wine was used to open my ini file.
Just up graded from 18.04 to 20.04 Ubuntu hoping to get better speed from my machine and it has become a bit of s doze machine.

Hi,

Precision of the entire machine and resolution of commands are two very very different things.

The setup and build of the machine itself are not the topic of this discussion. Please keep it that way.

PLEASE stay on topic.

Thank you

Back to the centre home position, you touch off using G54 offsets to achieve this in the work piece
linuxcnc.org/docs/2.4/html/gcode_coordinates.html
Here is an example part where you would touch off on the centre of the part as everything needs to be concentric of the centre bore.
 
This does not affect the machine home position
 

@phillc54 What's the boiled down theory of that? Disconnect electrode lead and a new voltage sensor path?
Edit: looked again, no its not that. I don't get it.

Can someone point me to the documentation on how to setup/use "Opt Block" and "Opt Stop" in QtDragon?

I tried putting a slash at the beginning of a block of code, and all the combinations of Opt Block on/off and Opt Stop on/off before clicking "Cycle Stop," but I couldn't see any change in behavior.

Also, I noticed that I can't turn them on or off while in Auto Mode, but that seems like it should be the mode I would want to do that in. ??

I searched for "Opt Block" and "Opt Stop" on the following two pages:
linuxcnc.org/docs/html/gui/qtdragon.html 
linuxcnc.org/docs/html/gui/qtvcp.html
and generally in google, but couldn't find any love.

Are there .hal pins?

This is not a priority, but I'm curious.

Thanks!

tommylight wrote:

It is not possible to use the same pin for tandem axis homing, but you can use one pin for home_all and the second for home Y2 as in the attached example from a working machine.

Also note how Tommy has used HOME_SEQUENCE to home the Z axis first.

This approach from Toast is also worth considering. As used by Swift Cut commercially (And also by Les from Sheetcam)

Using a safety relay with the estop external to Linuxcnc would be a better solutio.
If you used force guided relays as part of the estop circuit, you should not have an error. These relays have a pin that is forced into the contacts to force them apart. But you should have redundancy so two relays (probably in series) are used and both must be triggered.

 

I have an existing SBZ 130 i want to retrofit by keeping the original motors+drives, the motors all (3 axis and spindle) are AC 3PH servos with integrated 2 pole resolvers (6 wires - sin, cos, excitation pairs) for their feedback, aside from that I have about 42 inputs and 36 outputs as per the machines original schematics, but I might not use every single one. Moreover, I also want to add a separate rotary milling head for chamfers at different angles later down the line, so how would I go about adding/changing the combination of mesa cards.
The same machine I've seen a successful retrofit using combination of 6i25 7i77 7i70 7i71 7i74, but that system all the motors had absolute encoders
Mine is slightly different model (1998, mine is 2001) and I was recommended from a different person to go with 6i24 (do i need 6i24-16 or 25 and whats the difference??), 7i49 for the resolvers and controlling the drives with 10v analog, but would this work? I'm a complete beginner to this field so I'd like to know before purchasing any hardware. Moreover, do I need the other cards as well? (7i70 7i71 7i74) I understand the first two are for extra I/O digitals but im not sure what the 7i74 does, if someone can explain I would greatly appreciate it.

Edit : I just found out that the 6i24 has about 70 I/O pins, I think that covers my need so I dont need the extra 7i70 and 7i71 right?

I already have those set to the individual drive error/fault output pins, so I ended up adding a names_misc_errors, which according to the docs, does the same thing.

Thanks PCW!!

I will try this in a few moments.

I will report, if it is working

BR

I zero y table moving full front and sets zero. travel directions will always remain the same in the Cartesian coordinate system.

If the resolvers go to the drives(and this would be expected for AC servos),
the drives themselves have the resolver interface, so a 7I49 is not needed.
What hardware is needed to interface to the drives themselves depends
on what interface modes the drives themselves support.