Advanced Search

Anyone?

One way:

in the main hal file add:


net spindle-vel-rpm hm2_[MESA](BOARD).0.encoder.00.velocity-rpm


in the gui hal file delete:

net spindle.0.revs  => qtpyvcp.spindle-encoder-rpm.in

and add:

net spindle-vel-rpm  => qtpyvcp.spindle-encoder-rpm.in

Hi guys, can't get spindle RPM to display, i have noticed a few different examples in the postgui.hal but non seem to work, i just get a -0 in my rpm display, I will attach my postgui.hal and my main.hal and a screenshot of halshow. Hopefully it's something very basic.thanks in advance

     

Yes, looks like an encoder issue of some kind (especially the sudden drop to 0 velocity)

I would try lowering  the emulated encoder output scale, as
maybe the drive has an issue with quadrature generation at high
speeds and high  resolutions.

Its probably easier to add the step/dir spindle to a MesaCT created configuration.

Can you post your MesaCT created hal/ini/io files?

No more than handful of lines need to be added.
 

I know - it is very unusual as a linuxcnc noob to start with an ethercat setup especially when you are en ethercat noob as well...
but I was so fascinated that I just wanted to give it a try.
Now I am at the point where Linuxcnc is installed, my ethercat is running and I get this terminal output:
0  0:0  OP      +  EK1100 EtherCAT-Koppler (2A E-Bus)
1  0:1  OP      +  EL1088 8Ch. Dig. Input 24V, 3ms, negative
2  0:2  OP      +  EL1008 8K. Dig. Eingang 24V, 3ms
3  0:3  OP      +  EL2008 8K. Dig. Ausgang 24V, 0.5A
4  0:4  OP      +  EL1008 8K. Dig. Eingang 24V, 3ms
5  0:5  OP      +  EL2008 8K. Dig. Ausgang 24V, 0.5A
6  0:6  SAFEOP  E  AS715N_sAxis_V0.10
7  0:7  SAFEOP  E  AS715N_sAxis_V0.10
8  0:8  SAFEOP  E  AS715N_sAxis_V0.10

As servos I use 3x Stepperonline OMC a6 400W

Now I tried to figure out how to build a working xml and a corresponding hal file.
After several hours of reading try`ll and error my last hope is that somebody of you would be so kind to share its xml and hal (best with running a6 servos) file so that I have a starting point for my setup.

Any help or hint is highly appreciated!

best

Kai

One: as you said... puff
Two: smd caps is faster to replace. I have to change nearly 30 caps each driver. So 90 in total.

When clipping the old one and soldering the smd on the other side directly on/over the drilled holes its a damn fast way. Cleaning the holes, soldering tantals in, clipping the wires taked more time...

So mainly cause I am lazy. And tantals costs (in comparable quality at my normal suppliers) round about 15 to 20 euros more than smd ceramics.

Tantalum caps are good.

Why the anti-tantalum mentality?

They do explode tho.

I once plugged in a tantalum cap the wrong way and it exploded shards into my fingers.

I'm fine tho.

It didn't break the skin.

You will want to qualify the analog jog with another button press. Both selected speed and analog stick need to be active for jog to occur.
Without this the machine will jog if the analog stick gets stuck at non-zero, which will happen when chips or dust get into the stick.  When this happens I take the joypad apart and blow it out with air. After 4-5 years of using joypads on three machines, I should probably ebay a spare.

yes that's it. Not sure why the .jpg nor .zip download doesn't work anymore.

If you add these two of these files to your postgui list, you don't need to make any changes to your main configuration .hal. The first file is joystick_jog_speed.hal. Next add _xz or _xyz for a xz lathe or xyz mill configuration.  You will also want _extras.hal as it lets you use btn-base and btn-top to go between manual and auto mode. Keeping all your joypad .hal in separate files helps keep track of changes and allows you to simply remove the joypad from a configuration is it's not available. These files have been used on many 2.9.x machines. (Small changes to several names with 2.8.x machines.)

 

As I said this is another story. I am familiar with this kind of stuff. No timing caps, no analogue circuits etc are involved. Just voltage stabilisation functions in this cases. And I just dont want to have tantals on the board as long as I dont have to.

Ah and of course. No charging cap and so on. So low esr isnt a problem here too.

But thank you nevertheless.

Beware of changing cap types!

Multilayer caramics can change capacitance with voltage and stuff.

And ceramic caps are microphonic.

Tantalum caps don't degrade with age, only due to electrical abuse (which they are very suceptible to). (overvoltage, reverse voltage, etc.).

Read this before changing cap types: www.ti.com/lit/an/slva214a/slva214a.pdf

Thank you for your input, but at this time nothing I seem to do works out right. I clearly am missing something but I do not know what that might be. It's wonderful that a new version has a button for using a manual tool gauge, however after trying to follow instructions from this post - www.forum.linuxcnc.org/38-general-linuxc...-do-i-update-to-2-10 - and having the first two things fail with - www.linuxcnc.org bookworm InRelease' doesn't have the component 'master-uspace - I do not dare go any further as I do not want to risk what is working now. It took weeks to get the machine running and I do not want to have to start from scratch again. For now, I can at least set my tool height each time I change a tool by use a shim on the work piece top. A bit of a PTA but better than nothing.

Can't find anyone who can " translate" the procedure mentioned by the author into " human" language?
is this a script?:
sed -i 's/inm.00/inmux.00/g' ~/linuxcnc/configs/<config name>/<config name>.hal

Where should I put " pncconffor7i95T.txt" ?
what is meant <config name>/<config name>.hal
how do I run the script ?

Because Glade has a gui editor, vs hand coding xml files like PYVCP, I think it is best to just start playing with it. Load some of the demo sim configurations, then open those glade gui files using the Glade Editor program to get a feel for how those files are built and then make modifications of them. Then try to build your own VCP window.

The GladeVCP documentation really gives the impression that you have to build and do a lot with a Python handler file but you can do quite a bit without really needing much if any of one. However there is a lot more that you can do with Glade and a Python handler, that you could never even think of doing with a simple PYVCP gui. To the extent of even building an entire stand alone gui for Linuxcnc.