Advanced Search

Sorry for the late reply.

Well, I should have respected the wisdom of the ancients: 'have you tried turning it off and on again?'.

I tried the MDI command and it worked. Then I reloaded the program and it worked, too. Nothing changed, just a reboot between the tries.

Thanks for your support!

Hallo,
in dem Vorschaufenster werden ja die Grenzwerte des G-Codes angezeigt. Das passt auch. Habe ich aber einen Werkzeugwechsel (M6) im G-Code passen die berechneten Grenzwerte überhaupt nicht mehr. (Über- oder Unterscheitung der Z-Grenzwerte) Ich verwende eine dynamische Werkzeugvermessung, ich meine das nennt man so. 
Alle Werkzeuge haben einen Längenverstatz von 0 in der Werkzeugtabelle. Da ich den Längenversatz vom ersten Werkzeug  zum zweiten erst weiß wenn ich das Werkzeug eingespannt und vermessen habe, sollte für die Berechnung der Grenzwerte und alles was in der M6 Routine steht nicht bewertet werden.
Ich meine was ich was gefunden hatte beim googeln, das man beim Aufruf von M6 mit einem Parameter unterbinden kann das der Inhalt von M6 nicht mit verwendet wird bei der Berechnung. Habe aber nie gefunden wie der Parameter heist und wo der eingetragen werden muss. Also hinter dem M6 oder ob das eine globale Einstellung z. B. in der ini ist.
Kurz zusammengefasst: Wie verhindere ich das der Aufruf von M6 die Grenzwertberechnung beeinflusst?

Without Tachometer feedback, the drives are running in torque mode.

There are a couple of options for controlling this:

1. Run as is with different tuning. For single loop torque control tuning is basically:

   A. Increase D term as far as possible until you get buzzing/hf oscillation
   B. Then increase the P term until you get instability and then back off to about 50% of that P value
   C. Increase the I term until you get instability and again back off on the I term about 50%

2. Use a spare analog output channel to simulate a tachometer so the drive itself can run in velocity mode

3. Use a dual PID loop control in LinuxCNC (inner velocity PID loop and outer position PID loop)

There are three hall sensor wires, which have been pre wired as i got the servos and drives as a set. i dont think this is the same as a tachometer?
There is also a 2000PPR encoder which is wired into the Mesa card

I bought e-cam or simplexcam (both the same with other names) a while ago. Now I have a lifetime licence with no subscription trash.

Unfortunately this goes back to work-in-progress state.
The normal arc voltage reader didn't give a reliable output during ohmic sensing.
I'll put in another voltage sensor, right over the 24V-ish supply to the torch and ground.

Klar, musst du nur an einem Digitaleingang an der 7i96 anschliessen.

Heres a quick code thrown together out of Fusion drilling and countersinking a hole. Do some research on G code and how to setup your tool offsets and work offsets. hopefully it gives an idea of the G code structure for you.

Yeah Autodesk sucks. I have 5+ years of programmed parts and custom posts at work. Now they are killing the software. I have fusion so at least I can use my custom posts if needed. they better figure out the ITAR crap for fusion before they totally kill my HSMworks..

Hello everyone
After doing some research, I managed to understand how communication works, and at the moment I have everything communicating as I want it to.
Now my question is why the Spindle tab is not active in the CT table. Is there a bug or am I just an amateur?
thanks

Hello, This is likely the wrong spot to ask this question, but as its one of the first things I've machined using linuxcnc on the machine...

The profile I've machined is essentially circular and should be symmetrical, and the bore clocks in at X0,Y0.
issuing a G0 X0, Y0 gets me back over the bore and it repeatably clocks in.
The finished machined part has a Y offset of 0.2mm.
This may be a programming issue, but I have noticed a random Y -28.11 offset in the tool table for the tool used.
If that entry was doing what I thought it should, then the mis-machining would have been 28.11 and not 0.2. However, could this entry have caused the issue?
On a three axis mill, is there a purpose for the X and Y offsets in the table?
Thanks

Hallo liebe Gemeinde
Der Nörgler ist wieder mit einen Problem da. Ich möchte den Werkzeug Längen Tester Innstallieren. Habe mir das Video von Talla83 angeschaut, dieser hat aber eine andere Mesa Karte gehabt. Kann man das auch für die Mesa 7i96s nehmen? das nächste wird noch da Handrad aber das muss ich erst besorgen (möchte es Kabellos machen daher ein China Produkt). Habe Peter (Talla83) angeschrieben aber keine Antwort bekommen.
Gruß und nochmal ein Danke für eure Hilfe.
Hans

3 BLDC on one TangNano9k
youtube.com/shorts/vBrvq76CJBk

This Benezan config looks correct:

 

Benezan breakouts have step/dir swapped but this version has
the ability to swap the default step/dir pins with a hal parameter

Yes - I hit power and lcnc thinks it is moving. The servo stays in PreOp. 
My mistake - the changed files were not copied into the folders. 
Now I have success - I have errors 
twopass:pass0: loadusr -W lcec_conf ethercat-conf.xml

twopass: load_the_modules cmd=<orig_loadrt motmod servo_period_nsec=1000000 num_joints=3 base_period_nsec=100000 servo_period_nsec=1000000 num_joints=3 unlock_joints_mask=16 num_dio=6 num_aio=3>
waitpid failed /usr/bin/rtapi_app motmod
/usr/bin/rtapi_app exited without becoming ready
insmod for motmod failed, returned -1


twopass: load_the_modules cmd=<orig_loadrt lcec>
waitpid failed /usr/bin/rtapi_app lcec
/usr/bin/rtapi_app exited without becoming ready
insmod for lcec failed, returned -1

Shutting down and cleaning up LinuxCNC...
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
cia402_homecomp: dlopen: /usr/lib/linuxcnc/modules/cia402_homecomp.so: cannot open shared object file: No such file or directory
<commandline>:0: waitpid failed /usr/bin/rtapi_app cia402_homecomp
<commandline>:0: /usr/bin/rtapi_app exited without becoming ready
<commandline>:0: insmod for cia402_homecomp failed, returned -1
motmod: dlopen: /usr/lib/linuxcnc/modules/motmod.so: undefined symbol: update_joint_homing_params
LinuxCNC Ethercat crashed with signal 11
-- STACK TRACE START
0    /usr/lib/linuxcnc/modules/lcec.so(+0xfc8c) [0x7feb9d9b0c8c]
1    /lib/x86_64-linux-gnu/libc.so.6(+0x3c050) [0x7feb9e68a050]
2    /lib/x86_64-linux-gnu/libethercat.so.1(ecrt_slave_config_pdos+0x2f) [0x7feb9d97452f]
3    /usr/lib/linuxcnc/modules/lcec.so(rtapi_app_main+0x40a) [0x7feb9d9b1f38]
4    /usr/bin/rtapi_app(+0x10cd7) [0x55e898f48cd7]
5    /usr/bin/rtapi_app(+0x1162e) [0x55e898f4962e]
6    /usr/bin/rtapi_app(+0x11c2c) [0x55e898f49c2c]
7    /usr/bin/rtapi_app(+0xc974) [0x55e898f44974]
8    /usr/bin/rtapi_app(main+0x70f) [0x55e898f4444f]
9    /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7feb9e67524a]
10    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7feb9e675305]
11    /usr/bin/rtapi_app(_start+0x21) [0x55e898f44861]
-- STACK TRACE END
Waiting for component 'cia402' to become ready........Waited 3 seconds for master.  giving up.
Note: Using POSIX realtime

6457
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
lcec: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
trivkins: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
tpmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
<commandline>:0: unloadrt failed
Note: Using POSIX realtime

Mmmhh - in my understanding just the cia402_homecomp.so is missing - could this be right?