Advanced Search

Okay, good deal.  Glad it's working for you.

Thanks for the response. I am getting the line you asked about in the terminal. When I just tried using the space bar pause, it worked in all but one instance. I think you're right, it's a focus issue. In one instance, I had clicked the coolant button and then hit the space bar and the program failed to pause, but I was unable to replicate the behavior in the short session I had to test it this evening. I'll follow up if I'm able to reproduce the failure to pause.

But anyways, thanks for the help with this! I hadn't realized how much I use this feature until I didn't have it. When the tool is plunging rapidly, it's really nice being able to reflexively pause everything to check positions and the distance to go.

If you run linuxcnc from a terminal, do you see this text?
'Custom subclassed handler loaded for spacebar pause'

sometimes it's a focus problem, try pressing the 'G54' or 'ABS' button (after the program is started.). If that works I will look into why you need to do that.

I was able to reproduce this error with a simple test setup
with no mechanics and using g76. It also causes errors even
at a constant spindle speed, as the offset changes with thread
depth over the multiple threading passes which would cause
a  wider than expected cut.

To test this I setup a 7I96S with a stepgen spindle setup to
emulate a 8 count encoder with index (using the stepgen table mode)

I checked the offset by using the sum2 component to scale the spindle
rotations to the thread pitch and subtract the result. This offset
should be independent of spindle speed, X,Z motion constraints
and drive line distance to thread pass, but it is not.

Have you raised an issue on the LinuxCNC github page?
 

I would check the encoder signals at the Mesa card

The way to check is disable the drives (I hope this can be done
in a way the encoders still work) and then measure the differential voltage
(from A to /A and B to /B ) with a voltmeter in all quadrature states.
(you can usually to this by wiggling the motor shaft a bit to get all 4 states)

The absolute value of the differential voltage should always be greater than 2V
(you should get a positive differential voltage in one state and a negative voltage in
the other state)

Another check is to enable quadrature error checking on the encoder and seeing if
you get errors, that is set

hm2_CARD.0.encoder.NN.quad-error-enable
 true in halshow
and monitor
hm2_CARD.0.encoder.NN.quad-error

(CARD is the mesa card name and NN is the encoder number)

 

It doesn't seem to be working. Do I need to call that python file somewhere?

Hi Klopp,

That's a beautiful machine!

Looking forward to seeing the end result.

j

I dont have any experience with probe screen.

I don't know where to start. I found two sources:
1) Data in source codes:
lib/python/gladevcp/builtin-panels/versa-probe
github.com/LinuxCNC/linuxcnc/tree/master...n-panels/versa-probe
I don't know if it's possible to open it in Gmoccapy. And how?

2) Individual project:
github.com/verser-git/probe_screen_v2.9

What is better?

Thank you! That fixed it:)

Thanks rodw, I had ordered a DM542 from Steppersonline and it arrived today. Even with the 24v and 270OZ stepper and DM542 set at 3A I now have plenty of torque. Problem solved. I guess the TB6600s weren't up to the task.

satiowadahc wrote:

slightly off topic but related, A fun addition I made to our Gui.

Added a button that when you pause a program it appears. Saves the current position, current spindle speed, does a safe z move, switches to manual mode so you can jog.

 

satiowadahc hasn't been on the forum in a couple of years.  Anyone know what UI they were talking about?

I'd love to have exactly that feature.  The other day I was pretty sure my vacuum had clogged, since the pockets I was carving were completely full of sawdust about 3/4 of the way through the job.  If I could have, I'd have paused, done some hand vacuuming, and then kept going.  Other times I've thought, "sure wish I could recheck the positioning of that clamp", sometime after the job has started.

OUCH! 25KW DC motor... you win! I have a 11KW one on a Mazak lathe.
If the drive is working, i would not change it, well i did not change mine, so
-K332 is relay contact for enabling the drive
-Sollwert should be the analog +-10V input
There are other things there, but for now if the rest of the installation is OK, that should be it.
You would need an analog Mesa card like 7i97T or 7i92TM with 7i77, or some other combination.
In general, i use the old drives and motors whenever possible.

I would try to use them for sure, they are very good quality drives and new cost an arm and a leg, so try finding some used motors that work with these drives, for a reasonable price if possible.
Mind the encoder type.

That's a good suggestion. I comment out the offending lines and looked around "Show HAL Configuration"

Turns out, probe.* pins don't exist. HOWEVER, gladevcp.* has all the pins that have been implicated, including gladevcp.toolchange-change and gladevcp.ps_probe_max

The Z-height probing routine kicks off a message complaining that probe.ps_probe_max is not available so I thought I'd try to name it at the outset. I tried using EBMED_TAB_COMMAND to adjust the component name with -c probe but that doesn't run.
I dug around some more and found a line in probe_screen.py that was commented out.I un-commented it and it may have this particular problem. Makes me nervous because there are other lines nearby that are commented out...

Thanks for the tip, Aciera. Great handle, too.

Ah-ha! The 24V field power GND is not connected to earth ground, I was not sure that it should be. That probably explains it then.

Just weird that the machine ran fine for so long.

Thanks, I was getting frustrated with the constantly changing symptoms. I will connect those grounds tomorrow and test again.