Advanced Search

I have 3 new Mesa cards for sale. I bought those as a spare for a project but never needed them. All three are brand new, never used.

Mesa 7i77:  $180.00 USD     Come with a free set of 2 new din rail adapter   
Mesa 7i92   $  85.00 USD     Come with a free EPP-M parallel cable  (6 feet)  
Mesa 7i73   $  40.00 US

Will ship USA lower 48 only
Shipping for 1 item: $10.00
Shipping for 2-3 items: $15.00

I will list on e-Bay if no interest here.

Can you explain the "tool offsets...X and Y which is a bit unusual", please? The way I HAD been working was to (1) home my machine, (2) jog to the origin of my workpiece, (3) click the "touch off" button for x and y, (4) move my z to the the surface of my part and "touch off" z. (I also made a script with uses the tool setter for Z, but I'm leaving that out for this experiment.)
I don't think Fusion is setting G54.
@aciera thanks for the reply. I appreciate your comments!

The usual reason for brakes on non-indexing axes is to avoid unwanted motion when a driver is disabled. So, my first question would be as to why the motors on your machine need to have the brake applied while the motor drive is enabled.

lol - never mind.. I think I found it.. I will test tonight..

If Use Auto Volts is checked then the actual cut voltage is sampled at the end of the THC Delay time and this is used as the target voltage to adjust the height of the torch.

If Use Auto Volts is not checked then the voltage displayed as Cut Volts in the MATERIAL section of the PARAMETERS Tab is used as the target voltage to adjust the height of the torch.

Ventoy seems to be detected on BIOS-only systems where the Ubuntu ISO would not work on its own.

Try out Ventoy.

Try out Rufus, with different settings.

I installed Ubuntu on an old, BIOS-only laptop (c. 2011 Dell XPS l702X); Ubuntu only boots if the system partition of Windows 7 is there on the disk.

I strongly recommend leaving about 100GB unallocated during install so you can always install Windows 7 to that 100GB just so it will boot at all.

Note: If Windows is installed using the whole disk, it seems to put everything in a single partition; if you choose a custom install (using only part of the disk), it seems to install the OS to one partition and the boot stuff to another, small partition. You can delete the OS partition, but the boot partition might be necessary.

(Don't ask me why Ubuntu needs the Windows BOOT partition to work on my laptop, it just does.)

Short video
photos.app.goo.gl/sL9v2GkA7igL8KGU9

also - (I have just started using it and only have the 1 material in which is 1/4 inch. ) Made a sample program using conversational to get the jest of the gcode.

See below for the gcode I used as reference.
It uses tool 0 as far as I can tell - and as far as feed rate this seems correct - when I change tool 0's feed rate - it changes the programs feed rate.  OK..

But - I have the arc voltage set to 120.   When the program runs - the arc voltage is a constant 115.  I actually added 5v on the override so it actually shows 120 when cutting.   

am I doing something wrong?



G20 G64P0.004 G40 G49 G80 G90 G92.1 G94 G97 (preamble)

(conversational circle)
;using material #0: Basic default Material
M190 P0
M66 P3 L3 Q1
f#<_hal[plasmac.cut-feed-rate]>
g0 x0.152304 y0.152304
m3 $0 s1

g2 x0.152304 y0.152304 i0.367696 j0.367696
m5 $0


G20 G64P0.004 G40 G49 G80 G90 G92.1 G94 G97 (postamble)
m2

Python's error messages are so unhelpful.



Did you change anything?

Am I missing it?  Is there a way to display the current velocity of the machine while cutting?   

Thanks!

BTW - Just setup Plasmac using pncconf - It was painless and QTPlasmac is a really nice gui.   No problems..  (mesa style board with thc10)

Great work!

sam

Since this is for a lathe, there are only 2 joints in the HAL parameters. LinuxCNC requires that the joints are numbered from 0 consecutively, that is, I can only have joints 0 and 1. The association between joint 1 and the z axis is done in the HAL files. With that association, GCode works properly.

As I mentioned before, the pendant was jogging the X axis as I wanted in Step, Velocity and Continuous mode before I moved to the mesa card. I was using exactly the same vc-p1as.hal file as the one I'm trying to use now. Something very subtle changed and that's what I'm trying to figure out.

I tried debugging with halmeter and see what signals were triggered when I used the pendant, but that didn't help much. I'm still learning about the HAL.

Thanks once again for looking into this issue.

The gcode (M62,M63,M66) method with digital I/O will work for any motion but you need to change the gcode.

 

Aciera wrote:

The intended use is for indexing rotaries as described in this section:
linuxcnc.org/docs/stable/html/config/ini...:ini:sec:axis-letter

If you need more than just G0 moves then you would likely need to make something up in HAL.

 

I can only control the brake with G0 moves.
here is the way;
I have to control the brake for G0,G1,G2,G3 and manuel movements. Because that axis' motor has mechanical brake.
In any type of movement, brake is have to be deactivated and after the movement it has to be activated again.

Do you have any opinion else ? What else I have to try?

The intended use is for indexing rotaries as described in this section:
linuxcnc.org/docs/stable/html/config/ini...:ini:sec:axis-letter

If you need more than just G0 moves then you would likely need to make something up in HAL.

Nice work you have done on that DIY EXE, with DIN rail mounting.

Hi,
Check the Z travel to reach the probe in the .ini file.

buildbot.linuxcnc.org/dists/

is debs you can see if your OS is there and 2.7 is built for that OS version.

JT