Advanced Search

phillc54 wrote:

Something like this seems to work but I have not comprehensively tested for any side effects.

    /* check for reached end of move */
    if (! (&joints[jno])->free_tp.active) {
        /* reached end of move without hitting switch */
         (&joints[jno])->free_tp.enable = 0;
        rtapi_print_msg(RTAPI_MSG_ERR,_("j%d end of move in home state %d, homing aborted"),jno, H[jno].home_state);
        for (int j = 0; j < all_joints; j++) {
            if (!H[j].homed) {
                H[j].home_state = HOME_ABORT;
            }
        }
        return 1; // abort reqd
    }

 

 

I was able to test that code and it worked on my machine! Will run it and post if any issues arise. 

If you mean instead of a spindle encoder. no.

could this be considered for a tapping operation?

I have a problem to linking my pin spindle.0.on to another signal.
the error message is " spindle.0.on already link to spindle-enable "

my code
How can i connect spindle.0.on to my lube output ?

On another note, that float issue popped up again when cutting some plate for the a axis while on the latest dev branch (turns out when using the rip script make sure to call linuxcnc in the same line!!...doh). Going to check my probing settings and post them if i cant figure it out.

I'm currently studying the specifications of the DB25 and P2 26Pole connectors
What mistakes can be made during assembly?

Thanks, will look qt over the next few weeks as i dial things in. I got the latest code running on debian 10 and the A axis installed and wired up. (debian 12 was giving me latency issues ryzen 3600)
Went to run a file generated from sheetcam and got "g92 offsets are not allowed" error. Documentation seems to want a g38 instead of a g92. 

Including the test file and sheetcam post, sent Les a link to this as well. Not sure which side this lies (should g92 be enabled when tube cutting is 1 or should sheetcam probe with g38) 

Hi,

I was running this on Linuxcnc and not sure what happened, and it was years ago now but it died on me. It started out made by Larken and going through a number of new steppers etc. The original machine was made about 2000. The machine is a 3 axis CNC Router. All the mechanics are in good shape and the machine has done a pile of work for me. I do all the CAD and CAM work myself. I cut everything from fiberglass to aluminium, wood and etc.

eng wrote:

i'm still learning about programming, i just took its structure from dds and put it inside a void IRAM_ATTR onTime_0() the same we used here in esp32, and used your .c
with some simple changes, I hope to make it the same as jzolee, as soon as everything is working correctly I will make it available on github so we can use it because at the moment everything is new to me and I don't have enough knowledge to discuss about it, I'm going in trial and error with some basic calculations.
 

Hello, how are you? I was reading the topic and saw your post, did you make the code available on a github account as you said in this post? Tks.

I had to assemble the cable myself because there was no such cable anywhere. So I was recommended the following parts.

www.reichelt.de/ch/de/flachbandkabel-awg...8-26g-3m-p47644.html
www.reichelt.de/ch/de/d-sub-stecker-25-p...?&trstct=pos_0&nbc=1
www.reichelt.de/ch/de/index.html?ACTION=...A=3&nbc=1&q=pfl%2026

I assembled it according to the instructions and until last Monday I was always a little worried about whether the poles of the cable were connected correctly. The two of us then ran the cable through with the multimeter and everything was ok so far. Since it is a 25-pin DSUB connector and a 26-pin cable, I suspect the cable

Did you verify that your cable is correct?

Awesome Thank you.

yes, thank you very much for your help so far. It's demoralizing to imagine after a little over a month that one or two new cards are defective. And now - throw it away? That just can't be true?

"having these numbers off can lead to missed steps or no movement."

No, having these numbers too low can lead to missed steps or no movement.

Most common issue is too short step time, this can led to erratic
behaviour or no motion at all.

Too short direction setup or hold can result in lost or gained steps at reversals
but since reversals only happen at near 0 velocity (and consequent long times
between steps), there is little cost associated with setting quite long direction
setup and hold times (that is 20000 ns is probably OK for anything...)