Advanced Search

Hello, unfortunately I don't have a contribution to your CAM system, but I do have a question about the Raspberry Pi 5 and Linux CNC On the current PC I have problems with the latency, especially in the Ethernet connection to the 7i96s. Unfortunately, this always leads to unexpected stops of the machine. The last PC was no better and I don't want to buy a third one that will cause problems. My hope is that the Raspberry Pi 5 will work easily and without problems, even if it is a bit more expensive than a second-hand PC. Replacement would also be possible at any time. Now to the question What are your experiences with the pi 5 and which version are you using? Which SD card? Any special settings? Thank you very much Greetings Erwin 

Thanks for the idea. When I ran a few simple tests with no effect. I'm not sure how to test for emi. I expect if there was some my test would have had a reaction change but nothing changed. I moved the VFD as far away as I could and added a grounded makeshift shield.

I never thought to check that. I do have a filter on the VFD power. I will move it and see if that changes the problem.

I just went ahead and ordered the 1500mx. I had to get things rolling. It's gonna be an adventure!

As I said in the top post, my fallback is to use the same yaskawa PLC I did last time as a control. Last time it was a purpose built machine, this time I would have to rewrite my code to work on a mill layout. But I still have the backup of a simple UI coded for an automation direct c-more HMI. It has data entry boxes for operators to enter numbers for triming geometry. those get stored in memory and then applied to the motion control code in the yaskawa mp2300.

I just think it would be nicer and more dynamic to have a CNC control through. Hopefully I can make some flavor of LCNC work for me.

What does this code?

Is Electromagnetic noise from the VFD ruled out?

Hello,
I am scratching my head for days trying to solve a spindle problem. I have setup 2 other mesa boards and everything was fine.
When I attempt to start the spindle (M3 S12000) or click forward in the GUI the spindle starts then stops about 1 second later.
I did have On_Abort_Command setup and it called the abort which is the only thing I can get it to log. If I change the VFD to manual control the spindle works fine. Testing the 10V spindle out seems to be fine for the 1 second then drops to 0v. The machine almost always goes to "Machine Off".
The only differences to the other machines is they have dual Y and the size of the VFD.
I ran pncconf to setup a blank 3 axis limited machine for the 7i96s, axis work fine but spindle still causes the machine to reset.
My hal and ini are a mess from testing once I clean them up a bit I can upload them if needed, they are out of the box from the pncconf.
Motion seems to be fine, limits are working. I went through the .INI and .HAL line by line comparing all spindle items and found them to be identical. But of course the others work and this one faults.

Good morning Aciera,

I would be really happy if you could find the time and willpower to lift me up a little bit

I attached, hopefully my complete config incl. .comp & .py , config in the zip archive but  just to be sure i attached my vismach config separately.

Kind regards,
Jochen




 

OP-
I just re-read your first post and see that you want to be able to dial in tolerances, possibly for tool wear or stock variations.  This is possible with a motion-capable PLC, but is significantly more complicated than would be the case with LCNC and G-code.  I think you'd need an input - encoder or potentiometer - driving an input that is in turn driving/adjusting the motion positions.

So at this point my vote is for an LCNC retrofit.

langdons wrote:

Really bizzare.

Try the motor sans belt, draw a notch on the pulley attached to the motor and count how many revolutions it makes.
 

Yes, I would first check if the unloaded motor is doing what it should.

What is confusing me: Is the encoder in the belt loop or is it on the motor? If the encoder is connected to the motor and the driver is matching, a closed loop system should produce an error if loosing steps. Or not? 

Are you sure the pulleys are not slipping. (do not ask me why I ask this ) 
Had a similar situation, where things went slightly off. (at first I did not notice that the pulleys were not 1:1) after correcting that it was still doing weird stuff. I started searching for an electrical problem, but finally noticed that the set screw thread on the encoder belt pulley was not cut through all the way. It felt tight but it was not, result was the encoder was counting too less.

p.s. Another encounter I had was too short step input pulses to the driver, then the driver "thinks" it needs to move e.g. 1090 steps, but the controller was pulsing 1294 times and some of the pulses (not all) were skipped.
Some drivers have settings for input pulse duration. (just an idea)

pps. Thanks to my skillful EMC design I managed to drive the Z-axis down based on spindle rpm in a random pattern.





 

Any control you choose will need to be tested, along with the IO hardware you need to use.

HAAS has user-controlled M-codes, but I've no clue about add-on IO and how they manage/control them.

Any CNC control which uses USB for IO is suspect... you need direct IO, either through a main board (of some sort) or via an ethercat drive.  Most of the hobby-type controllers I'm familiar with have the ability to control IO via M-codes, but I think this scenario is likely best suited for 'vanilla' LCNC and a Mesa board.

Researching and proving out custom IO on a commercial mill control will, I suspect, take longer than just retrofitting an existing, working machine.

Another possiblity would be to use a PLC.  I've used an Automation Direct ClickPlus PLC for a two-axis custom drilling machine and that works like a champ.  The PLC has step-dir outputs for the servos, and plenty of IO for part-present sensors and limit switches.  Programming the motion part wasn't difficult, and ladder logic is pretty easy to set up conditionals and timers for your automation sequence.

As far as suggestions for what machine to start with, I'm at a loss as I can't really picture what you're trying to accomplish.  Part size, cutting tools, tool pressure (rigidity), stock feeding and part collection... And why a mill would be preferred to a lathe.  I'm kinda picturing a lathe with an air collet closer and two live tools mounted on a gang plate (no turret).

Do you have pictures of the previous machines and what a finished part looks like?

BINGO, adding the halui line did the trick. Thank you PCW and spumco, you guys are amazing (and lighting fast responders).

After my last post I was trying "machine-is-on" in the lines WITHOUT hm2. I tried your replacement and the result is M3 and M4 no longer do anything. No error.

#net spindle1-enable => hm2_7i76e.0.stepgen.04.enable
net machine-is-on hm2_7i76e.0.stepgen.04.enable

Even tried with the same "=>" and still same behaviour.

Do I have to do something with my regular spindle hal entries for it to play nice?
net spindle-enable => hm2_7i76e.0.7i76.0.0.spinena

PCW wrote:

Simply replacing:

net spindle.1.on hm2_7i76e.0.stepgen.04.enable

with

net machine-is-on  hm2_7i76e.0.stepgen.04.enable

Should fix the issue.
 

PCW - I didn't see the halui signal machine-is-on in his HAL file; maybe I missed it.

OP - if that signal is already in your half file, do what PCW posted.

If it's not already there, you can tweak it to this:

net machine-is-on <= halui.machine.is-on
net machine-is-on => hm2_7i76e.0.stepgen.04.enable

I can confirm this fixed my stepgen spindle after PCW suggested it to me last year.

Simply replacing:

net spindle.1.on hm2_7i76e.0.stepgen.04.enable

with

net machine-is-on  hm2_7i76e.0.stepgen.04.enable

Should fix the issue.