Advanced Search

I have to ask one last question. I have been working with Inkscape to develop g codes from and svg drawing. Works great and would like to use for this however I can't get the g code size to match the size in the page. I have looked all over and don't seem to get a clear answer that really works. About ready to give this up, shouldn't be this hard. Must be missing something.
Any comments greatly appreciated.

So I did have that pulled up at one point. If I remember correctly it would turn on when I hit the home button but then would stay on until after it estopped and I relatched the machine it would turn off

To check homing to index, you need to halscope the index-enable signal.
The actual index signal is often too short for halscope to see.

LinuxCNC sets index-enable once is has detected the limit switch and the hardware
clears index-enable when the index is detected.

thanks

What exactly is BuildBot?

It is a PC/server that checks and builds the debs for various version of Linux architectures, after getting stuff from github, as far as i can gather.

We should say this more often:
Awesome work and a magnificent machine.

thanks

soooon

All squared up, few more mechanical things to do, and then a bit of electrical and getting linuxcnc to use modbus spindle control.

 

Well done sir

I've found a setup on the forums using Leadshine EL8 drivers and trying to work from there. Setup I'm following.
I've attached the hal, ini and ethercat.xml files. It doesn't load, I get the following error.


Not surprising as I've pruned the file down from 5 drives and a spindle to 1, different brand drives etc.

I've used the xml file that I generated.

Am I on the right track at all?[/code][/url]

well, I got totally nerd-sniped by this, so here we go: github.com/LinuxCNC/linuxcnc/pull/3587

Hit another little snag with the homing. I have it set up for index homing. I have the call out in the hal to enable it but in the halmeter I was trying to catch it hit the index but nothing popped up on the scope. I'm not sure if it is indicative of hitting the index but the x axis is very close to where it is home and each time I hit the home button it jogs either way towards it but then faults out with two "cannot unhome while homing" errors and usually a "joint0 following error." If I understand the following error that means it is not where the computer thinks it should be? I am considering bringing my actual oscilloscope out to the garage to watch the signal if I can't figure it out.

Ok, I feel a bit lost on how to proceed with actually getting my drive connected in HAL.
My previous machine was using MESA hardware and pncconf did most of the heavy lifting, at least giving me a working hal and ini file to work from. As it is I'm struggling to find good tutorials or videos online that actually spell out how to get an axis drive connected and a motor moving. The one video I found (showing a full setup from scratch) gets to the cia402 stage and just says "I wont go into detail on the cia402 setup" and then just shows a moving motor... which makes me think I'm missing something really obvious.

You can also follow the signal into the plasmac component.
​​​​plasmac.move_up and plasmac.move_down should be the same as your digital inputs.
If you want to see what the plasmac component does, it is only some 20 lines of code
github.com/LinuxCNC/linuxcnc/blob/master...s/plasmac.comp#L1911
the led up and led down reflect the move_up and move_down input to plasmac.
Can help to isolate the problem.

-Turn OFF the plasma
-draw a circle in the wizard, some 10cm diameter
-set the Proma THC150 to test mode with at least 5 seconds of time between changes
-put something about 3-5cm above the plate for the probing and remove after probe
-run the circle with the torch ON in QtPlasmaC
Do not turn the plasma ON while testing this.

The 7I95T identifies as a 7I95 (even in hal) mainly so 7I95 configs will work with it.