Advanced Search

Well, I run sensor in terminal and output is in below:

==============================================================
raycnc1@debian:~/Desktop$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +56.0°C  (high = +84.0°C, crit = +100.0°C)
Core 0:        +56.0°C  (high = +84.0°C, crit = +100.0°C)
Core 1:        +54.0°C  (high = +84.0°C, crit = +100.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
temp2:        +27.8°C  (crit = +119.0°C)
temp3:        +29.8°C  (crit = +119.0°C)

radeon-pci-0100
Adapter: PCI adapter
temp1:        +60.5°C  (crit = +120.0°C, hyst = +90.0°C)

raycnc1@debian:~/Desktop$
=================================================================
Now the max jotter is 7000ns (servo thread) and 11880ns(base thread). If any thing abnormal in above data, please reply.

I am waiting for the spike to happen again and check sensor data again.
 

wow, thank you
my ping was 0.4s to the mesa card and went to 0.4ms

Since you already purchased 7i77 boards. SC900 servo drive does already convert resolver signal to incremental signal, lucky you Connect encoder incremental wires from the sc900 servo drive to 7i77. Connect +-10vdc from 7i77 analog outputs to sc900 servo drive. You still need the enable signal from the 7i77 to sc900 servo drive. I briefly had a look at your diagrams, it looks likeJ4 Pin 6 might be useful to enable drive (You still need to determine if the enable signal needs to be high or low)

for user xaxexa, when you say one pulse output , are you referring to it as only an A channel (x pulse/revolution) or do you mean it is a single pulse like an index channel where 1 pulse/revolution ?
if it is the index channel, you could probably implement it.

Echo to Murphy, we could benefit from having the option for only A/Z as it seems common for lathe users, , Myself and other users are finding increasing need for a non quadratic option so the encoder module can be used for MPG. Using Encoder module vs DIgitial IO for an MPG is a cleaner hal file, but also using digital IO for MPG uses 12% of the available inputs on the SPI version

Dear friends im facing problem of connecting 7I77 with Resolver based brushless servo encoder, Motors is rotating but not showing position changes on display. Pls help 

I was trying to edit LinuxCNC wiki. Signed in as usual. clicked Preferences ->  UserName: ben   -> Administrator Password: chipsI got the following message:Invalid UserID 111, preferences not saved.
(Preferences require cookies, but no cookie was sent.)Both Chrome and Microsoft Edge give the same error messageWhat am I doing wrong?Best Regards, Ben

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.