Advanced Search

You only need C3 if the bearing is an interference fit in the housing and on the shaft.
What are the original bearings? If they are C3 it will say on them.

Open a halmeter and see what the mode flags show:
linuxcnc.org/docs/stable/html/gui/halui.html#_mode

mode.is-manual needs to be true for jogging to work, it seems possible that something is changing mode.

Are you keyboard jogging, or using handwheels? It might just be a UI focus problem, with the key presses being "captured" by the button itself.

But check the mode first.

You ought to be able to update straight to 2.9.10 now that you have a working install.

What interfaces / motors does the current setup use? Is it a stepper machine or servos?

If it's a simple stepper machine you could make a start using the hal_gpio module and Pi GPIO pins, but you will need some level-shifting protection as the existing logic is almost cetainly 5V (or 24V) rather than the 3.3V of the Pi GPIO pins.

Are you planning to retain the existing drives?
I tink that where you choose to make the cut between old and new would depend on where the electronics failures are happening.
But it is generally best to keep the original motors and often (but by no means always) best to keep the original motor drivers.

Doesn't the 4000L have the carriage handwheel MPGs? I would think that those make a pendant superflous.

forum.linuxcnc.org/10-advanced-configura...oling?start=0#225787

forum.linuxcnc.org/show-your-stuff/53476...rical-mapping#307444

Any progress so far? I was wondering, if the mathematics in @nojo project is correct, would it be possible to create a hybrid solution by combining it with @fsabbatini project? Specifically, using the tool offset handling from @fsabbatini project and integrating it into @nojo project.

I'd like to thank everyone who contributed to making this project a reality. Fantastic work! The difference with the new S-curve planner enabled is huge. Motion is noticeably smoother, and the overall machine behavior has improved significantly.

Here is the file, you can see that  stepgen 03  has only dir , I don't understand why I put aside this combination: 7i80-7i85s-7i37 went 3 motors in step dir. I only need it as a transition because then I will switch to the 7i97t in analog, but for now I wanted to use step dir for 4 motors without any encoder or anything else.
in practice only the stepgen 3 one doesn't work 

Actually one way to do this would be to write a gcode filter for linuxCNC  that looked for hole below a certain diameter, removed the hole processing and replace it with a spot at the hole centre. Monokrom plasma has a filter that modifies hole processing so perhaps it can help you.

Another really out there possible solution that does not need post processing (but requires master branch) could  be to write a component or modify plasmac.comp and monitor the pin motion.interp.iscircle. When it goes true and motion.interp.arc-radius < minimum hole radius, disable the torch, use external offsets to move a distance of motion.interp.arc-radius along motion.interp.normal-heading (which will be your hole centre), fire the torch to spot, then unwind the offsets to return to where the torch was, let motion take over again then enable the torch when iscircle goes false.(the end of the hole)

QtPlasmaC should have a hole spotting/pierce only feature, i am pretty sure i tested that a while back.
www.google.com/search?q=qtplasmac+pierce...tplasmac+pierce+only

I just noticed the hal tutorial is not obvious from the earlier link I shared. It is  here . Also explore the rest of the  manual .

Zipdodar wrote:

Hi Group

I would like to potentially use linuxcnc on a Raspberry Pi to program and test steppers and servos

• Are there any solutions that I can see samples of or potential uses that are using a Raspberry Pi or Arduino and LinuxCNC to control and test servo and stepping motors?
  
• One plan is to have a test bench to play with ideas; this will have a controller board, some switches, sliders, connectors for motors, a variable power supply, etc..
  - Could LinuxCNC be used for this? i.e can i program it with Python or similar to run my code snippets or a full program?
  - When connecting motors that use pulse and direction, will I be able to connect any motor as long as the variable power supply is adjusted to give the right power to the motor?
  - Has anyone done this before like this?
  
  
• Another plan is to create individual builds that will have one or more motors, sensors, switches, etc.. and will be all built into a case or item as a stand-alone solution. With a customised touch control screen. So when powered on, it boots up and is ready to use and be controlled from the touch control screen.
  can linuxCNC be used like this?
  if so is ther any links to videos or projects that do similer?
  
  Z
  
  

Sounds similar to some of my customizations. I get, you won't need to run G-code files?

Look at the  hal introduction , and the tutorial that follows. There are several methods of connecting your own custom gui to a stand-alone basic hal config. I tend to use glade. Yes you can then also have the app auto-start, that is configuration in the desktop environment, same as auto-starting any other app at boot.

Yes
Yes
-yes
-yes
-yes, i did, to much for for not much use
Yes

dlv wrote:

I'm trying to stay in Fusion (for now at least).
 

In my opinion using Fusion for plasma (or laser) is like bought truck for drive to church - more troubles than benefits.
My favorite option is Librecad plus dxf2gcode - GPL and cost free.
Try this, even if you will not like them, this is simple and you will easy learn something.

Can't help in fusion but in Sheetcam you can create layers and you can define the minimum diameter of holes you can cut (say 12mm) so you move all of the small holes onto a new layer. When you generate the code for that layer  it will create the spots at the hole centre.
The torch won't fire if there is no movement in the following segment so move to relative coordinates to move a tiny amount to keep LinuxCNC happy and make the torch fire.

So now see if you can translate that to fusion.