Advanced Search

Sorry, due to my personal technical reasons, the detailed explanation of this issue will be very verbose.
In fact, I have made a detailed list of pins. Derived from idx00~31, the test results are the same. Additionally, I also tested other models of modules, and the xml used was almost exactly the same, but the test results were fine. Meanwhile, I received a message in other communities: Someone used the module of the same brand (with a different model), and the test results were fine.
I have recently conducted more module tests made in China and discovered some patterns. I will release the results later.
The current apparent result is that for the module I mentioned above, Linuxcnc can only read 16-bit data originated from ethercat PDO. Even for a data range of 32 bits.
Here are some examples: Please look at the picture
For this kind of problem, I plan to conduct network data packet analysis later. Later, I will provide detailed network data results. Thank you all.

I guess one of theses days I will have to give that one a go.

In a terminal one line at a time

Moved to "driver boards".
-
While waiting, you can use 7i84 OR 7i73 with 7i97T for testing or anything, without the 7i74, meaning only one at a time.

Link i posted has working cards, and later in that topic also ways to check and sometimes make work some other cards.

I would like to play Doom Eternal, but since i messed up my right index finger, it will have to wait.
Already on the third play through, still sweat a lot while paying on "nightmare"...

Hi
  I have a fresh install of Debian 12 and I want to make sure everything is up to date, but when do 'sudo apt upgrade I get the error in the attachment;I am not sure how to fix this. Help would be much appreciated.
Thanks
Aaron 

I’m not too familiar with Hal but his is what I could find not sure if I’m even looking in the right spot.

Version is 2.9-238.315.

I would probably recommend just buying a small, inexpensive 12V delta (or) power supply and adjusting the voltage to 10V and not messing with stuff.

People sometimes die in surgery, VFDs might sometimes die in surgery too.

Whatever, you can't change the past.

What is the model?

Could you link to the datasheet of the VFD?

(Don't attach files unlesss you need to, LinuxCNC does not have the money or server infrastructure to store lots of files)

Hitachi excavators are best-in-class.

I've seen smallish, 30-year-old excavators being used for pretty big projects here in Canada.

Not flashy tho, old school.
(Tried and true)

I assume their electronics are just as good and reliable, though Hitachi actually split into many different companies a while back.

Traffic lights? Walk!!!

Cycle!

 


Problem might be that the material symbol and icon library doesn't contain a turtle and/or a rabbit:
fonts.google.com/icons

Anyway regarding the Offset page I came up with this:

 

 

I've been away on sick leave for a bit.
Just getting back to work on ' trail' basis.

What i find is that there are some issues with the Z settings.
My machine is setup as 600x900x-200mm Home is 0,0,0 of course.

Procedure:
Home the machine.
Move the spindle and put the 3D probe in the ER collet.
Then run the Toolsetter macro. To my knowledge this sets the tip at 39.2mm above the bed.
Then I probe the work piece corner (werkstuk_tasten...) This should set G54 to the offsets from machine home, right?
Then I replace the probe with a mill (actually a lollypop stick for testing purposes). And run the toolsetter routine. I remove the workpiece to mill air while getting the bugs sorted out.
Then I load a program. The Touchy GUI shows the program movements etc on the screen. What i see is that it is correctly positioned in the X and Y but that the Z is to high up in the machine volume (red box on the screen).
Running the program errors out on that it runs out of Z distance wanting to go higher than is available.

So my question is on how to set the height coming out of the toolsetter routine.
The distance from Z-home (0) to the bed is unknown to enough of a certain height to be useable, right?
Or is there some other issue at hand?

You can use the old drivers as Todd said. But, sometimes, changing everything is easier. I already kept old servos on a retrofit, then two years after I changed them because there were damaged .
Delta B2 are ok.

Hi langdons,
yes the chinese has only 1,5kW instead of 2,2, just 320 Hz, no vector, no safety settings and outputs, no rs232 programming, it's cost is only 1/4 of the Hitachi. It is 3 years old, mostly layd in stock, has had 7 hours this year since built in, mostly parametring and testing time, but the 10V problem was from the beginning and sucked. Hitachi made a costless repair on it. I think, there's nothing wrong with the VFD itself, but sth has changed in Linuxcnc. But where?
(Hitachi is founded in 1910 and in the US since 1959, Hitachi VFD's are very common here in Europe and I have no doubt about their quality)