Advanced Search

Another way to show/hide objects is to apply a scale factor of 1/0 according to the state of a hal pin (not sure if that works for the tool trace though):

github.com/LinuxCNC/linuxcnc/blob/master.../twp_vismach.py#L210

I have also been told its pretty far deviated, so it will not be a simplistic task to add it to the main.

I am curious how the source of path-pilot looks like.

Hi Chris

Have you looked at my problem?
I have another idea, a request..

To set an input to slow mode, you set the 'slow' parameter for the corresponding pin
something like:

setp hm2_7i96s.0.inm.00.input-00-slow true

The documentation is in the hostmot2 manual page, inm section.

Halshow will not catch short noise pulses as it is normally only updated
10 or 20 times per second. You can catch them with HalScope however.
 

Hi Roockie,

The code is :
codeberg.org/skynet/linuxcnc_websockets

Above is dedicated to what you see on the youtube video.

Thank you. I have AMC amps for this application, these ones require the communtation signals until it sees the index. The thing that threw me off was the signals were differential, I’ve never seen , and I’m not an expert in this field, dual communtation signals. I take it , that I would just pick either the u,v, w or the -u,-v and -w . The AMC amps I’ve used allow for one set of halls signals. Thank you again.

If you use a graphic display , the file is checked each time it is loaded.
Look here how that is actually done:
github.com/LinuxCNC/linuxcnc/blob/master...qt5_graphics.py#L350

It's certainly supposed to be speed independent,
that is, the Z motion is supposed to be "geared" to the
spindle rotation.

(there's a video I can't find at the moment that shows
LinuxCNC threading while hand turning the spindle)

Possibly an encoder/index/Z axis issue?

It looks from the PC board that there are 12 outputs from the encoder.  A B quadrature, plus index (Z) and U V W commutation, and the differential complement of all of these.  That should be enough to run any industry standard servo drive.  AMC, Servo Dynamics, etc. have brushless drives that can take encoders like that.  Some don't need the UVW complements.
Fanuc had a different scheme for commutation on the older red cap version, the later ones are serial, so there is no ABZ signal at all.
Jon

My Current max acceleration is set to 25. I'm not sure where i got that number from unless it was a carry over from my motor and driver settings in the old Mach 4. any suggestions as to what they should be . running NEMA 23 425oz motors and the Stepper Online DM542T Drivers. Don't remember my settings for the driver but I'm pretty sure i went conservative on them as I couldn't find the correct Drivers settings in Linuxcnc

Slow cut speed = plenty of hot slag = hard to clean
Happens due to limited acceleration of the machine as it has to slow down a lot on corners.
Try upping the acceleration for X and Y axis, it should help a lot if you can get the corner speed near the normal cut speed.

Hey Scott,
Sorry to bug you again, but just wanted to let you know I finally managed to flash the firmware and ping 10.10.10.10! Next up is diving into the LinuxCNC side of things.

I’m planning to document everything I did to get it all working and might make a YouTube video showing the steps once my exams are out of the way next week. Also, I was thinking it’d be cool to contribute to the project documentation if there’s any way I can help out.


Thanks again for all your help – really appreciate it!

Id like to reduce the amount of slag I'm getting on tight corners, I've searched the forum for settings on the THCAD2 and the 7i96s and really haven't found anything related to it. longer cuts and or curves come out perfect its just tight cutbacks it leaves a pile of slag. I'm cutting 12ga Steel and reduced my speed from 120 to 100 for the 12ga settings. So I'm not sure if I'm getting the height control locking at at the right time or its something else. my air quality is consistent and I run a refrigerated drier so I know my air is clean. I did change the Post processor to one of the Updated ones here called Plasmac local materials for setting the material from plasmac instead of sheetcam. it improved quite a few items during cuts. Maybe my motors and drivers aren't tuned correctly? open to anything to reduce the amount of cleanup I have to do after the cuts lol. and i might have left out some speciffics needed so ask away.

  Hello there. I have a couple of mills with Yaskawa servo systems, mid 1990 BE series analog drives. They are junk, constantly blow up, very little info available, only support from Yaskawa, send us your life savings, in my case about $5 , so not enuff anyway.Using another brand of drive should be doable, the wrinkle here is Yaskawa’s unknown initial magnet sensing. The motors are sinisudialy communtated, sorry for the misspelling. The oldest ac yaz motors used what I suspect is a coded type hall sensing for initial trapezoidal communtation. The output signals were v,-v,u,-u,w,-w. , output from the encoder to the drive.The new motors have the markings on the encoder for the added signals, they are unused. I suspect the circuitry is there. Both encoders have on the glass disk , an inner ring of what I guess could be grey code. See pictures.Does anyone recognize this and have a hypothesis about how these signals would work? My guess is they are similar to the red cap Fanuc bldc signals. I have not put a scope on them  



 

 I'm having an odd problem. I'm running a threading routine using G76. I thought that, while threading, I could change the spindle speed without affecting the operation. Everything seemed to be working fine until I starting threading something a little larger for me - a 1"-8. I started to see bad gouging off and on during the threading. that at times nearly stopped the (7HP) lathe. I was only taking off about 0.002" per pass for most of the operation. I thought something must be moving, and checked all the obvious things. Everything looked OK.

One of the things I tried was making a scratch pass at three different speeds, 100, 150 and 200 RPM. I ran the same program each time without changing the setup. You can see that the cut indexed to a different point for each speed. Conversely, if I ran it three times at the same speed, it would index to the same cut.



This is not good! It means if I cut a thread and then need to recut it, I need to make sure that the spindle speed is exactly the same or I'll get a different thread position. Needing to cut the thread again can be because the piece rotated in the chuck during the cut or I didn't set the tool X position deep enough. I'm also thinking that as the lathe slows down slightly, it might change the Y position of the tool incorrectly and cause the gouging.

Any ideas?

Two indexing signals to LinuxCNC: one pulse per revolution for indexing, and ten pulses per revolution for position
Spindle speed set manually, and not by LinuxCNC
LinuxCNC v2.9.3