Advanced Search

tommylight wrote:

Rod, he has huge excursions on both sides of the graph, those are not shown unless using --show, and those are the ones causing latency errors and link drop.

Of course there are excursions. That's because the histogram is only showing a window of 20 usec when the range is 70 usec over a 20 minute period. Whether you use --show or --sbins 1000 won't matter because either will show the full histogram. This is a case of how to lie with statistics with an inappropriate graph scale.

I get this error when the same tool is in the machine and I start the program. If I use another tool, the machine normally changes and measures the height of the tool.
anyone have any idea what the problem isOperator Error : Operator Error : M6 / change epilog : Python argument types in emccanon.CHANGE_TOOL ( ) did not match C ++ signature : CHANGE_TOOL ( int )


 

Hi Chris

I found a few things to fix in qtdragon(hd)
When saving the log to a file, an error is displayed, as in the screenshot.

The "clear status" button does not work.

In MacroTab Widget, the spacebar does not work.
In all others, "FACING", "hole enlarge", etc. pause works with the spacebar, but with MacroTab it does not.

There is such a topic forum.linuxcnc.org/38-general-linuxcnc-q...p-line-number#330090
Could you make it save the line number, e.g. in the log?

Hi Chris,
I will use hal pins to control LEDS status. no toggle.

This push button will probably be popular with qtvcp users since it will mimic certain pathpilot buttons. It will also reduce the amount of real state on screens. I can see it used for pause/resume, jog inc/cont ...

You may be able to rework it to run on single phase. I haven't done it myself but i've heard reports:
www.practicalmachinist.com/forum/threads...han-expected.429807/

We have an old 3016 with the 88HS control in our tool room that we run from time to time. I find the built in control pretty ok and there is a lot of support out there for spare parts still. We use one of these: www.calmotion.com/product-page/lanusb-fad
to drip feed large programs and load smaller programs from USB

Yessir, my experiments concur.
In fact a P of 0.45 and an I of .0015 works quite well for this system.

The slowest speeds are quite a bit faster than commanded, but 1000rpm and above are fine.
This tripping of the relay is I think self inflicted, I don't believe hopping from a very high speed to a very slow one, is something you'd do in the real world without stopping the spindle to change a tool.
Next test is to see if I can orientate the spindle and even execute a tapping cycle.

Very exciting. Thanks for your guidance as ever.

Test fit of push buttons and choosing imbedded keyboard.
note that buttons are not secured in place yet. 

ist immer noch ein Call
schreib mich mal mit call ät darc.de an
dann schick ich dir die Dateien

Also:

eusurplus.com/index.php?route=product/search&search=7i84u
 

D typically makes no sense in a velocity--> velocity loop

Important ones are 
FF0 == 1

P and I

Mesa im Deutchland:
www.welectron.com

The vfd has a braking resistor. Now its being controlled, the issue has disappeared.
Think I just read that I should put P to zero and D to 1.

The oddness is possibly due to a VFD overvoltage on rapid decceleration. 
You may need to add a braking resistor to the VFD if you need faster decceleration.

Another  possibility is to limit the spindle speed rate of change by passing
the commanded  RPM through LinuxCNC's limit2 component.

 

Hello everyone!

I am currently investigating a linuxcnc retrofit on a Fadal 4020HT. The machine is a 1996, and I am as of now unsure if it has AC or DC servos. Still figuring out if I am going to go ahead with purchasing it...its potentially a steal!

So background, I am already pretty familiar with linuxcnc. I have a gantry mill that I built from the groundup running linuxcnc/gmoccapy that I make my living with building guitars. Looking to move to something more powerful with an ATC and so I'm shopping VMCs.  Might sound strange but they are a standard for a lot of guitar manufacturers and would greatly improve my workflow.

So this 4020 is from a good sized machine shop, it is under power but hasn't really been used for about a year.  I was able to inspect it and mechanically it is in great shape. There appears to be some sort of problem with the spindle orientation sensing on it. It is running an old 88HS control right now. 

My intention is to potentially purchase this machine and move it over to linuxcnc with probe basic.  Any general guidance or tips from people that have been down a similar road would be greatly appreciated. I also have a few specific questions:

• Since I'm using linuxcnc, is it reasonable or a good idea now or in the future to change the spindle drive over to a modern VFD while retaining the original spindle? I know these spindle drives can be a big cost and difficulty when they go out. I'm also not sure how compatible the existing drive would be with linuxcnc control.
• Related to the above, I am interested in running this conversion on single phase power if that is possible. I believe the servo drivers all ultimately run on DC power, whether they are AC or DC servos, correct? In that case, if I were to also be able to run a VFD from single phase I should be able to avoid the phase converter route. 
• I have not had much luck finding wiring diagrams that give specifics about the lines for the encoders/resolvers on the servos. Does anyone have a good reference for their detailed function to help me figure out how to interface with mesa cards?
• What is the general opinion on homing and limits for fadal conversions? This one, like most or all of them, has that cold start system where you line up the marks on each axis and let the resolvers/encoders do their routine at startup. As far as I understand it has no limit switches or scales or similar. Is it preferable to mimic the same sort of system with linuxcnc or install some sort of homing switches?
• Has anyone had any luck interfacing a jog wheel interface on a VMC with linuxcnc? I would absolutely love to keep that function.

Thank you in advance for any insights you have to offer!

Wie schon gesagt. Das einfachste wären die sserial (smart serial) Karten. Das ist plug n play. Bei der 7i84 zb. hast du s.g. Darlington Ausgänge. Die klnnen kleinere induktive Lasten wie Relaisspulen oder deine Ventile treiben. Haben sogar Freilaufdioden integriert.

Wenn dein Expansionport noch frei ist, kannst du auch die billige Selbstbaulösung fahren. An dem Port liegen 17 IO Pins des Fpgas frei, die du an Relaisboards klemmen kannst. Bzw. an deren Optokopplereingängen natürlich.

Also. Etwas Eigenbau/Gefrickel und du hast Kosten um die 20 Euro. Oder ne 7i84 zum Beispiel die wesentlich mehr kann und plug n play ist. Kosten so um die 100 Euro. Beides ligitim und die Mesakarten sind allesamt tiptop.