Advanced Search

here are the pictures. the one with the white folding table background is the old one.   

Thank you. I am starting to feel like I really must have missed something obvious here...

PCW: no luck on the setpci option:

 

I might not be the best person to reply to this as i absolutely enjoy retrofitting and bringing back to life old machines, so i may be a bit on the "trigger happy" side, but:
-i would try to use the existing drives and motors and VFD/spindle
-seems like those are analog drives, so a Mesa 7i97T would do perfectly fine if you can find one, if not a 7i92T with 7i77 is the same thing, or if those are also scarce a 7i96S with 7i85 and 7i83 should do the same job.
-if you still want to replace the drives, you have two choices in general: EtherCAT or Mesa with normal step/dir or analog servos (do not bother to look at steppers and close loop steppers)
-You will be bombarded by others to choose EtherCAT, i am still avoiding them due to some fuzzy communication issues, but i will test them for sure the fist chance i get.
-For the Mesa/new drives, i would look for "position and velocity" mode drives (analog +-10V and step/dir) and also with encoder outputs (all have encoder inputs or absolute encoders, usually serial ones) so the loop can be closed in LinuxCNC with both types of control, makes life easier during use. Given the choice between analog and step/dir, choose step/dir.

Again the memory area is disabled, you might try the setpci option

Also, if Linux runs and accesses the card, you may be able to bypass the mesaflash issue with:

sudo mesaflash --recover --device recover  --write 5i25_7i77x2.bit

Take pictures of both cards and post them here, do not touch the jumpers.
Did you y any chance set them to "setup mode" or something like that? been to long so i am a bit fuzzy....

If the sim runs probe basic works. Your mqchine configuration was wrong.

As i stated in the fb group. You can i stall the deb with gdebi instead of using dpkg and it will find the missing dependencies. You seem to be making this much more difficult than it needs to be.

Once installed, run the probale basic sinulation from the Linuxcnc application chooser. That tells you definitively if the installation is correct. You should be able to run probasic take it out of e-stop select power Hit The ref all button and watch the Sim work if you can do this the installation is correct.

Now your actual EMCO configuration is wrong it needs to be fixed that will never run the way it is until you go through the machine configuration section of the docs in the pro basic documentation website and make sure that your machine configuration is set up correctly.

Like I said, clunks while moving an axis.
No Clunks or weird behaviour in still stand/idle.

I cant reproduce the issue sadly. Happens randomly.

So installed a new Debian 12 Bookworm Linux on a new SSD exactly as per instructions here:

kcjengr.github.io/probe_basic/probe_basi...develop_install.html

... and I cannot install LinuxCNC because:

dpkg: dependency problems prevent configuration of linuxcnc-uspace:
 linuxcnc-uspace depends on libboost-python1.74.0 (>= 1.74.0+ds1); however:
  Package libboost-python1.74.0 is not installed.
 linuxcnc-uspace depends on libboost-python1.74.0-py311; however:
  Package libboost-python1.74.0-py311 is not installed.
 linuxcnc-uspace depends on libgpiod2 (>= 1.5.1); however:
  Package libgpiod2 is not installed.
 linuxcnc-uspace depends on libmodbus5 (>= 3.1.4); however:
  Package libmodbus5 is not installed.
... etc

I have been round this loop before, which is why I installed the combined Bookwork and LinuxCNC package; but then Probe basic doesn't work.

Ok guys, 

• got a totally new PC (dell optiplex 5050)
• install a completely new image of linuxCNC
• put the 6i25 board in 
• The LSPCI command seems to find the board and the daym mesaflash still cant find the board!The PC is not hooked up to anything but power and internet. 
• Mesaflash is up to date...according to the Synaptic manager....(3.4.9)

 

what in the name of the gods am i doing wrong???? Please help

What LinuxCNC version is being run?

There was an encoder index bug fixed Nov 2022:

github.com/LinuxCNC/linuxcnc/commit/6bf6...afbf95c84f4fbb44f138
 

Hello,
I tested on an Orange Pi5 Plus and noticed that the jerk was not always maintained.

the ini and the nc code in the appendix.
In addition, an NC code generated by a CAM where the jerk is also not maintained.. 

Edits: Photo link updated:
-Wire labelling and diagramming under way.

****************************************************
Original post, minor edits for clarity.
****************************************************
Hi I think my machine is strictly speaking, a router, but its kinda beefy.
photos.app.goo.gl/pLPEiGzPKKzL9mCc6
I want to upgrade it to have a BC swivel head plus a couple of rotaries. This will involve adding a minimum of 4 servos. I need to rework the wires for sanity and the conduits need replacement (cracked, broken and generally worn). 

I think most of the connections are correct, but, it is clear that the machine has been tinkered with by someone who probably didn't pay a lot of attention to documentation or detail, so I think its important for me to double check connections.

As of now, I am thinking of:
(a) confirming that the Fagor controller works and put it for sale.
(b) Remove all wires one at a time, labelling then, and then migrating the entire contros to Linuxcnc, keeping drives where possible.
(c) Adding a second junction box so that I have more space for fingering
 
Power is a complete other discussion. I do not need a 16hp spindle. Have to confirm that it works, and then downsize. I also do not want a swivel head large enough to handle this massive spindle.

The goal is to have a machine that is a full-sized prototyper. I want it to have plenty of capabilities, but lower throughput. I'm doing higher value, highly customized, runs of 20 to 50 per part. Not more. This is not a run day and night auto-loader setup.

Please, would love some comments and general feedback. Happy to add pictures to the album. 
 

Manche Sachen muss ich noch machen Bsp: Beleuchtung des Bedienfeldes , dies sind alle Ausgänge der Mesa 7i73

Moin in die Runde,ich bin gerade dabei, meine Maho 500 W4 zu retrofiten und habe schon einiges geschafft, stehe aber bei ein paar Punkten auf dem Schlauch. Vielleicht kann mir ja hier jemand weiterhelfen oder mal über meine Konfiguration schauen.Bisher erledigt:

• PID-Tuning der Achsen gemacht
• KSS-Pumpe lässt sich ansteuern
• Werkzeugwechsel funktioniert
• Bedienfeld läuft soweit

Hardware:

• Achsen: über Indramat 3TRM2 mit analogen ±10 V Signalen
• Spindel: über Indramat 6TKR, ebenfalls analog ±10 V
• Mesa-Karten:
  • 7i97t
  • 7i74, daran hängt 7i84U
  • 7i73 fürs Bedienpanel

Meine Fragen / Probleme:

1. Spindel:
   • Ich habe versucht, die Spindel über Tipps von ChatGPT und verschiedenen Forenbeiträgen sauber einzustellen. Ich habe eine 2-Gang-Schaltung (bzw. 3, wenn man Neutral mitzählt), wie es auch User Dowerna in seiner Konfiguration gemacht hat.
   • Problem: Die Spindel dreht zwar, aber es läuft trotzdem nicht vernünftig – sie ruckelt beim Drehen und klingt alles andere als flüssig. Ich weiß nicht, wie ich das noch sauber hinbekommen soll.
2. Mesa-Konfiguration:
   • Ich verstehe nicht ganz, warum hier PWM-Gen-Pins genutzt werden und nicht die Analogen-Outs, obwohl die Mesa 7i97t 6 analoge Outputs hat.
3. Konfigurations-Check:
   • Kann mal jemand über meine Konfiguration schauen und mir sagen, ob das so passt oder ob manche Sachen besser gemacht werden könnten?
   • Beispiel: Ich habe die MPG.hal nach meinem Wissen angepasst, die funktioniert bisher sehr gut, aber vielleicht gibt es noch Optimierungspotenzial.

Freue mich über jeden Tipp oder Hinweis! Danke schon mal vorab.

Englisch below:
 Hey everyone,I’m currently retrofitting my Maho 500 W4 and have made good progress, but I’ve hit a few points where I’m stuck. Maybe someone here can help or take a look at my configuration.What I’ve done so far:

• Completed PID tuning for the axes
• CNC pump (KSS) can be controlled
• Tool change works
• Control panel is running fine

Hardware:

• Axes: controlled via Indramat 3TRM2 with analog ±10 V signals
• Spindle: controlled via Indramat 6TKR, also analog ±10 V
• Mesa cards:
  • 7i97t
  • 7i74, with 7i84U connected
  • 7i73 for the control panel

My questions / issues:

1. Spindle:
   • I’ve tried setting up the spindle using tips from ChatGPT and various forum posts. I have a 2-speed gear (or 3 if you count neutral), similar to the configuration from user Dowerna.
   • Problem: The spindle spins, but it’s still not running smoothly – it rubs/jerks while turning and doesn’t sound or feel fluid. I’m not sure how to fix it properly.
2. Mesa configuration:
   • I don’t quite understand why the PWM-Gen pins are being used for the spindle instead of the analog outputs, even though the Mesa 7i97t has 6 analog outputs.
3. Configuration check:
   • Can someone take a look at my configuration and let me know if it’s set up correctly, or if some things could be done better?
   • Example: I’ve adapted the MPG.hal as best I could, it works fine so far, but there might still be room for improvement.

I’d really appreciate any tips or advice! Thanks in advance.My configuration is linked below.

Working on a switchable kinematics for my lathe, using the millturn example on GH.

(more here:  forum.linuxcnc.org/10-advanced-configura...r-than-x-axis#344888 )

One part of the switchkins process are a pair of M-codes: M128 and M129.  I gather these are used to change the axis max/min limits when the respective joints are swapped.

Problem is I don't understand the Bash language/terms/syntax well enough to make sure I'm modifying it appropriately for my config.

Here's the full M128:


Question(s):

1.  Do I need to change (INI_FILE_NAME) to my particular ini file name, or is this some sort of 'points to the configuration's INI file regardless of name' programming thing?

2.  Under #RESTORE, there is the foreach | $coords... part.
- Does this call, or otherwise ensure, everything below applies to all values after set coords "x y z" at the top?

- Does set L [string toupper $l] somehow change the lowercase "x y z" to upper-case for use in the ::AXIS_[set L]... part?

- What is "catch"?

3.  Could this have been written more simply?
like: hal setp ini.x.min_limit [set ::AXIS_X(MIN_LIMIT)]

and repeated for desired axes?  With no "set coords" or "foreach" or "set L" needed?

Bonus Question:
- Other than to confuse non-programmers, what purpose does this complication serve?  Is the intent to make it so the end-user only has to change the coords "n n n" values and everything still works?