Advanced Search

Thank you very much for your answer. I'm still a bit confused, I can understand what servo_period is, but I don't know what traj_period specifically refers to?

Hello, I'm trying to solve the following issue: 

Firstly, I'm using a Mesa 7i76e card to retrofit a Hardinge CHNC lathe. Special thanks to those who have shared info on the turret indexing etc (John!). 

I have made a spindle driver for the DC spindle motor that these things were shipped with. I want to sequence a few events when the spindle is commanded ON (M03). 

M03 needs to equal: 
1. Engage contactor (easy)
2. Delay x amount of time (1 second or so, precharge capacitors)
3. ramp up spindle speed (using mesa's 'potentiometer replacement' section of card) and PID control speed to by using the spindle encoder for feedback 

M05 needs to equal the same steps in reverse:
1. ramp down spindle speed
2. delay or look to see that spindle is near zero rpm, either is fine
3. disengage contactor 

I saw posts on how to hold feed moves until spindle is up to speed but I have not seen anything yet on how to delay speed command for a duration after spindle enable is used for something. Maybe theres a way to do this? 

Looking forward to any tips you may have! 

Thanks very much.  

A 7I92TH/TF and a couple Mach 5 Axis BOBs could do this
(or even without the BOBs if you are careful...)

Not sure what that was but reinstalled Linux Mint Debian Edition and didnt have that issue anymore. made it to finalizing our control box now, Just waiting on our 2nd THCad2 to arrive. decided to use 2 cards one for OHMIC and One for Height Control. That will be our next step hoping it wont be a big step lol..

Also this is not a boot issue, it is a LinuxCNC gracefully failing to start issue, gracefully as it also reports why it failed, but this time the reason it failed is missing from the pictures, we need the debug portion of the report, as Cornholio mentioned above.

meister wrote:

How Many Axis do you need

little fun-project, almost without soldering, but works and is inexpensive



 

For this project 5 step/dir channels and some way to control a 3-wire RC servo motor.  I'd go with a 6 channel Mesa card if it wasn't a little pricey and out of stock.  

I've seen that setup you mention, or something similar in the LinuxCNC compatible board list.  Soldering doesn't scare me, code does, I'm a novice/intermediate coder. What I liked about the Mesa board I have on my router, it was virtually plug and play. 

If I can save a few dollars and learn something along the way, maybe I'll give this route a go.  I'll have to check into it.

No I didn't install it, just ran the script from the cloned directory ./rpi-eeprom-config.
Odd it partially works,
No cannot see the part to follow,
sudo apt install openssl python-pip fails but suggests
sudo apt install openssl python3-pip (success)
sudo python3 -m pip install cryptodomex
get message about externally managed environment and many options I cannot get to work.
Many thanks for this, but your plan A is looking far the best approach now.

Hey all,

I'm hoping to get some clarification on the probing setup used by the Probe_basic system in QTDragon_HD.
I'm trying to calibrate my 3D probe, which the GUI provides an interface for doing, but I'm unable to find any documentation that explains it's use.

I measured my probe tip with a micrometer, a ruby tip of 1.987mm. Probe_Basic then has an input box for this number (tip diameter).

Now to calibrate the probe, I have first reduced the runout to <0.02mm. Was hoping for <0.01, but couldn't for the life of me do better with the little grub screws!

Reading the probe_routines.py, the calibration routine first probes the center of the bore, then repeats from the calculated center another probe cycle. I can confirm it does this, but the only return seems to be filling out the delta status box. is there no automation here, or am I missing something?

When I run the cycle using a bore I've made that measures 31.201mm (used bore gauge), it reads back a measured diameter of 31.507mm, a delta of 0.306mm diameter or 0.153mm probe offset. 

What do I do now? I tried entering this into the "calibration offset", but then when I measure the bore using the standard bore probe routine, it still reads 31.507?

Note I also measured a 100mm gage block, and it read the same offset.

What am I missing here? Should I just add this offset to the probe tip diameter? That sounds wrong to me as it would then affect my z as well.

Any help would be hugely appreciated! 

I have tested the pcbs and work fine except they have burned 3 times 0.5A fuses
I have 3 pcbs in mill and all times fuses burned in all pcbs.
I have replaced with 3A fuses and no problem.
Your scales work with 0.5A fuses ?
Because i didn't found tic116 scr i have used tic106 also not populated quad differential transmiter
www.farnell.com/datasheets/39877.pdf
www.farnell.com/datasheets/63251.pdf

with P=1 / FF1=0.12 was a very good starting point responds very well..
Next is halscope tuning..
Thank you again

Screen shots are difficult enough, but the debug section does not appear to be there, which kinda makes it hard.

Are you sure you're using the updated tool as that string doesn't appear in the file.

Did you follow this part
Requires Python Cryptodomex libraries and OpenSSL. To install on Raspberry Pi OS run:-
sudo apt install openssl python-pip
sudo python3 -m pip install cryptodomex

How are you calling the new utility ?
How did you "install" it ?

The string you're quoting is from an old version. I suspect you're still running the old version.

Just for fun, here are some of the first moves it made when I got a very rough tuning on a single loop working.  Crusty motors and drives circa 1989!  Pardon my shop disaster, everything is a mess from recently moving the machine in.


 

How Many Axis do you need

       

little fun-project, almost without soldering, but works and is inexpensive
 

But...
so I run the updated tool, and the BOOT_ORDER info is displayed
I can apparently edit the line. ^O to write it, and ^X
but on exit, the very final kiss of doom is another message.
"This tool only works with a Raspberry Pi 4"

Back to plan a.