Advanced Search

I don't know if it's correct but I directly turn off the main power switch and everything goes off.

I've been wanting this to, so thanks for the input!....but.... how do you guys handle the shutting down process? Currently i'm quiting LinuxCNC with ctrl+q, going to Application-->Logoff in Debian and clicks Shutdown....waits untill the screen turns off and then flicking the main-switch on the machine.... is there a better way?

Hi,

I'm trying to setup the  Vers WLR v9 probe  and i got it working fine together with the Vers toolsetter. However, there is a pin out for errors. This triggers if there is issues with the communication for the probe(e.g. if it runs out of battery, is not turned on, communication fails and so), but how to configure this in HAL to halt the probe-cycle? First i thought about making some logic to check if motion-type is "probing" and combine that with the error pin. But the issue is the famous "one pin for all probing", so i don't think i "know" if i'm using the 3D probe and should monitor the error pin or i'm using the toolsetter and the 3D probe is intentional not active(causing the error-pin to trigger!). I've seen several posts about using M-codes to determine which probing cycle to run, but i've also seen people warn about this approach since it requires you to remember to use them each time....

Am i missing something obvious here or have others found a clever solution to this?

/Thomas

I believe that I have figured out my problem, however I don't quite know how to fix it. I'm using subroutines to perform different types of feature probing operations. An example program would look something like this:

preamble
o<probe_z> call [...]
o<probe_xy_boss> call []
end

When I load one of these gcode programs, I immediately get "unknown word starting with c" errors from the 3D plotter. It seems like the plotter isn't recognizing the syntax for named subroutines. If you ignore the error, then the first subroutine will run without issue. After the first probe is completed, the error will appear again for the second o code and terminate the program. I attempted to fix this by wrapping each call in a conditional like this:

o100 if [#<_task> EQ 1]
o<probe_z> call [...]
o100 endif
o101 if [#<_task> EQ 1]
o<probe_xy_boss> call []
o101 endif
end

This stopped any errors from appearing prior to cycle start. The first subroutine will execute without issue, and then the error will get triggered again immediately after the first probe. Limiting the file to a single subroutine solves the issue. The #<_task> wrapping method doesn't seem to work more than once in a file in this situation. I suspect that this has something to do with the fact that the first subroutine contains a probe operation which limits the lookahead of the controller's planner. Perhaps the backplotter is getting re-triggered after the first probe operation, but the machine is still in automatic mode since it's mid-file? Any ideas would be appreciated. I'm using probe-basic.

I am updating a grinding machine which only has the y and z axes controlled by a motor, the x axis is hydraulically driven with limit sensors, I already have the machine working with an old 5i23, I configured the x axis to not have errors in pncconf by configuring a linear encoder mounted on the x axis with the intention of being able to visualize them but when running a program it shows me a tracking error obviously given that there is no x movement command and the encoder starts to count, is it possible to disable the hili of the x axis only keeping the encoder count to be able to visualize the x axis on the screen? 
 

Danke tommy,

werde es nachher gleich probieren.

karlhe

Habe ich brobiert, leider nur freecad 0.2, nich 1.0

 

How did you create the config?
If using the wizard, there is "invert" on the right side of every pin, so check that for direction of the axis you need.
You can also edit the .ini file and add " - " (minus sign) in front of the SCALE value for the joints/axis you need to change direction.

Seen that a while back, it is a version of Voron 2.4 but bigger.
I have a bigger Voron with 10mm belts all over and i think i linked to files probably twice till now, they ar eon printables.com under the toma.3d name, just in case.

Glad you got it to work.
It errors for timing reasons it seems, the function get called before all the initiation is done.
After initiation then there is no more errors.
I ran your panel in master and it's the same.

You can quiet the message by changing the code in hal_actions.py

Anyone have a Lattice Diamond project for the Colorlight v8 board?

I bought the board and a HW-USBN-2A jtag programmer.. however, the litex .bit file generated doesn't seem to do anything.. no led activity, no button response, no serial output etc.

So just want to take a step back, and see if I a simple blink-led project, synthesized in Diamond works.
 

What version of linuxcnc are you using?
I like this idea and have it working in principle for master branch.

I just came across this today, very tempting. Albeit it needs some work.

We have been working on keyboard jogging for Flex GUI at the request of several people.

A test repo is here github.com/jethornton/flexgui2

JT

An input filter is not supported by Flex GUI at this time.

JT

I had this router working with Mach 3 and just swapped the Breakout board and LinuxPC.

The paraport wiring is the same and I put it into the step config the same way. I can jog the Z and X just fine, but since it is tandem Y, and that axis is last to home, I haven't gotten that far.

I just thought I would focus on the Z for now and get it to home upwards instead of down.

In Mach 3 I had put it set to home X and Y in negative direction. Z in Positive since it went from 0 to -150mm.

Any help is greatly appreciated!