Advanced Search

You might need to force home-sw-in high, so that it always thinks it's on the switch, and then it will set the index-enable.

ie, in the HAL file:
sets joint.0.home-sw-in 1

Hi Andy, I've been running a 25,000ns relatively successfully. Which is why I've been scratching my head so much. However, actually thinking out loud on here had me thinking it had to be electrical. So I dug out the oscilloscope and probed the signal. The cheap Chinese sensors had a 20k pull up resistor which was far too strong and was causing the pulse width to be way too long. So at 1900 the signal went from a pulse train to just "on".

I've swapped out the resistor and now getting good clean pulses read by the Pi with a stable speed reading up to 4000rpm.

Thank you for your suggestions as they have pointed me in the right direction. I'm in the process of modelling up a mount so i can mount two sensors to create a encoder that will do direction as you suggested.

I think you are suggesting that you could supply "fake" commutation signals from LinuxCNC to the drive, and that might be enough to persuade the drive to start working?

This is what I'm thinking. I will try it as soon as I have time and report back.

For comparison here is how the plot looks without the patch applied.

 

Hi all, new user long time lurker. My first linuxcnc experience was a sherline and a parallel port some 10 years ago. That turned into a pair of tormachs, now a vf2ssyt, and more if I had the space. Anyway...I picked up this lathe some time ago. It was originally cnc and converted to linuxcnc by the previous owner. I got it in a sort of working state. Everything was hooked up and moving but needed some refinement. At some point the PC died of unknown causes so I decided to start from scratch with trixie, kde and 2.9.6. I've got the servo thread running solid at 0.5ms, the motors all tuned and running well, the spindle drive is now controlled through modbus rather than analog, and I've added a few handy things with pyvcp. It's running fast and holding size.Now it's ready for a turret, and I'm hoping to get a recommendation. I currently have a neat manual turret but... manual is no fun. I've browsed alibaba and seen some affordable options. Also checked ebay and the pickings were slim, ancient and beat to death. I considered a tormach turret since it works so well on my sl15 but it would be nice to beat the $5k price tag.Also searching for an automatic collet closer or some sort of automatic chuck. It would be amazing to have a 16c or a 3j automatic collet... sounds like a huge amount of work if I can't find something to retrofit. Any ideas?

Looks like a fair bit of work has already gone into this. Thanks for sharing.

Hello everyone,
I am a beginner of LinuxCNC but I have collected what i have learned using EtherCAT, BECKHOFF modules and a OMRON R88D-1SN drive. I think it may be useful for others approaching this world. The repository is still incomplete and lacks of many things. Hope in a feedback from everyone and from who is working with the same OMRON drive. 

Here is the link to the github page:  linuxcnc-collection

Thanks
 

Lcvette and the Probe Basic dev team quickly produced a patch for me to test.

They are clearly making progress on this issue because with the patch the crash is gone. However I noticed a slight side effect with the plot not drawing all the moves correctly.

Here are the steps I did to produce the following screenshots.

I started by setting all the G54, G55 and G56 offsets to all zeros:

G10 L2 P1 X0 Y0 Z0
G10 L2 P2 X0 Y0 Z0
G10 L2 P3 X0 Y0 Z0

I then loaded the file attached to my first post and probed all the three parts going from right to left (starting with G56, then G55 and finally G54). The probing worked and there was no crash but the plot show some strange moves.

 

Opening the same file again without doing anything else produced the following plot instead.

 

The plot above looks better but I think it's not fully correct as it should start with the left most part not center one.

Here are the offset values for G54, G55 and G56 used for the two plots above.

 

Hello, I looked all options.
If I go with base interface I would have to do isolation on all 6 encoders that would be best option concenirg signal grounds and also I would have to make aditional 6 connectors to carry signals to mesa board. Also not sure if 6i25/7i92 has space for 6-7 step gens + 6 encoders(not regular ones but uart + incremental -> absolute so more logic needed). But if I do it this way I would get all 6 readings synchronized.
Probably I will choose to go with stm32 ethernet option or mesa smart serial(maybe both try). In this case I will not have synchonized reads of positions but mismatched max by 60uS.

When you talk about SSerialB are you refering to master or slave? Could official firmware for example for 6i25 or 7i92 currently accept 224bits via smart serial from slave? In my case slave will just send 24 bytes to mesa card.

Do you know for robot kinematics module how much I need to sample robot joints angles at “same” time?
I suppose mesa built encoders interface do this in hardware and just read all 6 regiters at same time, so no even small mismatch in time between samples?

Thanks

So on the z axis I did manually set the z enable and jogged to where the index was and it did turn off. I then tried changing the final velocity to invert it from the starting velocity of homing to make it come back instead of continuing into the E stop limit and that did not change its behavior it still goes past and it's homing sequence to the E stop

that seems like an easy enough check. Ill do that after I get home from work!

Glad to help.  The user guide maybe needs a little clarification in this area. It's sometimes difficult to write user guides when you already know the process... 

Happy cutting.

That works! thanks for that little bit of advise. I could have saved myself the headache by asking right away.

wels wrote:

Is the DRO box the buttons added in settings, then yes. I just found that I need hal pin

qtplasmac.ext_laser_touchoff
I have to figure out where to put it and if it will work...

That is not quite right. You just need to finish the following hal connection in either the <machine_name>.hal file or the <machine_name>_connections.hal file, I cant remember where it is off the top of my head.

Then do the peripheral offsets part and the LASER button will show.

I would verify that the index works by manually setting the index enable signal
for the tested joint (via the halcmd sets command) and then manually moving
the axis past the index mark to see if the index enable signal gets cleared
at the index mark.