Advanced Search

There is always voltage applied to the motor,
but as I said, with 2 pins your only real choice
is mode 2.

The driver will create /PhaseA and /PhaseB
from the PhaseA and PhaseB parallel port
signals, so at any of the 4 possible output states
2 motor drive outputs are energized

I think its a good feature. As you can imagine at 24000 rpm when you hit pause & then wait for the spindle to stop a 3 mm mill bit doesn't take much to cook. Also having the spindle move clear of the work piece when you hit stop seems very natural. If you hitting stop chances are somethings gone wrong & you want to get at the job.

The large machine that I'm planning to get going has a 3 meter bed so it would be good to be able use remote buttons & a USB controller makes a good cheap pendant.

I appreciate all of the work you are doing on this. QtDradon has been what has been bringing me back to LinuxCNC as it seems (to me) the most intuitive interface,

As always any thoughts are appreciated but I think it is something worth working on even for future versions as I believe many people would benefit in the future.

Thanks
Alex

is there a way i can get these limit switches to be off normally? as it is right now, they are lite up like a christmas tree and when i trigger them, they turn off. how can i get them so they are off and they turn on when they are triggered?

Removed Dropbox links and figured out how to resize my images and insert them, sorry about the nuisance.

I suspect the motion box thing is doing some sort of signal manipulation or filtering.
It seems bizarre to me there's a phase where there's no voltage output. I derive that from the working turbocnc setup I can plug this box into and it runs the stepper smoothly.

I was going to refer you to this but... it's you!
forum.linuxcnc.org/qtvcp/49921-qtdragon-stop-pause-run?start=0

PCW wrote:

If you only have 2 output pins, and  the drive is not step/dir
or CW/CCW, mode 2 is the only mode that makes sense...

Yes, of course, sorry i forgot about using two output pins.

If you only have 2 output pins, and  the drive is not step/dir
or CW/CCW, mode 2 is the only mode that makes sense...

That adapter should work for sserial devices

FF1=1 works if the analog output scale = velocity in machine units per second at 10V
 That is if the machine velocity is 200mm/sec at 10V, and you set the analog output scale
to 200, FF=1 is correct.

ok I'm glad you stuck with it!

Do you want it to always automatically raise the spindle on pause? Right now you must press the 'spindle pause' button. That button currently does not have a pin associated with it.
Most people use HALUI for conecting with an operator panel, but it is not going to intergrate well with the spindle pause without some work.
HALUI pause will work fine but the HALUI resume function will not wait for qtdragon to lower the spindle before resuming the program.

This is a bit of a weak spot for qtdragon/linuxcnc.
We could probably find a work around.

Please upload pictures here on the forum, your first dropbox link insist i register to view, the second gave me two warnings about cross site scripting attacks on my PC. I really do not like drops#it rummaging through my PC.
-
LinuxCNC can do stepgen types 5, 6, 7, 8, 9, and 10, all for 2 phase stepper motors, what you describe seems like type 8, not 5, so just edit the stepgen type, save and test.
From past experience, the most speed with good torque i got from 6 and 7, most torque from 10 but some stepper/drive combos really do not like it.
But, first, make sure the wiring is correct, no amount of software will help with a unipolar motor wired to a bipolar drive or vice versa.

I added a 74HC74 flip flop IC and divided the frequency signal by 1/2, which now works perfectly with a muxed A encoder. I couldn't get periodm to read the signal cleanly, it only updated the frequency if I touched the nozzle, but that's probably user error.

The good news about the 74HC74 chip is that by reducing the frequency sent to the encoder, it is a cleaner signal and the detection distance from the sensor increased from 0.1" to approximately 0.75". I am able to detect way further now with great response which should help immensely.

I'll have to grab some data to see how linear the response is now. One weird thing though, when the surface approaches the nozzle, the frequency increases until contact, and then it goes back to 0 (approximately) Hz. It has the opposite effect as before.

I didn't check everything but I bet it's this line that must be set somewhere.:
DaneelDragon.hal

# net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

oops..

That's the line for the remapped M6 routine. I had pinched the computer of another machine with the touch off button in a different location.
The error doesn't say which file the error is in although it should have been obvious.
Thanks for pointing this out.

I have changed the parameters in M6 and now everything is working as it should including the pause button.
Again thanks for persevering with me to solve this.

One last question,,,
At some stage i may setup a usb board to control the machine remotely, Can I link one of the buttons to the pause function & still get it to raise the head. What HAL pin should I link it to.

Alex
​​​​​​​

This should be everything. I have the console dump as well if it would help.

Ron

The lines outside the box are surely the problem.