Advanced Search

How hard is it to get the single A pulse and Z index working for the spindle? Is it going to be future update ?
​​​​​​
​​​​​​

Hi..new here....switching from mach 3...I set up 8 axis so far and want to run a test using my W axis to do an arc ....Should just changing axis name in file fro Z to W work or is there more to it than that?

Thanks for any help,

Rick

Hi, unfortunately no. The QEI is for the STM32 based boards, the QDC for the RT1052. These refer to the decoding circuits integrated into the MCUs. The QDC has the capability to count a single channel, but the current software implementation cannot take advantage it.

Thanks for the hint! I played a bit around with this example and indeed it is working, BUT:
I added the file-loaded signal and then it begin to behave different than inside gmoccapy code (user command file).
As a VCP I only get this message when I open another file.
But inside gmoccapy I get the message on every reload (reload button click).
And the message graphics-gcode-properties I don't get at all in a VCP.

Sorry it's taken a while to get back to you.

"So can you confirm my understanding - the qtdragon_hd.ui and qtdragon_hd_handler.py are are just copies of the most current?"
 
This is confirmed and correct. I put those files there as I may make changes to them for myself.

I ran a file yesterday that had a 2 tool changes, one at the beginning(as expected) of the file and one later on. 

Here's what I did in order:
1. from the MDI menu:  G54 X0 Y0
Results were as suspected.

2. Lowered Z Axis to top of stock and zero'ed Z
All good so far.

3. started running the file. The first tool change was successful and so was the touch-off on the tool height sensor.
All good here.

4. All of the cutting/paths was precisely as commanded.
All good.

5. At the very end of the first job, and BEFORE the tool was changed. The spindle raised up and was stopped but, NOT at the
tool change position. The RESUME button on the screen was blinking. Not good. 
So I changed the tool just in case I didn't get the actual tool change prompt.

6. Once I clicked RESUME the spindle raised to the top as expected and then moved to the tool-change position. The spindle was still stopped at this point. I received the  tool change prompt as expected and clicked OK to indicate that I had changed to the tool. 
All good here.

7. The spindle moved to the tool setter sensor, descended and touched off the sensor as expected.
All good here

8. From here the spindle moved BACK to the tool change location and began running.
All good here but I don't understand why it's returned to the ACTUAL tool change location and then switch on verses just turning on at a safe level above the sensor and them move to the next path?

9. And finally the spindle moved to the correct path and began "air-cutting" just above(10-20mm) the correct path.
Not good here.

This leads me to believe that something in my subroutines didn't work properly.

I am attaching these two subs.

Also adding the file that I was using. Note that for readability sake, I've truncated
quite a bit of the file size noted by 

---

CUT, CUT, CUT

---

  lines.

 


 

It wouldn't let me upload the photo of the rack and pinion and the servo, so here is the servo. They are all 3 alike if I remeber correctly.  They x axis one is covered in junk right now, I can't get to it.
 

i was not expecting this good of a cut step over or depth of cut for that matter but i probably tripled my step over on my X axis. .600 depth of cut with a .130 step over at @ 75 IMP with a 1/4 diameter 3 flute. the drive did perfect the spindle was starting to drop in rpm slightly. now i'm making some chips

 

I got the report file finally.

Tommylight thanks for the reply.  I'm going to research those tonight.  

It's funny, I'll think I've got a good handle on things, then I'll read something or watch something and then be completely lost again.  

That is actually the exact machine he bought.  That's exact one is sitting in my shop.

As far as the servos, I'll attach a photo, forgive all the dust and junk, it's been sitting dormant in a dusty shop.

And they are rack and pinion drive.  There Are two servos on either side for the Y, and one for the x.  Size wise I don't recall, but the pattern from what I could remeber matched a nema 23 or 34... I don't remeber for sure.   It looked like a stepper would bolt right in if the servo was removed.

Phew, that was long
For Mesa:
7i97
Or
7i92TM with 7i77
Or
7i96S with 7i77
Or
7i96S with 7i85 and 7i83
Or
7i92TM with 7i85S and 7i83
Not sure about the last one, if it has encoder inputs then yes, it will work.
Personally, i would go for 7i96S/7i85/7i83 as it has everything for step/dir and analog servo, and enough IO to get the machine going, then add a 7i84 for 32 more inputs and 16 more outputs, should be OK even for ATC.
All of those can be used for step/dir and analog at the same time, but do keep in mind that for 7i97 and 7i92TM wiring must be very careful for adding step/dir outputs as those header wires go to FPGA, so adding resistors or using a simple cheap BOB is advisable.
P.S.
Next time your head starts spinning, take a brake a day or two, then come back to it, it all starts to fall in place.

So I guess it's one of these:
www.govdeals.com/asset/16511/685

Looks quite sturdy but it's kind of hard to say without the details.
One thing you might want to check is the kind of mechanics they use to move the axes (acme screws, ball screws, rack and pinion, etc) also if it actually has motors for both sides of the gantry and what size the motors are.
A router will likely need a fair bit more lateral cutting force than a drag knife.

Sorry, there will be no crash report today. I lost the file and can' t produce a new one because linuxcnc is crushing linux every time since. I tried like 10 times. Will try later again. But I'd put no hopes on the crush file, because, as I said, it is different every time I was able to see one.

Max_velocity
Value for each joint/axis, that is in units per second, be it mm or inch.
But first check if the scaling is correct by moving the machine a certain distance in GUI and the measuring if the machine moved the same amount. Start with short distances till you get to ends of travel for each axis.

Ok, thank you very much.