Advanced Search

When the jumpers are in the left hand position, /A /B /Z is a ground or should i wiring all 220 ohm resistor in ground (24V) ?

I'm a bit worn out right now, so I have no idea if this works on 2.7 but you can give this a go and have a look at 'mycomp.spindle-inhibit' pin in halshow:

To load this add this to your hal file

@Lcvette,

That is fantastic! 
Thanks. It's a lot off work. And coding into the linuxcnc source is not easy.

I see Probe Basic is a python hmi for linuxcnc.

Today i was working on hal-core , This is a hal environment.
It has a c++ hmi that now runs the nist rs274ngc interpreter.
The interpreter misses a few gcode commands like G64. Will add them with the G9.

The idea is to code both projects together to the finish line : linuxcnc & halcore

Halcore has less code overload, uses no python, has no code forest, is compact & fast.

Halcore now reads the gcode file trough the rs274 interpreter and shows the results in opencascade :


Halcore has no Milltask component. So i will create one for it, But will name it different.

I have a question about gcode file from robh:
In the gcode there are arc's that start with z value, then the arc uses a different end z value.
Plane is xy. This arc is a spiral? I never used a spiral before, but in this case opencascade has to draw a spiral i suppose?
Also trajectory interpolation model for a arc spiral has to be made then.

That is fantastic!  you just let me know when you need some testers and I will carve out the time. 
It will take some time for the next test on the production machine will be done.

also if there are any user buttons or anything that will be required for settings,
I think this can be done if everything works ok.
 

been a while.

FINALLY got the atc spindle onto this machine. still have some drive setting issues (i might need a different drive) but it works.



It turns out that while i though *some* of my various chatters from the machine were from the light duty spindle, it turns out almost ALL of them were. It cuts 3-4x more volume now despite having *less* power.

I have modified the source according to my MKS Tinybee board. And successfully compiled it, but didn't tested it. I have complied as default schematic of Tinybee. Using i2so for step/dir etc. and gpios for general input and outputs. Will this config work? It will be good board for linuxcnc with 5axis. 

Thanks for pointing me in the right direction. Will do.

First I think you need to add this as a userspace component.
Then you need to have a loop in there as otherwise it will simply run once and then disappear.

Have a look at 'Basic Usage':
linuxcnc.org/docs/2.7/html/hal/halmodule.html

[edit]
2.7 was before my time so things may have changed a bit but these days you would also want to poll the status channel in the loop so your getting up to date information

TO start with, I'm just trying to add the inhibit for tool 999.

Okay, I added:[DISPLAY]
USER_COMMAND_FILE=usercommand.py

As I am on LCNC 2.7 on the maho, I dont have spindle.0.inhibit, so I replaced that with motion.spindle.inhibit in my usercommand.py file.

#!/usr/bin/env python

prob_in_spindle = 0

def user_live_update():
global prob_in_spindle
#PROBE = T999 / T998
if s.tool_in_spindle == 998 or s.tool_in_spindle == 999:
prob_in_spindle = 1
hal.set_p('motion.spindle.inhibit','1')
else:
if prob_in_spindle == 1:
prob_in_spindle = 0
hal.set_p('motion.spindle.inhibit','0')

I have an INI entry:
[PYTHON]
PATH_PREPEND = python
TOPLEVEL = python/toplevel.py

I tried putting my usercommand.py in both the directory with the INI, and one down in the python directory. In both cases, there are no errors on start, but there is also no change in behaviour. It doesn't inhibit the spindle with T999 active.
I have struggle with this interface of multiple files and directories, and would appreciate your help pointing out which changes I need. Thanks.
Cheers,
Mark

ps... I wonder if my 2.7 Lcnc even has the global variable prob_in_spindle?


 

Greetings linux forum members,
I bought this cnc machine that I was told  was running off of Linux. Does any of the members recognize this machine? Any help with getting it running would be apreciated. I was going to run it on an Older Acer computer with the usb prot adapter since it dosent have a seriel port. The Acer computer has 4 gb of ram storage.
CJ Cappella

This homing is for absolute encoder (single turn)?
For servo motors with multi-turn absolute encoder linuxcnc just takes current shaft position ?

Also, you might want to test the switching of the DEFAULT/CUSTOM homing routine with 'home_offset' = 0
This should make debugging a bit more straight forward.

Hi everyone

How have you resolved your ENA output on NVEMv5 board in linuxcnc HAL file and in config.txt if different?
I have tried OUT1 on remora.output.00 and @cakeslob help with no success.
Could this work on Aaxis outputs pins.

Hi Tommylight, thanks for the response.
I did what you indicated, I created the file in stepconf of Linuxcnc 2.9.2 and replaced the files in the old version (2.8.4) of Linuxcnc, but Axis does not open, there must probably be something incompatible between the HAL and INI files.
I tried to copy Stepconf from the newer version of Linuxcnc and run it on the old version, it didn't work either.
I verified that the Stepconf of the most current version runs in Python3, however in Debian Wheezy there is no 'native' Python3, only the previous versions.
Is there any other alternative for me to try?
Thanks again for the help.

Oops, after all of that I realize that I used underscore instead of hyphen in the homing pin names.
My appologies I'll have to fix that, or your hal entries wont work.

[edit]

Ok, I fixed the halpin names in the component posted above and also the screen shots. So make sure to download the fixed component and install it again.

Nice idea. Will try to see if I can do something with it.