Advanced Search

I am using Octopus Pro board with remora-spi. Can you help me with working TMC5160 (stepsticks) drivers. Previously I used TMC5160 with tinybee board flashed with FluidNC in daisy chain config, they were working fine.

Gui related pins (ie gmoccapy and pyvcp related pins) do not exist until the gui has loaded. So you need to put those hal connections into the postgui halfile.

Ah cool thanks.
my screen res is 1680x1050 right now (old cinema display) and my panel screen is 2k, 4:3. I'd rather not buy a new screen for any of this.

I'm installing linuxcnc 2.9.4 now.

I got mine set up using axis and then moved to TTS repeatable tooling and  went to QT Dragon because I could not get probe basic working on my hardware. Then I found none of the QTdragon screens worked for my 16" monitor so upgraded to a 16"  1080p monitor. It has probing and ATC. The manual tool change works well.
Don't Google, Its all well documented in the Linuxcnc docs.

There was nothing wrong with my THCAD-300, I just switched to a divided voltage source from the new plasma cutter instead of the raw voltage from the older plasma source. By changing the input voltage for the THCAD I would get better resolution with my divided voltage source signal.

If you are ramping the spindle speed you cannot use the PWM enable in the same way.
The PWM enable and 7I78 enable pin need to be driven by something like machine-on
in this case.

Interesting - almost sounds like the spindle is 'decoupling' from the synchronized z-axis when it reaches the programmed z-value (-50).

This is not the exact behavior I was seeing, but I also wasn't trying G33.1 at such high spindle speeds or accel values on my real machine.

It may help troubleshooting if you can set up a halscope that shows the z-axis position command and spindle velocity during the decel-stop-accel phase (M3-M5-M4) at different spindle accel settings.  Maybe we can see the point where the z-axis stops doing what we expect it to do.

Hopefully someone more experienced than I am can help diagnose, or confirm that this is a code problem rather than a config issue we're both having.

Side note - the behavior you describe is almost identical to my Emco 325-II lathe running Emco's version of Fanuc 21TB.  Emco's manual claims the lathe can rigid tap, but after a number of broken taps and some investigation using a high-speed camera, I discovered that the control stops synchronization of the z-axis when the spindle stops to reverse.  It doesn't 're-couple' the z-axis until the encoder index signal is triggered during the M4.
So depending on where the spindle stopped there could be up to 359 degrees of spindle rotation with no Z-movement while the tap is still in the hole.  I've had to switch to tension-compression holders to stop breaking taps.
Ironically, Emco's version of Siemens 840d and Operate rigid tap fine...with the exact same hardware.

In my case, I actually followed the directions and used the links that Lcvette listed, but it seems it was right around the time that changes were made to probe basic and I hadn't updated since then. There were also a few other changes I made while trying to get everything to work and also to get better latency numbers.

It wasn't a surprise that I needed to do the probe basic conversion again and although I didn't want to reload linux, I did tweak some things there and I had the same thought as Lcvette, when I had issues updating, in that it might be best to start over.

Even though Dr. Dflo did link to the proper instructions page that you guys use, I missed a step or it was updated since I followed it and with the struggles of learning it all, I may have caused some of the issues.

Lcvette spent a lot of time with me on messenger to chase down the issues. That turned out to be a great way to quickly share pictures of what I had going on.

I'm thankful he and everyone else on the forum have taken the time to help people get their machines going. I have read many threads on the forum and that helped me piece together hal ini and of course had lots of information on the hardware of converting a mill.

 

Thanks for support.

The problem can is test in sim/axis, is the same on real machine.
Set axis ini.file in mm and increase max velocity general and axis at 300 for example.

Start linuxcnc.

Commnad m3 s2500
after g33.1 z-50 k1.

the spindle start rotation at 2500 rpm .
The g33.1 start when index encoder is reached.
the momachine move at z-50 with correct velocity.
The spindle decelleration , but Z not move in decelleration ( not correct)
The spindle ramp in m4 , but Z axis not move ( not correct)

I have test on real machine and sim/axis, if ramp acelleration spindle is very short, the problem disappears with m3 s2500 and it could reappear at 4000 rpm. If you further reduce the spindle acceleration, making it almost instantaneous from 0 rpm to 3000, the problem becomes evident with the m3 s5000 command.

But these are just attempts, to understand where the problem is, in reality the spindle must have its own acceleration and cannot be instantaneous, in order to preserve the mechanics and electronics, especially in deceleration, since it will have to download the energy of the drive's DC BUS onto the braking resistors.

Drives are delayed (guy is sick) but I got my lenovo tiny pc and the electrical cabinet set up and a spare delta ms300 to try rs485 things with.

So originally I intended to try probe basic, but I don't have a 1080p monitor so I may try something else. What was the one you mentioned Rod? QTdragon gui?

Does this ui cover probing and ATC well? (im googling it now)

Thanks

And there is one "last" thing, about enable signal. I'm using spindle soft start code in hal, as my vfd doesn't provide any feedback signals, and it works OK when starting (accel), but after M5, it immediately disables VFD, that means it doesn't wait for deceleration.
Is there a pin I could use for that?

My spindle soft start code

Linuxcnc is running, well little by little.
I have the encoders counting and the DRO scale is calibrated.
I have the limit switches all tripping.
I have the main safety relay latching and tripping from the external button.
Next stop to get the safety relay to trip from the gui, then I plan to enable the servo relay, see if the axes can be moved by the gui, then study homing which looks like a whole mountain of mystery in itself.

Not only makes even more sense, but works.
Thank you sir, again.

If that pin is used for homing, you can not create it, well you can, but that would require a lot of change in homing configuration.
Machine pins you can find by using the "show hal configuration" from the "machine" menu when you run LinuxCNC.
But since you can not run LinuxCNC yet, you can find them in the hal and ini files you are using, the pins are usually like this:

net both-home-x <= hm2_7i96.0.gpio.000.in_not

net both-home-x => joint.0.home-sw-in
net both-home-x => joint.0.neg-lim-sw-in
net both-home-x => joint.0.pos-lim-sw-in

loadrt not count=2
addf not.0 servo-thread
addf not.1 servo-thread

net inverted-min-y <= not.0.in hm2_7i92.0.encoder.03.input-index
net min-y => not.0.out

net inverted-max-z <= not.1.in hm2_7i92.0.encoder.04.input-index
net max-z => not.1.out

"net" syntax is

net signal pin [pin] [pin]

if "signal" does not exist, it will be created
if "signal" does exist, the pins in the net statement will be added
to the existing pins already connected to the signal.

In this case its assumed that the signals min-y and max-z already exist and
connect to linuxcnc's joint limit and possibly home pins.