Advanced Search

rebelx wrote:

Hi Tom, please let me know how I can send help! More coffee and pizza, or perhaps some nice beers? 

Thanks for the offer and sorry for the late reply.
If you figure out how to get more time out of a day, let me know, that is what i need most!
-
Rod is right, those optimizations are fairly narrow and in usual use not really impactful.
In general, by now all major distros are within several percent of each other in anything as far as speed is concerned, and so are in usability and stability, so here are some reasons why i use Mint for everything:
-fast boot time
-very stable and reliable
-even when i break something badly, it can be restored, always
-can run for months without a single issue
-Mate DE is not the most "user friendly", Gnome and KDE plasma are better for that
-Mate is not "touch" freindly, but it is better than Windoze and Gnome and KDE win here again
Why i do not like other distros:
-Debian has a nasty habit of stuff just stopping at random, mainly taskbar stuff
-Debian boot time has improved a lot, but not yet Mint times
-Tuxedo OS has issues with kernel licensing, it is very user friendly and reliable but just a bit heavier on resources, touch works out of the box, LinuxCNC needs a lot of cuddling to make work so does not pay off
-Fedora boots very slow, a bit sluggish on older hardware, quite good with touch, does not use DEB's, no LinuxCNC
-i will not use anything that does not open a terminal with CTRL+ALT+T !!!
-have not used Gentoo in ages, it was very fast and very stable, has issues with some hardware back then but mostly could be made to work.
-SlackWare was even faster than any of those, was a pain to setup but worked like a "nuclear powered battleship", no idea where it is now
-FreeBSD was similar to SlackWare and got better when PC-OS came out
-Porteus, Pupps, etc, are very good at what they do, and there is DebianDog Pup with older LinuxCNC

May I ask, why would you need 500V OVP? Pick a plasma and I dare you to find one with an open circuit voltage (OCV) over 400V, this would be the voltage without current flowing. No plasma in the cutting business will sustain a 400V arc length with a current capable of cutting metal. Plasma's used to cut metal, will typically not go much beyond 200V and the powermax type of stuff 150V (these are rough numbers). Then lets say you divide it by 20 (the lower one of your dividers) that's 20V.

Mesa that is connected directly to the raw arc voltage tolerating 500V is something that makes sense, my guess the 500V withstand voltage is the resistor max rating. Note this is not OVP, its what the pcb will withstand "forever".

Then if you are thinking about example beckhoff EL3064, it has an electrical isolation of 500V, but that's from the ADC to "LAN". I can't find a definitive max input voltage but i assume its the "Dielectric strength" of 30V, I find that to be weird terminology.

There is no point to over engineer this stuff. You can have safety margins, and you should, but reading an analog voltage that normally ranges from 0-5V, or even 0-10V, does not need to withstand x 10.

Thanks for the detailed answer. Its always a bit difficult to comment on projects you dont know about.

The asix chips look nice on paper but then again if you pair it with a MCU, how much benefits are there, I don't know? I was just wondering if there are benefits from the programming side so that it would make sense to use that instead of the LAN9252. I have 0 experience with the asix chips so I would love to hear from people that have used both.

Although both maybe available on aliexpress, I would say the LAN9252 is far more obtainable than the asix chips. I typically try to scan something like octoparts for any "special" components I might use, at least if there is even a small chance I make something more than one. A quick look and just digikey and mouser stock these in the thousands. I lost my mind on the chip shortage so now days I try to find multiple sources for parts and if I'm lucky multiple alternatives.

Good luck with your plasma build!

Humm,
Still needs thinking about. I can't click things fast with the interface. What would be nice is to be able to set the increment step live. The system can obviously handle large steps and do all its rate stuff but I can't supply a variable step.
I guess I'll have to get the git source to compile but I believe I need a 2.9 version to suit the Pi not bleeding edge so it might be a bit of a job to add and extra call into linuxcnc/src/emc/motion/command.c and then feed it back through the layers to a pin.
More head-banging to come I guess.

That makes sense.

Do you have any idea on how i could maybe debug what its stalling at?

Hello,

is the any way to change the network card driver from default generic to my hardware native e1000e when I install ethercat stuff from responsitories please? 

thanks regards

The problem with the latency tests is that they just test dispatch latency.
it's likely what you are seeing is some kind of resource contention.

I'm in the middle of doing the spindle encoder, waiting on parts, I'm having no luck with the ADUM1200 chips, you can only get the ADUM1201 already soldered on a breakout board. So you will need to to desolder the 1201 and solder on the ADUM 1200. I'm going to try a iso7740 next. If you look at past posts the pins which you can use as an encoder are listed. You will have to solder a jumper wire directly to one of the opticouplers that is used as an encoder input to bypass it. 

theres no usefull info in cmdline output.

I reimplemented latency-test directly into linuxcnc using the timedelta hal module and pyvcp.
And now i can see that the latency excursion occurs once exactly every 60 seconds but only while linuxcnc/axis itself is running never when only latency-test or any of the other latency testing programs are run.

linuxcnc just has to be running, it can be totaly idle and the excursion will occure.

Very strange and i dont know what to try from here

If you read on, it does go on to say in real world conditions, they could not see an improvement. Interesting article nonetheless.
 

Is this the original gmoccapy screen?

It stops doing this move.

- XY move (G53 X#1801 Y#1802 )