Advanced Search

Hey guys. I wonder if someone could assist me in nutting a problem in my configuration. I know the layout of the config has more than one problem, and i plan to learn better how to fix this myself, however as long as i have the axis' dialled in and the servo spindle controlled through the software i am a-ok with not having spindle orientation and extras setup until I better understand the Hal configurations. 

I have been running Probe Basic as a 3 axis stepper driven mill configuration, 3 homing switches for a year using the standard mill motor spindle and that has worked fine. I have just installed a Servo Motor to drive the spindle and now for some reason I am getting a joint following error when homing any axis. 

I have had the servo spindle working in a test file, (both Axis and probe basic GUIs),but when combined together in the previously working Probe Basic config I have issues. 

I have a feeling it might be something that is related to the post-gui file, as in an attempt to chase errors I was getting I have consolidated a not task that was conflicting, and I have reached to end of my limited knowledge.

I am working regularly to better understand the control flow within linuxcnc, but for now, if i was just able to get a minimal running configuration sorted I could at least use the machine whilst i gain that better knowledge. 

Thanks very much,
Bruno

I finally gave up. I have spend hours and hours trying to find out why my motor stall. I even contacted the manufacture of the drives and motors with no success. I replaced all wires,motors, drives, added ferrite cores,.... There is almost nothing I have not tested.

I am convinced it has nothing to do with the Rio software. But the tang vs parallel port makes the difference. The signal after the BOB comes out with less noise when I run it from the parallel port as when I have the tang connected. I don't know why and I don't know why my DM332T don't make an issue either way, but the Microkinetics does.

I will order a new drive, but that opens up a new can of worms and I may upgrade directly to servo drives...

The attached control circuit will disable the spindle and servos of the machine if an Estop push button (PB) is pressed or change tool is requested. The arrangement is combination of both software and external hardwired circuit.

To stop any movement of the machine, the approach uses estop and reset pins of the halui component and redundant hardwired external circuit to disable any movement of the machine. The interface between the software and the hardwired circuit is done through digital I/O (2 or 3 inputs and two outputs).

Operation of this system is follows:
If an Estop PB is activated or tool change is requested machine will go into an Estop state.

• If only Estop is activated, operator is required to press push button reset to enable spindle and servos
• If tool change is requested, operator is required to change the tool, press tool changed PB (either hardwired or UI) and press reset PB to reset the estop and continue operation. (I know operators don’t like to press two buttons sequentially in certain order, but for their hands and fingers sake the extra mental challenge makes it worthwhile, I think!.

On the left side of the sheet is the electrical schematic. Showing use 5 relays. If you decide to use this circuit you need to determine the number of contacts normally open and normally closed before ordering the relays. The MCR contacts connection to servos and VFD are hardware dependent (if you need help with this part of the diagram ask)

On the right side is a postgui block diagram reflecting net listing of hal file see below.

 

#

---

# Load realtime Components and their counts

loadrt and2         count= 2
loadrt flipflop     count= 1
loadrt or2          count= 1

#

---

# Add functions to threads

addf and2.0                   servo-thread 
addf and2.1                   servo-thread 
addf flipflop.0               servo-thread 
addf or2.0                    servo-thread 

#

---

# Connect Pins with Wires

#     signal/wire                 connected Pins
#--+

---

+

---

net estop.activate.sig     halui.estop.activate  and2.1.in1  flipflop.0.out  
net estop.is-activated.sig halui.estop.is-activated  and2.0.in1  flipflop.0.reset  hm2-7i92.0.7i77.0.0.output-00  
net estop.reset.sig        halui.estop.reset  and2.0.out  
net external.reset         and2.0.in0  hm2-7i92.0.7i77.0.0.input-01  
net external=estop         flipflop.0.set  hm2-7i92.0.7i77.0.0.input-00  
net t.prepare.loop         iocontrol.0.tool-prepared  iocontrol.0.tool-prepare  
net t.xch.done             hal_manualtoolchange.changed  iocontrol.0.tool-changed  
net tool-changed           or2.0.in0  
net tool-xch.request       hal_manualtoolchange.change  iocontrol.0.tool-change  hm2-7i92.0.7i77.0.0.output-01  
net tool.changed           or2.0.out  and2.1.in0  
net tool.changed.button    hal_manualtoolchange.change_button  and2.1.out  
net tool.number            hal_manualtoolchange.number  iocontrol.0.tool-prep-number  
net ui.tool.change.pb      or2.0.in1  

cmorley wrote:

Gcode properties are generated in Gremlin and then sent out using Gstat messages to whomever is connected in that GSTAT python instance context.

line change messages come from linuxcnc status, which is available in every GSTAT python instance.

So if your vcp has no gremlin then it gets no gcode properties message.

If I add a Gremlin object to the Glade file, then I get the G-code properties, nice. Thanks for that hint

cmorley wrote:

I have a hunch that is why you get a 'file-changed' message on reload, but would have to test to confirm.

Chris

I am looking forward to your idea..

is it possible you need:

loadrt trivkins coordinates=xyzy kinstype=b

I can reproduce it by running Gmoccapy from LinuxCNC 2.10 with a pref file which is created by 2.9 or earlier, so it has lowercase names for "system_name_gxx" and so on. After that, entries like "system_name_G5x = G5x" are added additionally to the existent "system_name_g5x = G5x".
If you try to run that with 2.9, it gives the duplicate settings error.
Now come the weird thing: Gmoccapy from LinuxCNC 2.10 works with the duplicate settings because it only takes those ones with the capital letter.

Internally Gmoccapy works with the capital letter, so "system_name_G5x", "Gtk_theme" and so on.
In 2.9 the configparser does convert the settings name to lowercase and the same configparser on the same pc but in a 2.10 environment does not sonvert it and write the capital letter. I have really no idea why the configparser does now take capitals into account.

However I provided a fix here: github.com/LinuxCNC/linuxcnc/pull/3181


 

I'm in the process of remapping  M6 , and I'd like to do the same as GuiHue (forum.linuxcnc.org/49-basic-configuratio...et-coordinates-found).
I have modified the program so that it corresponds to my machine and without use probe.
The automatic change tool works but I can't get the manual tool change part to work.

I'm having problems with this part

no window appears (on axis) asking me to remove the old tool or insert the new tool.

I think this is due to my hal

My hal


when I use "external manual tool change dialog" the message appears but my automatic part no longer works.
what should i reactivate?

Great, thank you. I will flash it tomorrow morning and see what I can figure out. 

 

I discovered Flex GUI by chance with this post, it's a great job, thank you very much.

The last line, which says to look at the exampleconfig a gantry machine, was also only semi helpful since 1. This example config wasn't even available on my variant of linuxcnc, and 2. Since there is nothing helpful in the example config,

Not sure why that should not be available on your installation:
github.com/LinuxCNC/linuxcnc/tree/2.9/configs/sim/axis/gantry

However your issue is not 'joint' jogging but axis jogging as your machine seems to home correctly.

If you do get the step/rid servos, they will have encoder wired to their drives, so you can look at it a simple stepper system, and if you can use the scales wired to LinuxCNC, that would also close the loop in LinuxCNC, making any backlash in the system less impactful. This from LinuxCNC's point of view makes it velocity mode where LinuxCNC controls the position.
That can all be done with 7i96S and 7i85.

I'll have a look, I can't remember. I did start with RT-Prempt but latency was poor.

I'll have a go at a fresh pull, or git checkout your updated work. I'm so worried to over-write anything though, not because I doubt any of you beyond incredible talent and knowledge, but because the existing version I've rooted for is flawless. Spi W5500 + gowin that is. I actually made quite a few parts before leaving, Nothing to regret having jumped in!!

Always good to keep updated and in the loop anyway, so I'll do that. You sound good man, good vibes, Keep it up!

Gitano's creativity is great. Doesn't look Cult'ish enough though, he needs a tattoo + blink one of his eye and it's sorted

Hi Guys!
I started a new project, a retrofit of a Hermle UWF 700. It was made in 1984, 40 years ago. The mechanical condition is very good, no signs of wear anywhere, although that might also be due to the automatic lubricator. The mill has a 18-speed gearbox, maxing out at 2000rpm's. The electronics were not working anymore, so I only got the machine itself. I did get a lot of nice documentation however. Tool clamping works by a hydraulic cylinder. The gears are lubricated with an oil spray system with a seperate oil pump.This is what the Hermle looks like: 

 

And inside my small shed:



The ways still look pretty good:



I paid 2000€ for it, which seems fine.

My Plans:

• I want to use Servos for the three axis. I am currently thinking about 660 Watt JMC servos or some chinese ones, since I can not get my hands on anything else.
• The machine already has glass scales on all three axis. I think it should be possible to use them with a mesa board if I use three Heidenhain EXE 602 E and use them as feedback in a PID loop.
• I have a 7i96s with a 7i85, which could be able to do the trick If I use the step/dir interface of the servos, which only works in positional mode. But I read multiple times here on the forum that velocity mode is better. Otherwise I will buy something like the 7i97T.
• I might increase the low spindle speed by using a belt drive, at least 4000rpm would be nice.
• I might use an Arduino to shift the 18 gears of the gearbox. That seems simpler to me rather than using LinuxCNC to handle the shifting.

I will post updates from time to time.

Manuel

Also I don't think pncconf supports the 7I95/7I95T but MesaCT does.