Advanced Search

Hi all

I'm having issues with spindel setup.
The spindel not getting the 0-10v needed to run.

I can get the 7i76U (new) hooked up to old 6i25, to turn the spindel by 
enable HM2_5i25.0.7i76.0.0.spinena-invert (or spinena) 
Upping the xxx.spinout.minlim

But im unable to edit or use xxx.spinout and M codes dont work to start up spindel.

I added firmware "5i25_7i76x2r.bit" to the 6i25 to get the card to read.
And have external 10v supply for the spindel. Took the negative from driver back to the 24v ground.
Seem to have some noise, not sure who it should be hooked up.

It might be the firmware or something Im missing in the hal and ini.
I really dont know. 

I'm unable to edit the xxx.spinout in Halshow to make the spindel spin. Like I think maybe it should be.
Any tips, all this CNC is new for me.

Added hal and ini if anyone would want to look
 

Hello @beakersBestFriend, i would realy love to use the same sinumerik panel as you did. Is there any way to get the PCB you made?
Thank you.

Ok, Thanks that was very nice

That is a PCI card (a 5I20)

If the motherboard is OK, probably the easiest path
is to just get a new harddrive

Is there any chance the original HAL and INI files  are available or
can be salvaged from the hard drive?

One thing on the plots, adding the Z velocity would make analysis easier.
Both in determining the start of motion and the point where Z motion
becomes synchronized with spindle rotation

Also an actual screenshot is easier to check than a picture because its
accurate and does not have geometric distortion. (making it hard to tell if
lines are straight)

Here's another interesting example. I first made a threading scratch pass at 50 RPM. When the second pass started, I cranked the spindle speed quickly up to about 300 RPM (I'm guessing), then back to 50 RPM. The second cut started overlaying the first, then went to the right as the speed increased, then back to the original cut at the end.

So the speed definitely affects the Z position, and my original concern about the lathe bogging down during threading in a deep cut and then that slowdown causing gouging is warranted.

beauxnez wrote:

Thanks, I don't know if I did it right but I got an error message.
That's a warning, not an error. You can usually fix it by copying the

That's a warning, not an error. You can usually fix it by copying the libusb.dll (libusb dynamic link library) to the path of your Python installation.

Note: If you downloaded Python from the Windows Store, you should copy libusb.dll to the C:/windows/system32 directory.

I spent 20 minutes trying to sketch a simple part to revolve and gave up after the autoconstraint engine completely hosed up the sketch. They really really need to put work into the sketcher and the UIX , it is still god awful to use. Hell I am willing to donated money on a monthly basis to get out of using fusion360 at this point, but there doesn't seem to be any seriousness from freecad developers about working on it fulltime.

comp file is a list of nominal (normal) position and compensated numbers in each direction.

ie (type 0 compensation)

10, 10.1, 10.08

Meaning when you move to position 10 in forward direction, the machine will move to 10.1.
In the reverse direction moving to 10 will actually move to 10.08

You need to leave a little bit of max acceleration head room for the machine to apply compensation.

I've never used it, just interpreting info I have found.

please let me know how it goes

The default timeout for wait_complete() is 5 seconds.
Do you need wait_complete?

I have a machine coming that uses a motherboard with a pcie card. I don’t know the model of the card yet.

Should I try and use this or just switch the more modern Ethernet card?
 
Im assuming the original HD is bad.  That’s why they sold the machine.

 

Well I looked in every single box.. nothing. bah!

Good catch. I ran the test again, and noticed that HalScope does not update the picture except after every scan - that was probably the problem. I also made all the pictures at 100 ms per division. Here are the revised photos. I also made a zoomed in photo of when the movement starts, so I could read off the delay.I'm not sure if that has any significance.

100 RPM - 30ms from falling index to start of Z movement
 

200 RPM - 17ms from falling index to start of Z movement

thx i will try it