Advanced Search

FabLabRacing wrote:

Wins feel good, even if they are small ones

 

Yes, they do.

I have made a few updates to the code & I feel like I hit a pretty big milestone, I was able to get a full circle trace (for the first time) I set the software to use "to many" move points so I got an overrun of ~77 deg but for a camera-followed trace on a printed line, this seems pretty respectable. Especially because this is not post-processed yet — this is raw captured polyline.

This is the raw data:
Points:             250
Average segment:    0.02922"
Total trace length: 7.276"
Fitted radius:      ~0.9501"
Radial RMS error:   ~0.0108"
Radial p2p error:   ~0.0495"
Angular coverage:   ~436.9°

The overlap:
First full-lap return point: ~0.0167" from start
Overrun overlap average:    ~0.0114"
Worst overrun overlap:      ~0.0179"

The circle was drawn with a 1" radius

Apologies, if this more exciting to me than anyone else, and if this is boring data, but I felt it was "share worthy"
Wins feel good, even if they are small ones
 

Yep, that's it. Should be in ~/linuxcnc/nc_files/examples/remap-subroutines on your actual pc. Just know that it's changing the tool length offset (tool table Z) instead of the actual WCS Z offset. So you put the height of your tool setter above the machine bed in "probe HT" of the probe tab (leave "block HT" at 0 as mentioned before). Then you put the height of your workpiece above the machine bed in for your desired WCS Z offset. 

So example would be the toolsetter is 1 in above the machine bed and your stock top is 3 in above the machine bed. You set "probe HT" to 1 and your G5x Z offset to +3. You have to turn on the "tool measure" button in the probe tab and now when you run your program, the remap automatically takes over once the M6 line is reached and it will bring the spindle to your defined change position in your .ini, then after you change the tool and hit OK, it will drive over to the defined tool setter position in your .ini and probe the tool which will automatically fill in the tool length offset in the tool tab. Same diagram as figure 7 in section 14 of qtdragon docs, but "block height" is your g5x z offset. If you want to run without the remap, just turn off the "tool measure" button in the probe tab. It will still bring the spindle to the change position, but doesn't probe the tool and doesn't create a tool length offset. Nice thing about running the remap this way is it creates a universal tool measurement independent of the part setup allowing you to run multiple WCS offsets at once. 

You need to make sure your .ini has all the things shown in section 14.3.2 of the qt dragon docs for this to work. it's also very important to make sure you are using the qt_auto_probe_tool.ngc file from 2.9 and not the 2.10 master branch as the 2.10 version is different formula and won't work the same. Included my .ini, .hal, and personally modified .ngc remap if you want an example of what it looks like.  

wait, if Linuxcnc enables it, then can I start linuxcnc and then run mesaflash? we'll try it.

updated the old PC to a new one and linux and linuxcnc to the latest.

Found it !

github.com/LinuxCNC/linuxcnc/blob/v2.9.1..._auto_probe_tool.ngc

I don't think mesaflash has changed but rather your PC or BIOS

Did you just update to LinuxCNC 2.9 or did you change other hardware at the same time?

Thats what is exactly happening. So my options are get a new motherboard or put the 5i25 back in the old pc, and update the firmware in it. Also need to update the 7i77 firmware.

Will the 2.9 linuxcnc pc able to update the latest firmwares or is that verson of mesaflash too old?

rodw wrote:

That works. I run several versions of LinuxCNC as virtual machines at once in virsh during development/testing efforts. Virtualbox is great, too, but I got to fighting it all the time on my headless server. Virsh played nicer for me in configuring virtual machines on the headless server over ssh, then I connect with those VMs using Remmina remote desktop.

What does

lspci -v

report?

Is this a new motherboard?

I have seen this issue before where PCI devices are found but not enabled
(LinuxCNC enables disabled PCI devices but mesaflash does not)

The motherboard is using pcie to pci bridge. I am wondering if this is the issue. Mesaflash doesnt like i but linuxcnc doesnt mind. Just a thought.

Hi guys,

I have updated from 2.9 to the latest linuxcnc. It is running but two main issues one is the onboard 7i77 enc0 does not exist when it did before and mesaflash does not see the 5i25.

I assume the enc is related to the 5i25 and the 7i77 has old firmware message.

My question is Is it possible that the new mesaflash not see an old 5i25 card? and if not how to we get it updated?

Linuxcnc runs and see the 5i25 and everything seems to work except no enc0.

Thanks,
Bob

Bob
 

This repo is where probe basic et. al. live and it's been added as a convenience for users but its up to the qtpyvcp devs keep their repo current. I suspect its a transient issue from your message as I have not noticed issues here.

If you are not using any qtpyvcp stuff, you could delete the relevant qtpyvcp sources file in /etc/apt/sources.list.d
and do a sudo apt update

Hi RodW, yeah, sure. I am aware of that. The idea is just to get comfortable and experiment withe the Linuxcnc functionalities, configs etc.... of course later when I get all the stuff set up then will be a dedicated computer with real hardware.

qplasmac is a complicated GUI. Normally, it is set up assuming a mesa card using pncconf. 
I think I  would try running up pncconf and build a rough config for a 7i96s. You just need a template for all of the plasma specific pins so pick a mesa pin to use for each. don't worry about scaling the axes etc
Then I would copy the pin layout to your hal file and make sure any plasma  specific stuff in the ini file is copied to your ini file, then replace the Mesa pins with your lcec pins. 

With linuxcnc running open another window and type halcmcd show pin lcec should list all your Ethercat pins and you could probably filter out just the inputs or outputs

Also reviewing recent plasmac configs on the forum may help
I have one but its a very complex one with lots of custom stuff so would not recommend following it github.com/rodw-au/showstopper/tree/master 

In the qtplasmac GUI, there is a couple of fields for THCAD parameters. Set the offset to 0 and scale to 1 and use the actual torch volts. You may need to use mult2 to calculate the full scale voltage. Alternatively, use the scaling field which might be better.

Good luck