Advanced Search

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.

Zipdodar wrote:

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?

You can build this, but it will be absolutely useless.

Which infos you need?

I can upload actual hal and ini again.

I thinking about the issue with the moving b axis when turn a axis.

Issue is that the b axis encoder is not reading the moving because it comes from the mechanical buuld of a ans b axis. Should i make a video???

I'm reasonably decent at CAD having used Fusion360 to design and 3D print for some time now.  However I'm a newbie (and I mean COMPLETE newbie) to CAM, gcode and post processors.  

I've built a 1500x1500mm downdraft plasma CNC table.  It's working rather well.  I've managed to get myself as far as the most basic of understanding manufacturing in Fusion.  Using the PP from the forum here I can get a flat pattern, generate a tool path and post it to an NC file and get parts cut with reasonable success.

I haven't figured out hole spotting though.  I know folks may say use something like Sheetcam and I'm sure it's a good solution but I'm trying to stay in Fusion (for now at least).

I tested QtPlasmaC's built in spotting function by writing a really simple gcode file to spot at the torch's current zeroed position and it works.  The built in spotting is quite nice actually.  Leaves a perfect little dimple (I'm testing with 1/8" aluminum sheet).  500ms pulse@20A

Before I try to reverse engineer the Fusion360 post processor to figure this out I'm wondering if there's any cool tricks in Fusion to get the PP to write the M3 $2 S1 command at a specific point.  

Or as a reasonable work around get it to write something out that's easy to search and replace with M3 $2 S1.   If that makes sense.

I did see something about adding in a drilling operation but when I tried it I discovered the free version of Fusion won't allow that.

Also not sure why the G91/G1microscopic move is necessary.  Pretty sure the tolerance settings will result in it being ignored but without it I get an error loading the file that it'll move outside my machine boundary.  I don't think that's the case but QtPlasmaC still throws the error.

Anyway I hope this isn't a bunch of utterly annoying newbie questions.    I sincerely appreciate any help with this part of the learning curve.

Cheers,

-Dave
 

Hi everyone,Ho to make visualization of the tool path for machine with naturally horizontal Z axis?A would like to use it for surface grinder and possible horizontal milling machine. Those machines have XYZ axis, but Y is vertical and Z is horizontal. Is there any simple way how to rotate virtualisation? 

What does mesaflash --readhmid report when  the 7i80db_16_7i85sx3d.bit firmware is loaded?

 

That all sounds correct. I think I misunderstood your problem with Z position. Can you provide more details?