Advanced Search

I used Argon drives on a retrofit, they are very good and have nice software for setting them up, good documentation too.
You do need a dongle though, and the comms between dongle and drive have a hard coded speed that can not be changed, so might have issues. Use good USB cable.

Meanwhile i found a driver that could fit my needs but i'm too late .The Argon Drive made by  Granite Devices can do step/dir and Analog+-10V but sadly is no longer in production.
I guess i will have to wait til next month and see what Leadshine come up with ,assuming the technician i talked to did not bullshit me.

About the Index sensor - Pocket sensor vs drive wheel sensor
This could be a design issue, but if I look at my geneva mechanism I think for indexing ideally you would want to detect the pin on the geneva drive wheel, so the drive wheel is fully locked in the geneva wheel.

If you detect just a pocket pin, the drive motor and drive pin will stop at the disengagement position of the pin, where the lobe takes over.
 

If I detect the drive pin on the drive wheel, it would allow for more error margin as the lobe is fully engaged.
But this would require both the index sensor and homing sensor to be high to complete initial homing.
Otherwise the first index move after homing could be false, depending on the direction.
 

What is the usual way to do this?
If I check the subroutines the M13 homing cycle is not considering the index sensor, only the homing sensor.

Maybe bind Index sensor to the Homing sensor input signal in HAL using AND2 ?

I've never tried the lathe option.

How do you run ncam (embedded, standalone...)?
Does it give errors?

Regards
Giovanni

Hi Rod,

You mean adding the cmake project into the original makelists.txt file and build it from there is the way to go?
I did not test that option.

I think the state_tags are just used to get or set the current states of the cnc. In my view it has nothing to do with
compilers.

Here is a sim config:
 
 

1. unpack to your 'configs' folder
2. make sure that '/vismach/mazak-integrex-200y-gui.py' is marked as executable (right-click->Properties)
3. 'halcompile --install' the enclosed 'mazak_integrex_200y_kins.comp'
4. start the config and run the preloaded example gcode

Notes:
- Slide tilt angle and pivot-length can be set using the slider in the right hand panel.
- the vismach model is a reused model from one of my other sim configs so it is a bit minimalistic but should suffice the purpose for now.
 

Did you check out this?
github.com/MetalMusings/MyOwnEtherCATDevice
I have made several EtherCAT devices.

Please post the output of lcec_configgen.

Thanks but lcec configgen and ethercat pdos ... seems to reply with complete list of supported expansion module of coupler S1-M20.... maybe module need to be configure via tc3 for see from linuxcnc .....

.xml send to me from svelec talk exactly of 0x1600 and 0x1601 register that not compare in the list .... compare only 0x1600 and 0x1610 .... real strange situation. Perhaps I verify el1x.c file .... ecl16dp-in is equal to el1809 module, 16bit register for 0x1600 .... and el2x.c file can work for ecl16dp-out too with same register ...

Touch screen. Qtdragon and a touch screen.
One can get by without keyboard and mouse.
 

notJamesLee wrote:

I am going to leave it as is because its clean and now going to switch the control to closed and see about tuning in the PID before i reinstall it on the CNC. unless thats not a good idea.
 

 

I'd suggest leaving the PID settings alone in the drive for now.

I think the drive's following error setting is PA0.05, which is factory set to 4000 counts before an alarm.  In your screenshot it looks like that parameter is "Max position following..."  and I think the cut-off text is "...error."  If so, that's the number of counts the motor can be out of commanded position before the drive faults.

Which means:
1 - the encoder PPR setting in the drive is correct (it's looking for 4000 pulses, which is what a 1000-line encoder produces in quadrature), and
2 - the motor can be a full revolution out of position before the drive faults.

Set the following error counts to 200 for now, and you can adjust that up a bit if you start getting drive following errors under normal positioning moves.  Frankly, with as low a torque load on the motor as I expect you could probably get away with 50 counts (or less).

Regarding your earlier question about the encoder... the motor datasheet indicated a 1000-line, 4000-pulse encoder is on the motor.  If the drive wasn't programmed to expect a 4000-pulse encoder the motor/drive pair would act really wonky.  Those drives are usually set to match the motors, but it doesn't hurt to check.

That was it, adding the self.task == 0 at the beginning solved the read ahead issue and removing the yeilds in the middle of the g-c-code operation took care of it! Behaves like expected, M-codes execute and the tool change executes with the offset. Got quite a few commits trying to troubleshoot this one. Thanks for the help!

update,

I changed the number to in the driver gui to 1800 and upped the 'stepsPerRev' variable in the Arduino code to 600 and its working great so far. This is with the dip switches set at default.

If i switch the dip switches to 1600, the value in the gui updates to 1600. So this leads me to believe the dip switches set the steps per revolution. in retrospect i guess its obvious.

I am going to leave it as is because its clean and now going to switch the control to closed and see about tuning in the PID before i reinstall it on the CNC. unless thats not a good idea.

langdons wrote:

I have no quality mice available.

I have plenty, you are welcomed to use them, but i can not guarantee the quality! They do chew on everything in the shop though, seem pretty healthy by the looks and the speed they move through the shop.
Edit:
The evidence of the above:
forum.linuxcnc.org/show-your-stuff/32784...ofit?start=30#239606

In order to control the ATC stepper motor like a "dumb DC motor" with just the DI-Outputs mapped to my MESA outputs and free up the stepgen on the MESA for other future purposes, I simply purchased a step generator from amazon (10 bucks) and two relays.

I will just use the relays to trigger the board start/ stop and direction tactile buttons (solder to button pins).
Should work fine in combination with the geneva drive..

I still have to find good sensor flag positions for Home and Index, but that should be solvable.