Advanced Search

MarkoPolo wrote:

....it should be "qtvcp"

Moved, thank you.

Yup, that might be it, did not check the category or previous posts.
Still, might be very useful to someone, i use it on all my machines.

So habe heute mal auf deutsch gestellt und habe gleich wieder das selbe problem.
Der Befehl war 
sudo localectl set-locale LANG=de_DE.UTF-8
wieder auf sudo localectl set-locale LANG=en_US.UTF-8 und alles geht wieder

have you checked if 'hm2_7i76e.0.7i76.0.0.spinout' changes it's value when the spindle speed is changed with hm2_7i76e.0.7i76.0.0.spinout = true?

If that is the case then you would need a voltmeter to check the voltage on the VFD 'AVI' input.

Hello Everyone,

I was trying different suggestions as per post replies but not getting foolproof system. However I was monitoring Hal configuration. I found one pin "lcec.0.0.drivestatus-0" which is representing drive OP state. This pin goes high when drive is healthy and is in OP state.
I have already configured Axis Fault alarm to "lcec.0.0.drivestatus.3" because it is going low when drive is healthy and there is no alarm.

Now, do I need to invert "lcec.0.0.drivestatus-0" ? How it can be done? And if there is other option to link this pin with Emergency or even axis limit(ghetto idea) or anything which prevents EMC power-on(Servo-On)

Or may be more reliable setup
Check drive status
If ok then only power On, or else alarm
Check Servo On
If ok then only power on or else alarm


Thanks in Advance.       

I tried your recommendation, but wasn't working. After several try and error I'm now able to turn on/off the spindle by LINUXCNC. The wiring looks like this

Mesa <=> VFD
Dir + +12V
Dir - FWD
En +
En -
nc
SPI + +10V
SPI OP AVI
SPI - COM

The next challenge is the spindle speed adaption. At the moment is only full speed possible. I've added the following to my INI and HAL files (not sure if it makes sense)

INI
MAX_OUTPUT = 20000
OUTPUT_MIN_LIMIT = 6000
OUTPUT_MAX_LIMIT = 20000
OUTPUT_SCALE = 100

HAL
net spindle-cw => hm2_7i76e.0.7i76.0.0.spindir
#net spindle-ccw => hm2_7i96s.0.ssr.00.out-01
net spindle-enable => hm2_7i76e.0.7i76.0.0.spinena
net spindle-vel-cmd-rpm => hm2_7i76e.0.7i76.0.0.spinout

setp hm2_7i76e.0.7i76.0.0.spinout-scalemax [SPINDLE_0]MAX_OUTPUT

sets spindle-at-speed true

setp hm2_7i76e.0.7i76.0.0.spinout-minlim [SPINDLE_0]OUTPUT_MIN_LIMIT
setp hm2_7i76e.0.7i76.0.0.spinout-maxlim [SPINDLE_0]OUTPUT_MAX_LIMIT
setp hm2_7i76e.0.7i76.0.0.spinout-scalemax [SPINDLE_0]OUTPUT_SCALE

You put the topic in the wrong category, it should be "qtvcp"
What version of qtdragon are you using, is there such a variable in the qtdragon_hadler.py file "self.factor = 1.0"?

tommylight: I think they are talking about a specific startup issue with the EtherCAT
Lichuan drive.

I would probably start with a pncconf configuration file set
made for a 5I25 + G540. I would set the number of stepgens and
encoders to 2. Then select "accept component changes" and assign
your stepgens and encoders to the desired axis. Finally hand edit the
resulting hal/ini files to deal with the card differences. (mainly GPIO settings
for limit switches etc)

Edit: You may need to add an additional PWMgen or stepgen for controlling the spindle
and additional encoder for the spindle.

Darium wrote:

Has anyone solve "the start lcnc before plug in ethernet cable" issue yet?

From PCW:Edit the IP and the location as needed, save to a text file with whatever name .sh, make the file executable in properties.

like here:

 

Has anyone solve "the start lcnc before plug in ethernet cable" issue yet?
i have the same thing but my driver are lichuan closed loop stepper CL3-E86H
I got it to run but still have to do the ritual every times I turn on the machine

Hm, seems to me that the recorded (blue) path deviates quite significantly from the displayed smoothed tool direction path.

Nur einfach die zwei Zeilen in der ini einfügen wird nicht reichen. Du müsstest 'Probe Screen' auch noch installieren:

für linuxcnc 2.8 könnte das hier helfen:
github.com/linuxcnc-probe-screen/probe-screen-ng

für 2.9 schau mal hier (das ist dann aber wirklich nicht mehr anfängerfreudlich)
forum.linuxcnc.org/49-basic-configuratio...obe?start=650#277215

Alternativ mal die QtDragon GUI ausprobieren, dort ist Probing schon mit eingebaut.

Ok,

Now it follows the tooldir path.