Advanced Search

Yes, that is exactly what I'm after.

Yes, I have full control over the HAL files. I have actually got it to "work" decent, but it's a bit ugly. I convert both the park and follow command from the qtvcp panel, as well as the digital-out HAL pin to pulses with edge HAL components. The pulses go into or2 components. This way I have one "set" (track) command and one "reset" (park) command, but those are just pulses. I feed those signals into a flipflop component that is then actually controlling the shoe movement. See attached schematic. "ds" is my qtvcp panel, so ds.track and ds.park is the momentary panel buttons. text on the lines are the net names, text over the blocks are the component name. 

It's working, but I get into the situation that the motion.digital-out pin is not reflecting the status of the shoe if overriding it from the panel. It actually is a minor thing, as my M6 remap always park and then activating the shoe again. But I would like to have the motion pin reflecting actual state, just for sanity

edit: adding the attachement
 

Hallo Pascal,

ich hatte zu dem Zeitpunkt noch nicht das Verständnis, wie das alles ineinander greift. Inzwischen bin ich soweit, dass ich die Motoren ansteuern kann.

Allerdings stolpere ich aktuell darüber, dass ich die Fräse (bzw. meinen Testaufbau) noch nicht in den "normalen" Zustand schalten kann. Ich habe ja einen Gantry Aufbau mit zwei Servos für die X-Achse. Allerdings kann ich in der Oberfläche bisher nur einzelne Motoren und keine Achsen auswählen.
Ich nehme an, dass das daran liegt, dass die Referenzierung noch nicht funktioniert.

Bevor ich mich allerdings um die Referenzierung kümmern kann, muss ich noch die Parametrierung machen, da die Servos aktuell zum Zittern neigen, sobald sie auch nur ein winziges Stück bewegt wurden.  Zwei Adapterkabel dazu habe ich inzwischen angefertigt, bin aber noch nicht dazu gekommen, die Parametrierung auch vorzunehmen.

Schönen Gruß,

Uwe

You can set do 'setp' command while linuxcnc is running via halcmd i think.
open a terminal and write halcmd -k (double check this syntax)

linuxcnc.org/docs/html/man/man1/halcmd.1.html

I think you can set set via bash commands, i haven't tried though
I think you make a file with your command and call it trough a custom Mcode.

in the file:
#!/bin/bash
# M101 - some command
halcmd setp parport.0.pin-XX-out true


There is some more steps to this. I think you need to ad a new new Mcode is the ini file RS274NGC section.

I hope this gives you enough to keywords to search.

/Peter

So m65 commands operate a dust cover and you want to override the controls manually while in auto mode?

You can control m65 directly while in auto mode other then with gcode.
But could you put some logic components between motion pins and the dust control pins that the control panel can control. Something like an OR component?

A real noob on qtvcp I will say

From a qtvcp panel, is it possible to modify the motion.digital-out-xx HAL pins with M62-M65 during AUTO mode, as in when the machine is cutting, without going into MDI mode?

I would like this to have the ability to manually raise or park a Z independent dust shoe during cutting. The dust shoe is normally controlled with M62-65 during tool changes.

Thank you. I will look into this. I'll post what version of GUI I'm using when I can.

Almost certainly, provided it is capable of accepting either analog velocity or torque commands, or digital positioning commands (step/dir or quadrature.) or can do EtherCAT.

What size piece gives your 0.75" larger, or is the oversizing pretty consistently the same amount regardless of the size of the item or is it a proportional oversizing (bigger pieces off more smaller pieces off less?

Are you using tool diameter offsets? One possibility would be if you have your CAM program generating the tool path with tool offset, but are also using an additional tool offset in Linuxcnc.

How did you determine your step scaling? Did you calculate it from the drive mechanics, or did you use experimentation? (Measure a feed move and adjust the scale to get the size move you wanted.)

If you used experimentation and the system was loosing steps for some reason, This can give a fairly consistent offset in size variation for each move.

OK Leistung ist OK,
Andere Probleme können die Verkabelung oder die HAL-Datei sein Wo wird das 7I84U angeschlossen?

Mangelnde Kommunikation kann ein Verkabelungsproblem mit dem Kabel sein
oder dass der verwendete Kanal in der HAL-Datei nicht aktiviert ist

I made the config with PnCconf and only slightly changed to to account for probe basic interface.
the inductive endstops are mounted on the traveling part of the axis and there are metal stops at each end of the travel.

the machine has the following specs:
Machine Specs:
X460, Y750mm, Z160
20mm linear rails
10mm pitch ballscrews, 20mm diameter
Construction: aluminum profiles bolted to 12mm steel plates, welded gantry sides
Motors: Y-axis 6.8Nm stepper, Z + X-axis 3Nm stepper
Drives: DM556 V1 48v
Spindle: 24K RPM 2.2kW ER20
inductive endstops
good latency values mostly sub 3000ns servo

Hallo Peter
Ich habe die 7i84u Pin 1,2,4,4 mit 24 V + und Pin 8 GND Verbunden
beim einschalten brennt CR 5 Rot, CR 2 und Cr 7 gelb
wo liegt der Fehler

mfg
Hilton

Hi..after calibrating x,y,z axis pretty close...I run file (see attached)..and the part comes out about .75" larger than what was generated in cambam..
not sure what is happening here....

Thanks for any help..
Rick

I think that this would best be done in the GUI.
Which GUI are you using?

You _could_ use the "message" component to pop up the message when any HAL pin indicates "homing" but blocking the homing until the OK button is pressed would be harder.

linuxcnc.org/docs/stable/html/man/man9/message.9.html

A custom python component might be able to monitor homing state, pop up the message and also inhibit motion until OK is pressed.

I don't know if set_feed_hold or maxvel affect homing moves.
linuxcnc.org/docs/stable/html/config/pyt...command_code_methods

It _might_ suffice to automatically send a tool unload as the flag to indicate that a tool length check is needed.
Then maybe remap the S-word such that the system aborts with a message if there is an attempt to start the spindle when the tool-number is zero.

It might be possible to detect a tool change by watching the spindle encoder position. If it moves with the spindle off, then it's likely to be a tool change (especially if it moves backwards)

Can i use this ac servo motor for 
building my mini diy linux ethercat CNC?