Advanced Search

Das kleine Programm ist echt nett und hat mir viel Arbeit erspart. habe gestern ca. 5h damit gearbeitet, ohne dein Programm hätte ich viel länger gebraucht, jetzt muss ich noch die Daten aufbereiten und neu testen. DANKE für so ein cooles Programm.

Was mir aber beim Arbeiten aufgefallen ist.
1) Es werden nicht alle Einstellungen gespeichert.
Beim Neustart musste ich viele Ansichten neu holen, der Button für die Logen war nicht mehr da.
2) Beim Speichern habe ich keine Dateiänderung angegeben, das war für mich anfangs verwirrend, da das Programm dann einfach nichts macht.
3) Ich persönlich finde die Option "Move Type" an dieser Stelle unpassend und würde es lieber über oder unter dem LOG sehen.
Aber das ist Geschmackssache.
4) Da ich kein Englisch kann und alles über den Übersetzer mache, wäre eine Sprachdatei gut, dann könnte man alles in die jeweilige Sprache übersetzen.

Aber das ist nur meine Meinung, ich finde das Programm wirklich gut, es hat mir viel Arbeit erspart, DANEK !!!!!


Gruß Mücke
 

Hi All, 
I've started to build a retrofit system for a Cincinnati Sabre 500 milling machine, however now I've come across a more urgent job where I'd need to reasonably quickly convert one of my Mazak QT10 lathes, Both are known to have faults, I planned to repair them using the original Mazatrol T1 controllers, however the original parameter information and documents are missing from the machines. I have contacted the previous owner, despite his best efforts, he had decided to scrap the machines a week before I contacted him, and put the old manuals in the fire pit as he couldn't sell the machines. 
one machine has a tail stock, one doesn't. Both run ATC turrets 
unlucky for me! (I have an electronics engineer who would have helped repair the machines hardware faults) 
I'm now in the position, of what's going to be the quickest way to get them running,  
options -
1. Fit resolvers to the axis motors and run a Mesa board type setup - lots of custom config and wiring. (I see someone on here has done this on a Mazak before, a micro15, seemed very in depth to get it working) Seems controlling the original spindle wasn't to hard.
2. Fit 2 x new step/direction type servo motors and control it with a Pico systems step/direction controller. Jon has been very helpful with the setup on the milling machine to date.
3. Open to ideas! - the easier the better, I'm very electrically inclined but I'm a mechanic not an engineer

I have built a retrofit cnc controller previously for a stepper motor CNC router using UCCNC, I'm looking to have closed loop feedback on this machine if possible.
I appreciate any help anyone can give towards this subject! 

Check and make sure the directories are correct os the only thing i can think, loke i said i tested it here and it worked as expected. So im not sure why it wouldn't on your install.

AFAIK Sim is non-realtime by definition

Ok cool thanks... it is a HP4600 Workstation and it has a parallel port so it's I guess pretty old now... I might just do and image backup of this HHD and crack on using what I have.

do you have a good configuration for realtime sim config ?

I clicked on file and save or I hit ctrl+s on the keyboard. If I use "Save As..." it shows that the name it is saving to is probe_basic.ui is this the correct name?

It looks like you are running a non-realtime (sim) configuration



 

Team,
I need some help.  New to linuxcnd.    Linuxcnc  bookworm on N97 CPU, Mesa7i92TF,   fails to launch. 
Error "Unexpected realtime delay on task0 with period 1000000"
hm2/hm2_7i92.0 erro finishing write! iter=2219.

i did update the driver  r8168kdms,  disable cpu power saving mode ,  set - c state  at level 2.  Please
 

I just installed a new dev build from the Doc scripts and it is updating on save as expected. I would check your build, did you change the name when saving?

Yes, I use the launchers on the desktop, "Designer for PB Mill" and "Designer for PB Lathe", then launch LinuxCNC with "Probe Basic Mill" and "Probe Basic Lathe" launchers on the desktop.

It is also standard practice for cam software and tool length offset. Definitely need to change to standard practice, so reason to reinvent the wheel on this. With a work offset you will be setting zero wherever you want. But machine motion is always z moving down is negative direction.

You should switch your Z=0 direction.  Machine Z-0 (G53) should be at top of stroke (or furthest from chuck for lathes).

This is standard practice on most machines, and is compatible with the qtpyvcp/probe basic tool setter routines.

You can set your G54 (and other) WCS wherever you'd like, of course.

I like SSR's, but I don't trust them as main disconnect (i.e. Estop) devices.  SSR's tend to fail closed, not open.  Even if you don't use a dedicated, guided-contact estop relay, a magnetic contactor between your overcurrent protection device(s) and everything else is a safe bet.

Final suggestion - draw your wiring diagram before you settle on a control panel layout.  It will help you internalize what voltages go where so your layout makes sense.

Plenty of times I've had to add a relay, or stuff some un-accounted-for component because I hadn't finalized the wiring.  Or run out of field connectors for IO, or other dumb stuff - like switching from steppers to servos in the middle of a build.

Good point! I do have a handful of 40 amp solid state relays I didnt draw in there yet that I plan on adding for powering on and off along with a couple of switches. had a solidworks update but I'll redraw some stuff and post it again!

This panel will probably be behind the mill and I'll make a separate control panel where my computer sits that will have e-stop and the other goodies. Possibly something similar to this 3d printed estop switch combo that I made for a rocket thrust stand.
 

Seriously thank you all for the suggestions! always good to get another viewpoint!