Advanced Search

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?

Yes.. power up.. start linuxcnc... loose the brakes.. bring all joints to the sharpie marked position. Then reference/home to the index of every single encoder.
After this all joints at zero. B axis has offset 1 degree that there no failure message comes from linuxcnc because.. if all joints at 0 degree they are in singluarity... thats why its needed to brin as example a small offset to the B axis.

Thats how i understand it.

I really appreciate you info dumping here; so much good stuff to know.

I had a 7i80 with a 7i85s and a 7i37 working with 3 stepgen, I tried reconnecting it and only a step dir signal comes out of the y-axis and that's it. I loaded the firmware 7i80db_16_7i85sx3d.bit. I don't understand what could have happened, I put it away and all three axes worked.

hitchhiker wrote:

I only had zero x y z in genser mode... not correct?!

 

First at powerup you have to zero every joint, did you do this?

disclaimer:
I have not yet had opportunity to run a LinuxCNC robot, except for playing with the sim. I have spent many hours programming/repairing Fanuc and ABB robots. Some day when I have enough projects completed to make more space in my shop I want to buy an old robot and put LinuxCNC on it.

I only had zero x y z in genser mode... not correct?!

I know that when i rotate A axis the B axis make moves.. because the mechanical stuff inside the hand goes over small gears.. but this should not be the problem or???

Thanks

hitchhiker wrote:

I have a small success...old ini... home and homeoffset to zero.. jog to marked position (edding/sharpie on the joint..).. then homed to index.. bring all in a non singular position... start g code...

I think this was a step in the right direction... but z stays not on z on the table.. but on the linuxcnc dro
 

Are you saying Z does not operate correctly on the machine although it displays correctly in the DRO? If so then I would first suspect the problem would come from having some joint not zeroed at the exact true zero point. I think a slightly incorrect DH parameter would create the same symptom.

Hi,
after some test I found the maximal output step frequency that I can get is around 100kHz, , beyond this frequency I start getting following error message, no matter what value on following error is placed at .ini
Do you know if is possible to increase this frequency? 
And compared with maximal frequency step output from my PCIe Parallel port card (around 10kHz) I am guessing that is a very good upgrade, I hope this card (V2) became that stable as the PCIe card has been shown after this time that I been using it.

 

But what was on lines 1-4? The screen shot of your code does't show. It would have been better (and used less bandwidth) to upload the actual g-code file, rather than an image of a screen shot.

youtube.com/shorts/PnO5MxeK1Xg?is=1G0Dy59B0bhhUQdd

I have a small success...old ini... home and homeoffset to zero.. jog to marked position (edding/sharpie on the joint..).. then homed to index.. bring all in a non singular position... start g code...

I think this was a step in the right direction... but z stays not on z on the table.. but on the linuxcnc dro

Heeeelp thanks

To analyze problems with gcode, it is so much easier to load the relevant file into your own simulation and test it than to look at a screenshot and make some assumptions...