Advanced Search

I got it running!  Turns out it was just a hardware issue. I’m using a 48V PSU that I hadn’t earthed, which caused some strange behaviour. I’m also running a Leadshine DM805-AI and realized the 5V needed to be connected (I had assumed signal GND).Just in case it helps anyone else, I’ve attached my HAL and INI files.Now making this into a carousel setup—wish me luck!

Found out the file is to large.

Thank you very much. I will review this information.

Not my video.

Thank you,

after i have had read the manual i could solve the problem.

 

WOW, you made 3 posts, quite long at that, justifying yourself being obtuse from the start, instead of replying to questions, or even more importantly, making a normal post to begin with, with normal questions and at least some info to go on with, so now we have a mess that absolutely helps no one, nor does it contain any info about your machine/software/use case/what the issue is.
And you call us being ....
And since you got stuck to it, "again" was aimed at you not giving us any useful info, but hey feel free to write essays about it, as long as it keeps you from giving us any info about your "miracle" machine that you "invented".

So I'm working on a CNC (DIY build) setup using LinuxCNC and a Mesa board. Apparently it used to work, but there has been an update of LinuxCNC, and probe_basic and now I get an error on starting Linux CNC with regards to probe_basic
"5/30/2025 Latest update requires config modifications"
There is also a link pointing to a section in the probe_basic documentation that describes the changes that need to be made.
I've been through the changes, and to the best of my understanding, made them. However the error is still there. This suggests I've missed something, or got something wrong, which is not unusual in itself. The problem though is that I can find absolutely no clue as to what I've missed. The log file seems to contain no errors, or indications of what steps in probe_basic have been successful.
Is there a way to troubleshoot this? Some output somewhere that would indicate what the specific issue is, or failing that, a standard config that is going to work that I can then add the machine specific changes to?

regards

Jonathan

It is ok?
Milko 

With Linuxcnc running and a  S1000M3 MDI command executed,
 what does:

halcmd show all | grep pwm

report?

(halcmd typed in a terminal window)

Wow.! Thank you for the deep explanation.! Let me try that. Because I am no fan of step/dir method which is unreliable and prone to many isues like EMI. Since Ethercat is free and Ethercat Based servos have become relatively inexpensive. I am going to give a shot. 

If the comp table is backwards then the interpolator function will only ever read the first value, so you will get a fixed offset, and no apparent compensation.

Your HAL looks correct.
When you say "in the oszy" do you mean in the HAL oscilloscope , or on a physical one?

In the HAL oscilloscope try scoping both the index-enable signal and the hm2_7i80.0.encoder.00.input-index pin.

If index-enable is high then it should go low when the (short) input-index pulse is seen. 
The index-enable pin should go high as soon as the home switch trips. 
 

  Hello,
between pins 22 and 23 I find 10V
between pins 22 and 24 also 10V
I don't see any change if I lower the speed
if I stop the spindle
between 22 and 23 0V
22 and 24 10V

Thank you

Miilko

I think it was an attempt to link to this thread.

forum.linuxcnc.org/plasma-laser/41893-ci...ng-to-cnc-use#202415

And now that we know that it is CigWeld CutSkill, not Gig SkillCut we might have more idea what is being discussed.

As setup, if you have 10V on Spindle+ (7I96S TB3.24) and you run s1000M3
in MDI, you should get +5V measured from Spindle-Out  (7I96 STB3.23)
to Spindle- (7I96S TB3.22)

(you do have to home the machine before MDI will work)

I would verify this before worrying about the VFD setup