Advanced Search

Hi

Will there be a img for 2.9.3 for us raspbarry pi users ?
I am having issues with gmoccapy. 

please =) 

Thanks for all the great work
/Peter

Which board did you select?

JT

Updated to 2.9.3, looking better, even got the axes to move. Though, now when I try to modify the previously created configuration, I get the following error and can't proceed.

LinuxCNC Version: Master (2.9)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pncconf/pages.py", line 107, in
on_button_fwd_clicked
if not self(): # prepare returning True skips that page^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/pncconf/pages.py", line 1012, in mesa0_prepare
self.a.init_mesa_options(0)
File "/usr/bin/pncconf", line 2157, in init_mesa_options model.append((cur_firm,))
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 1016, in append
return self._do_insert(-1, row)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 1007, in _do_insert
row, columns = self._convert_row(row)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 899, in _convert_row
raise ValueError('row sequence has the incorrect number of elements') ValueError: row sequence has the incorrect number of elements

Lösche mal diese Zeile in deiner HAL

setp hm2_7i92.0.7i76.0.0.output-00 true

dann versuch mal im MDI die subroutinen aufzurufen:

o<Ventil_an> call

o<Ventil_aus> call
 

Ok, yes, manually you manage.
Question was: automatically.
-> Default behaviour in both Windows and MacOs,

Over travel in G38.x does not influence the stored position, it would be fairly useless if it did:

Thank you! I somehow missed (or forgot reading) the docs...

Depends on your Servo Thread, usually 1ms for a Mesa setup.

Yeah. I just found out that I mixed the times of the servo and base threads in my head So motion.probe-input is checked every 1ms. That means that I have to calculate how much distance the probe can travel in 1ms to see what's the expected error in my calculations.

Thank you all for your replies.

Ich habe das jetzt mal so probiert wie Talla83 das gemacht und @CHEROKEE-Laredo auf Seite 1 vorgeschlagen hat, allerdings in stark gekürzter Version, erstmal ohne irgendwelche Kontrollsignale und ohne T0, denn T0 habe ich am Werkzeugrevolver nicht.
In meiner Konfiguration wird auch die Pneumatik nicht geschaltet, weil ich das nicht hinbekomme, im Beispiel werden mit GPIOs die Signale ausgegeben, ich habe aber nur OUTPUTs (7i92TM+7i76+7i85) und so einiges damit versucht, aber es klappt nicht.
Mit der jetzigen Konfiguration und dem Aufruf in MDI von zB. "T1 M6" passiert nichts bzw. der Pfeil von "Aktuelle Datei ausführen" oben in der Leiste bleibt gedrückt. Unten steht auch weiterhin, Kein Werkzeug.

 

Die "toolchange.ngc" sieht so aus:

o<toolchange> sub
#4001=45
M61 Q#4999
o500 if[#<_current_tool> EQ #<_selected_tool>]
    (DEBUG,Tool bereits in Spindel)
o500 elseif [#<_current_tool> NE #<_selected_tool>]
    G0 W[#<_selected_tool> * #4001-#4001]
    M6 G43
    #4999=#5400
o500 endif
o<toolchange> endsub
m2

In der INI-Datei steht:

REMAP= M6 modalgroup=6 ngc=toolchange

In der "linuxcnc.var" wurde der Parameter #4999 eingefügt.

Wenn ich in MDI zB. "G0 W45" ausführe, dann dreht sich der Stepper, das funktioniert problemlos.

Um das Pneumatikventil zu schalten habe ich das hier gemacht:

"revolver_klemmen.ngc"

o<revolver_klemmen> sub
M65 P0            (Ausgang setzen Revolver klemmen)
o<revolver_klemmen> endsub
m2


"revolver_loesen.ngc"

o<revolver_loesen> sub
M64 P0                         (Ausgang setzen Revolver loesen)
o<revolver_loesen> endsub
m2

und in der "custom_postgui.hal":

# --- Werkzeug-Revolver loesen-spannen ---
setp hm2_7i92.0.7i76.0.0.output-00 true
net   wkz-rev-pneumatik  hm2_7i92.0.7i76.0.0.output-00  <= motion.digital-out-00

Warum funktioniert überhaupt nichts davon, wo liegen die Fehler?

Danke und Gruß
Olli

(every thread cycle; 25us by default?)

Depends on your Servo Thread, usually 1ms for a Mesa setup.

Over travel in G38.x does not influence the stored position, it would be fairly useless if it did:

After successful probing, parameters 5061 to 5069 will be set to the coordinates of X, Y, Z, A, B, C, U, V, W of the location of the controlled point at the time the probe changed state.

linuxcnc.org/docs/html/gcode/g-code.html#gcode:g38

Correct statement. The spindle requires indexing at 0deg before the probe tool be mounted and meas takes place. And ofc only effective in the angles the calibration is prog to be within. Best 'workaround' I found to address this delay/overtravel issue. Yet.

I don't know if the overtravel I'm observing is actually an issue, that's why I asked in the first place. If someone can confirm that the order of operations performed by LinuxCNC is as I understand them to be, it should not be an issue after all.

What I expect LinuxCNC to do:
- Check motion.probe-input as fast as possible (every thread cycle; 25us by default?)
- When the pin changes state, store the current position into #5061/etc.
- On the same cycle start decelerating.
- When the machine stops, finish G38.2 command and move on to the next command in the program.

Can you or somebody else confirm whether this is correct or wrong?

If it's correct, overtravel while decelerating should not be an issue, as far as I can tell, because the position I'm interested in is already recorded at the correct timestep.

Btw, are you Mecanix from cnczone forums? I found the thread about your probe and I was wondering if you ever measured its pretravel variation similar to how ZincBoy described in an old thread .

Does anyone have coreldraw and could draw me a small cdr testfile ?
without copyright ?
to include it in my git

just a few circles, lines and curves

Tanks,
Olli

forum.linuxcnc.org/9-installing-linuxcnc...ebian?start=0#305349

jdryg wrote:

Correct statement. The spindle requires indexing at 0deg before the probe tool be mounted and meas takes place. And ofc only effective in the angles the calibration is prog to be within. Best 'workaround' I found to address this delay/overtravel issue. Yet. 

You are 100% correct though. The Lcnc control could see improvement on the probing code (I recommend). I also run a 828 and 808 (sinumerik) and both sends the control into estop-like when the probe triggers, then reset. Not sure how that's done, slightly brutal on the mechanical but nonetheless there is zero overtravel. Saying estop-like here it could also well be disabling/enabling the drives too. 

Please update us on your progress. Subscribed, and thanks for raising this issue. 

Right. thanks.
done: github.com/kcjengr/probe_basic/issues/119

Out of curiosity: do you manage to have actual synchronization of remote shares on Linux file explorer without manually refreshing (either by F5 or going up a folder and down)?
Or is it just something that's not a thing?

You can change between 'Scarakins' and 'Identity' kinematics using the GUI button in the right panel or gcode commands 'M428' and 'M429'.