Advanced Search

I'm not sure what makes you say that. The table you posted shows that 38.2 probes toward the piece and 38.4 probes away from the piece.

Also, I've implemented this enough that I can get it to sometimes work (~1 in 10 tries) because the "Probe tripped" error that I mentioned doesn't always occur.

7I85 or 7I85S?

Not sure what you mean by index enable.
(all configurations with encoders have an index enable pin)

 Edit: I looked back and you are using step/dir index and a 7I85
(even though the firmware you are using is for a 7I85S)

As far as a PWM output goes, it probably belongs on a free 7I96S
STEP/DIR output, Is that OK?

 This means two PWMgens on the 7I96S (PWMgen 0 for the built in analog and
PWMgen 1 for the PWM on the step/dir pins)
 

sudo mesaflash --device 5i25 --dbname1 7i76 --dbname2 7i74 --readhmid

Yes. I wanted to communicate via spi only. Since I also configured it in spi mode in daisy chain config in FluidNC. Remora communicate with LinuxCNC via spi. If possible I can send spi config data to tmc via some module in LinuxCNC. Or if you modded remora-spi source to suit tmc 5160

If you are doing 3d printing have a look at the remora

github.com/scottalford75/Remora

This will display the current speed as a bar indicator and the spindle-at-speed signal as a red/green indicator to the right of it.
Example form the docs (speed 0 and spindle-at-speed True):

 

Ok, not sure how I do that as I used the stepconf wizard to create the config files and it created the pyvcp files.

Gmoccapy provides it's own pins for spindle feedback which you can connect in your postgui halfile:
linuxcnc.org/docs/html/gui/gmoccapy.html#_spindle_feedback_pins

Hi Grotius,
In the latest version of scurve, how do you set the max deviation parameter? 
Right now, I am not able to change the filleting using the spline. Is there any way to enable spline filleting?
I am running the ../cmake/configs/axis_9/axis_scurve_9_mm.ini config.
My tpmod parameters are: 
Parameters:
Owner   Type  Dir                 Value  Name
     4  float RW                    0.5  tpmod.hal_blend_speed
     4  s32   RW                      1  tpmod.hal_blend_type
     4  s32   RW                      1  tpmod.hal_g0_transition_blend
     4  s32   RW                     20  tpmod.hal_look_ahead_lines
     4  float RW                   2500  tpmod.hal_max_jerk

No amount of fiddling with G64 is getting the splines to show up.
Am I missing something or some step? 

Regards,
-automata

did you tune your servos?
could be just small gain in drive.

And will go with two THCAD-2 as ohmic sensor looks like very good approach. For the moment i'll stick to the hand held Duramax torch i have. 

Thank you so much for the data, that made my day!

as soon i have the hardware i will try to get it running. If i have time in the i will try to make a GladeVCP screen for the turret.




Greetings
Tom

The thcad2 replaces both the thcad 10 and thcad 5. The manual will tell you how to configure it. Go for a 200 volt range and you will be sweet for the 45XP

Personally, I would buy the cpc interface. There is a trick you can do with a short piece of fine wire inserted into the torch connector to permit CNC firing of the machine torch Search for it.

Thank you rodw.

I don't have THCAD yet and i just saw on Mesa website only THCAD-2 is available:( The rest is out of stock - looks like i'll have to go with THCAD-2 anyway and deal with voltage dividing somehow. My Hypertherm 45 XP is not equipped with CPC apparently, the second source as well. Buying CPC now is not and option so i will need to look at THCAD-2 if i can add some resistors to extend the range.

I'll spit my dummy if you delete this topic. I learnt stuff that was interesting. I had no idea about the whole silicon thing, which was largely due to living in a western English speaking country.....and probably dropping out of highschool. My attitude was inversely proportional to my intelligence. The more I learnt the bigger cnut I was at school.
School is wasted on the young

If you had of read the docs, the parts regarding using a parallel port and software step generation, you would have learnt that there is a limit to the stepper speed based on the latency of the base thread.
This is the problem, people don't fully research/read the docs and don't fully understand what they are doing. They also assume things that are not so.
Many times people blame Linuxcnc, 99% of the time it is a mistake they have made.
The recent rise in the availability of home CNC machines has led people to think it is easy thing to setup and use. It's not, there are many hats you have to wear. And to be fair the basis for a project for Linuxcnc, all those years ago, was for control of industrial machines. I don't think the original authors of the papers imagined the extent that small CNC machines would become available to the "average Joe".
Checkout the mesa website, see what they have available. Read the forums, see what other people are doing. Checkout the remora project, have a look at Linuxcnc-RIO, geesh I even gave a link to my own GitHub project.