Advanced Search

many thanks again

fixed in main/dev

I recently made a modification that only copies the modifier files to the Gateware directory when necessary,
but I didn’t realise at the time that some of the filenames are slightly different (debounce -> debouncer.v / pwm -> pwmmod.v)

Thanks guys, got it working and after playing with parameters it feels quite workable.
The joystick is one of the ones with a button so may look at using it for fast/slow jog

Will post full file once finished

It is interesting to see your mod. It looks like you have kept the original spindle motor and gearbox control. Did you use the gearbox Comp my mate created for the 400E, or did you roll your own?

github.com/jin-eld/mh400e-linuxcnc

Thanks for the feedback I will try again .

When I bought the machine it would not boot, with a bios battery error message, so the original computer is probably dead, but not really a big loss... But the machine was working fine the last time it was used, a couple of years ago, according to the seller, so the original Indramat drives and motors are probably fine. Main problem is they require 380v, 3-phase and 17kW of it... A bit more than I have available in my garage. So the plan is to reduce the power somewhat (especially for the 10kW spindle motor), given the machine is only going to be used for hobby projects, and get it to run at 230v 3 phase.

With regards to ethercat vs mesa it looks to me, based mostly on forums posts, that the mesa route is safer, more tested and less potential problems, does that sound about right?

Yes
The ini file is from gmoccapy sim sample
Only adjusted machine size and speeds according to real cnc.

Dear meister:

 


When I add debounce for bitin7, the builder had a error.
Thank you


Tim

Dear meister:

I tested again, Thank you very much

In your ini file your max limits are negative, I doubt that is correct. Remove the - from max limits. If the motors run the wrong direction, fix by adding - to scale value as tommylight has pointed out.

Now that sounds pretty neat! I take it your Arduino Q contains literally both the mini-pc running Debian 13 AND the motion controller grblHAL STM32. The entire system on one compact little Arduino board the size of Arduino UNO!
I bought one of those Arduino Q when they introduced them. I'd love to unpack it and try that, but I'm currently working overtime on another big project, that should be done in a few more weeks...

Did you try editing the ini file for the sim?

If the old motors and drives work, i would not change them, just get some Mesa analog boards and move on.
I can not give you useful advice for now as i always try hard to use the existing drive train when retrofitting (done plenty of those), and i did not use EtherCAT yet, but from what i read here they are both hard to set up and have issues i do not like to deal with, especially having position feedback going on vacation at random on a 15 ton machine.
If you need inspiration, have a browse through "show your stuff" section of the forum, plenty of retrofits by me and other forum members there, also many more on other sections but might be harder to find.

I still have some old functional microwaves in the shop...
And some 6S/32AH batteries,at 10C they can deliver 320A of current easily, should be enough to run 6-8 microwaves at once! For around 5 minutes...

I really hope those are not - signs in front of the axis lengths!
First, make sure when X axis is moving to the right numbers go up on screen, move up when Y axis moves away from you, and go up when Z axis goes up although these should be negative values.
You can change direction of any axis/joint in the hal file, just add - sign in front of the SCALE value in the INI file, save and run LinuxCNC (needs restarting LinuxCNC, not the PC)
Only after you got this correct move on to fixing homing if using home switches.

Dont forget to set halui.axis.N.jog-speed as well to the same value as joint.N.

joint.N.jog-speed is used before homing, and axis.N.jog-speed is used after.

It may get a little complicated in HAL, but there should be a component or other logic chain which triggers joint.N.plus when the joystick value is >0, and opposite for <0.

Maybe look at wcomp...  Perhaps two wcomp instances, one for plus and one for minus:

• set the wcomp.0.min to just above 0
• set the wcomp.1.max to just below 0

giving you (I think) an adjustable deadband if the joystick analog value flutters a bit at the center point.