1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • Altenthaler1988
  • Altenthaler1988
06 Jul 2024 12:52
Replied by Altenthaler1988 on topic qtplasmac "torch not showing"

qtplasmac "torch not showing"

Category: Plasmac

 

File Attachment:

File Name: Plasma_V2....2.tar.gz
File Size:14 KB


So das müsste die richtige sein sry nochmal war gestern schon spät!
  • garthnoakes
  • garthnoakes
06 Jul 2024 12:51
Replied by garthnoakes on topic Driving relay using NO, COM and or NC

Driving relay using NO, COM and or NC

Category: Driver Boards

I think my board is faulty - getting nothing (AC or DC) from ground to the 5V connector. I've tested using ground/COM etc - all combinations. The relay light on the board switches on and off though. Going to order a new board - I want a spare anyway (I'm cutting several thousand pieces of foam)
  • Grotius
  • Grotius's Avatar
06 Jul 2024 12:50
Replied by Grotius on topic Trajectory Planner using Ruckig Lib

Trajectory Planner using Ruckig Lib

Category: General LinuxCNC Questions

1. Check if the first G01 command has I,J,K words
2a. if no then read the machine kinematics from the ini file and recalculate the tool vector from the ABC values
2b. if yes, use the IJK values to create the tool vector directly.

I think in my program if u have 5 axis gcode as you say that are only G0 or G1 segments.
Then parse I,J,K to letters A,B,C if a line has a G0 or G1. This could be done also by the 5 axis post processor.
The A,B,C are the tool vector. It doen's have to be a normalized vector.

Inside the program A, B, C has a transformation matrix, they are multiplied in order. Then multiplied by a tcp offset matrix.

For now to keep it simple..
Let's say we stick to the 6 axis machine configuration for now to solve the toolpath & tooldir optimalisation.
Then if this works, we can expand the code with different kinematic models.
  • Cant do this anymore bye all
  • Cant do this anymore bye all's Avatar
06 Jul 2024 12:34 - 06 Jul 2024 12:37
Replied by Cant do this anymore bye all on topic Driving relay using NO, COM and or NC

Driving relay using NO, COM and or NC

Category: Driver Boards

External Relay Yellow wire to +5v
External Relay Blue wire to on board relay NO if onboard relay turns external relay on
OR
External Relay Blue wire to on board relay NC if onboard relay turns external relay off
On board relay common to ground of the above +5v supply

Imagine the on board relay is a switch. Pretty much what I said in my first post, but now with colours
  • Grotius
  • Grotius's Avatar
06 Jul 2024 12:33
Replied by Grotius on topic Trajectory Planner using Ruckig Lib

Trajectory Planner using Ruckig Lib

Category: General LinuxCNC Questions

@Arciera,

Yes, that is because the 5axis CAM output only consists of straight line segments (ie no G02 or G03 commands) the CAM user defines the length of the line segments.

I wasn't aware off this. This makes things easyer.
But i think it's stupid to use no G2, G3 in 5 axis machine code.

--
We where wrong about connecting the ta knots with lines.
Proposing connect ta (tool dir points) knots with lines. :
 

The thin blue line is the recorded tooldir path:
 

I think we need to create the recordedb blue toolpath before program starts. Then create the fillets, like
sketched in the image.

This example uses gcode with no G64 fillets so far. This is just a example howto get where we want to.

Short movie how to tool tp and tool dir are recorded.


I will now try to create an idea to add clothoid fillets to the tool tp path and tool dir path.
 
  • Robbbbbb
  • Robbbbbb
06 Jul 2024 12:16
Replied by Robbbbbb on topic Position vs Velocity mode

Position vs Velocity mode

Category: EtherCAT

The problem with LCNC and ECAT is that the master which is lcec driver from EtherLabs has a lag over the true ethercat comm cycle. In their docs they show a .0005-.001 ms offset from the true 1 ms tick cycle required for true ether at frame rate. That means that the FB of position is at a lag. Therefore by the time the position is returned to LCNC and LCNC recalculates the new position and determines the error the data is outdated. So Lcnc will never be able to show the true error nor fully close the loop over ether at in the purest sense.

...

The other course of action would be to install a scale and set LCNC to use that position to monitor the actual position to derive error from. But it would be overkill and a waste.


With LCNC over ethercat think of LCNC as a GCODE sender kinda. The sender has no idea if the axis did its job for the most part and assumes it did. But since I have a really smart drive, my assumption can within solid parameters be correctly assume it did its job.

This is the best you will get with LCNC.
 

Maybe my use case is a bit different as it is on a milling machine which is comparatively slow compared to the numbers being mentioned in this thread. But at the 0.0005 - .001ms offset you mention at a 10000mm/min milling speed (max rapids in my case) would only result in a position deviation of 80~166nm!

My plan until reading this thread was to use the existing linear encoders on my mill to try and compensate for the cheap ballscrews it came with, using linuxcnc to close the loop (without spending thousands on drives that support linear encoders). I don't understand why that wouldn't work with ethercat? My existing linuxcnc control loop with my old stepper motors is 1ms so nothing has changed there, so what would I gain using for example a Mesa card and step/dir commands? The cheap servo I bought for testing cost the same as the non-ethercat version as far as I can see, so would be nice to make use of it if I can...

Thanks for all the info you're providing here, it helps with design decisions!
  • garthnoakes
  • garthnoakes
06 Jul 2024 12:16
Replied by garthnoakes on topic Driving relay using NO, COM and or NC

Driving relay using NO, COM and or NC

Category: Driver Boards

I found when I send an M3 and M5 that I can hear the onboard relay clicking on and off. So the config is correct (NO is pin 14) - I just dont know how to connect the onboard relay to the external relay
  • tjtr33
  • tjtr33's Avatar
06 Jul 2024 11:50
Replied by tjtr33 on topic Build 2.9 RIP in Debian 12 without Documents

Build 2.9 RIP in Debian 12 without Documents

Category: General LinuxCNC Questions

failed and the configurator said to add
--enable-non-distributable=yes
resulting in:

/configure --with-realtime=uspace --enable-build-documentation=no --enable-non-distributable=yes

which worked fine

HTH
tomp
  • garthnoakes
  • garthnoakes
06 Jul 2024 11:41
Replied by garthnoakes on topic Driving relay using NO, COM and or NC

Driving relay using NO, COM and or NC

Category: Driver Boards

I have this relay

www.amazon.com/gp/product/B01B60LPVK/ref..._title?ie=UTF8&psc=1

And this board

www.amazon.com/gp/product/B0093Y897A/ref..._title?ie=UTF8&psc=1

I've used X, Y, Z and A for the hot wire motors (XYUV), so besides the 5v and B output pins and the input pins, everything is used besides the NO/COM/NC connectors
  • Walkahz
  • Walkahz
06 Jul 2024 10:49
Replied by Walkahz on topic Deckel FP4 Gearbox Comp

Deckel FP4 Gearbox Comp

Category: Advanced Configuration

Not sure exactly how to open in comp.

Ive made a little progress.
I abandoned the modified Files I was using and went back to mark's files as downloaded from github.
i then have gone through to modify as required to remove the unneeded portions.
I was able to compile it and stopped getting the errors above when I uncomment the inputs and outputs, So the Hal is talking to the comp.
Still having a few problems but at least they are different. I was able to open LCNC but it opened very slow and showed a different version to what i have installed (2.4 rather than the 2.9 i have installed)
After some changes to the hal to try to identify the issue I was then once again unable to open LCNC  and had the following debug information come up.
2 steps forward 1 back.
Debug file information: Note: Using POSIX realtime rtapi_app: caught signal 11 - dumping core [Gmoccapy.QTVCP.QT_ISTAT][[33mWARNING[0m] INI Parsing Error, No DEFAULT_SPINDLE_0_SPEED Entry in DISPLAY, Using: 200 (qt_istat.py:532) [Gmoccapy.QTVCP.QT_ISTAT][[33mWARNING[0m] INI Parsing Error, No MIN_SPINDLE_0_SPEED Entry in DISPLAY, Using: 100 (qt_istat.py:532) [Gmoccapy.QTVCP.QT_ISTAT][[33mWARNING[0m] INI Parsing Error, No MAX_SPINDLE_0_SPEED Entry in DISPLAY, Using: 2500 (qt_istat.py:532) [Gmoccapy.QTVCP.QT_ISTAT][[33mWARNING[0m] INI Parsing Error, No MAX_SPINDLE_0_OVERRIDE Entry in DISPLAY, Using: 1 (qt_istat.py:532) [Gmoccapy.QTVCP.QT_ISTAT][[33mWARNING[0m] INI Parsing Error, No MIN_SPINDLE_0_OVERRIDE Entry in DISPLAY, Using: 0.5 (qt_istat.py:532) (gmoccapy:25734): Gtk-CRITICAL **: 06:32:40.415: gtk_entry_set_text: assertion 'text != NULL' failed [Gmoccapy.GMOCCAPY.GETINIINFO][[33mWARNING[0m] No DEFAULT_SPINDLE_SPEED entry found in [DISPLAY] of INI file (getiniinfo.py:282) Waiting for component 'inihal' to become ready. While waiting for 'inihal', component 'gmoccapy' loaded. Did you specify the correct name via 'loadusr -Wn'?.........................................................................................................................................................................................HAL: ERROR: exit called before init :0: waitpid failed milltask inihal :0: milltask exited without becoming ready [Gmoccapy][[33mWARNING[0m] No virtual keyboard installed, we checked for . Try 'sudo apt-get install onboard'. (gmoccapy:2080) Could not open command file 'gmoccapy_postgui.hal' 25678 Stopping realtime threads Unloading hal components Waited 3 seconds for master. giving up. Note: Using POSIX realtime mh400e_gearbox: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime mux16: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime classicladder_rt: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime pid: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime hm2_eth: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime hostmot2: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime motmod: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime trivkins: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime homemod: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 Note: Using POSIX realtime tpmod: not loaded :0: exit value: 255 :0: rmmod failed, returned -1 :0: unloadrt failed Note: Using POSIX realtime
  • Cant do this anymore bye all
  • Cant do this anymore bye all's Avatar
06 Jul 2024 10:28
Replied by Cant do this anymore bye all on topic Driving relay using NO, COM and or NC

Driving relay using NO, COM and or NC

Category: Driver Boards

NO,COM,NC are (usually) the switched side of the relay.
Where are the coil connections connected to ?

Could you do a quick sketch of how you've wired the relay, you're description isn't quite clear.

If you want to drive a relay via another relay, connect one of the coil terminals on the relay you want to dirve to the + power rail, the the other terminal to the NC or NO depending on whether activating the first relay turns the second relay on or off and connect the COM to the ground of the power supply that the coil of the second relay is connected to.
  • Aciera
  • Aciera's Avatar
06 Jul 2024 10:26
Replied by Aciera on topic Driving relay using NO, COM and or NC

Driving relay using NO, COM and or NC

Category: Driver Boards

=0.8em  It has NO, COM, NC connectors

Those would be the contactors for the signal you want to switch with the relay: NormalyOpen, COMmmonm NormalyClosed.
To switch the relay you need to apply a voltage to coil (usually A1 and A2)

 
  • rodw
  • rodw's Avatar
06 Jul 2024 09:50 - 06 Jul 2024 09:51
Replied by rodw on topic Position vs Velocity mode

Position vs Velocity mode

Category: EtherCAT

I found an example of said inertia, where I cut a small V shaped notch when plasma cutting a hook for a curtain rod to act as a fold mark.

Here the notch was deep enough to get to cut speed of 2.2 m/min before immediately reversing. Accelleration was probably 5 m/sec/sec (0.5G)

And I thought I had a stiff gantry!
 
  • garthnoakes
  • garthnoakes
06 Jul 2024 09:22
Driving relay using NO, COM and or NC was created by garthnoakes

Driving relay using NO, COM and or NC

Category: Driver Boards

I have a SainSmart 5 Axis Breakout Board for Stepper Motor Driver CNC Mill board.  I want to drive a hot wire relay with it.  It has NO, COM, NC connectors - how do I wire these to the relay, and how is Linuxcnc configured for this? I connected the inputs to ground and NO, but an M3 does not trigger the relay
  • phillc54
  • phillc54's Avatar
06 Jul 2024 09:00
Replied by phillc54 on topic qtplasmac "torch not showing"

qtplasmac "torch not showing"

Category: Plasmac

Dies ist zwar die richtige Vorgehensweise, der Inhalt der von Ihnen geposteten Datei entspricht jedoch nicht dem, was in einer Konfigurationssicherung erwartet wird.
Displaying 25141 - 25155 out of 25679 results.
  1. Forum
  3. Search
Time to create page: 0.743 seconds
Powered by Kunena Forum