Advanced Search

I have 8 ST link V2 and they are all 128kb. How can I put the remora-rt1052-3.1.3.bin firmware on them when they are 350kb?

Doesn't work. The i226 uses the igc driver.
Neither igc.EEE=on or igc.EEE=off does work, entered just by chance.
As it turns out, eee is disabled by default on the new i226 card so all is good there.

Coalesce is set like thiswhich is perhaps how it always have been done. No need for any tx-usecs, that was the point. In fact, that is an error to add tx-usecs.

 

The flat control cable from the driver's controller has 16 pins, I shouldn't try it because I'm afraid that there will be some ``smoke signal''

the end of the shaft snaped off. i just pulled it apart to see what i could find. that's pretty odd

machinedude wrote:

 my x was a bit under powered, so this is reason to bump up a little since i can get a 3 Nm with the same frame and shaft size.

Great to see adoption of real engineering units in an imperial world! 

it did seem odd to me too but i did a quick search on google on mechanical failures with steppers and it said gears stripping? i never tore one apart before but i might on this one just to see the inside. when you spin it by hand it feels wrong. usually, you can feel the 1.8-degree full steps.it turns under power but it has no torque.

i got a bigger one this time of the same brand because i can have it later today. my x was a bit under powered, so this is reason to bump up a little since i can get a 3 Nm with the same frame and shaft size.

Thats unusual. Usually, they overheat and loose steps if you push them too far and eventually stop. There isn't anything to strip really. But the temperature could exceed the safe limit and melt the insulation in the windings. What happens if you swap stepper drives?

There is something to be said for using quality motors. Try Moons Industries who you are in US. 

 

I think there is more to consider when commanding a tangential knife. eg when do you lift it on a sharp corner? When do you have to overrun and reposition on a corner? I don't know anything about tangential knives but I am guessing the  motion for the knife that a supplier of mine uses to  cut my parts from rubber sheet is a bit different to a circular saw a stone mason uses.

One issue with external offsets is that you need to allocate a percentage of velocity and acceleration of the axis to the offsets. In some applications (eg plasma cutting) motion and offsets are mutually exclusive so you can allocate 100% of motion to the offsets by doubling the velocity and acceleration and using a offset ratio of 0.5

I've never experimented with anything but wouldn't you be able to to use joint.N.motor-pos-fb to align the knife?

well i have my first real issue with this build. the X axis stepper tapped out on me today. to be fair i was giving it a workout as usual
the funny part is i made a video and got thought the first one fine but only made it halfway through the next one

I'm pretty sure i stripped something out on the internal parts of the motor which is a first for me. i guess if you mess around with this stuff long enough you run into just about everything

i installed new version 2.9.4 and have problem, old 2.8.4 working well and no problems, now i have big problems, if i try open new G-code in ro linuxcnc "open code", then search file location windows go all time black screen and go back to login site. same than has boot all computer, why. same this doing if i try open code come black screen and then go back to open file location first 1-2 time and 3 time go main login screen and has closed all linuxcnc and computer.
but if i open g:code  not search rows what file and were have what open, only click open no problem and open code and run cnc good, but if open search rows were file have come all time black screen and go back to main login site again and all softwares has closed, 
sorry my english not can tell better what is problem. same if open linuxcnc sometime screen stay blinking wrong and any buttons not can use, need end linuxcnc software and open again then no blinkink screen and can use normal. blinking mean all pictures blink some have normal some black and display blink ad shake.

In a terminal enter:

halcmd show pin <PIN NAME>

you could try something this:
linuxcnc.org/docs/devel/html/gui/gstat.h...mponent_code_pattern

but use the message 's-code-changed'

Many thanks. I'll give it a go.

DISPLAY_JOINT = 4
DISPLAY_JOINT_NAME = A
[GEOMETRY]
AXIS_A_JOINT = 4
AXIS_A_TYPE = ROTARY
AXIS_A_LENGTH = 30
[TRAJ]
COORDINATES = X Y Y Z A
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
DEFAULT_LINEAR_VELOCITY = 36
MAX_LINEAR_VELOCITY = 4.00
AXIS_A_JOINT = 4
-
Gray is OK, the rest is not, and it is all over the ini file.

Rod,
I might have explained things a bit poorly when I talked about the axis 'catching up'.

It's not how fast LinuxCNC itself responds, its the fact that axis motion commanded via hal pin isn't added to the queue. This means that if the rotary axis cannot move fast enough at a sharp corner, the other axes will not slow down in proportion. To compensate, you would have to feed slowly at all locations or write a program/post which implements smooth changes to slower speeds at corners.

I've had this issue using external offsets to simulate coordinated motion for surface mapping. This isn't a criticism of external offsets, it's just not the most ideal tool for that purpose if your X and Y axes are faster than the Z axis compensation is. This is because a standard implementation is commanding the Z offset using a hal pin corresponding to the current XY position, so you need to slow down at all positions to guarantee an acceptable Z positional tolerance. A tangential rotary axis will definitely suffer from this type of issue on sharp corners.

I understand what you're saying, and modularity is the aim for LinuxCNC, but surely since this tangential rotary axis I'm describing is ideally in coordinated motion with the other axes, it makes sense for it to be directly controlled by the trajectory planner? And especially since I'm describing a case where the tangential angle is both generated by and used by the trajectory planner?

The trajectory planner already directly commands axes, so allowing it to slave a rotary axis to an attribute of the linear axes calculated by itself could make sense.

Also, please ignore some of my thoughts above about how the rotary axis might also be commanded with G-Code as well, I admit I got a bit carried away thinking about a more complex implementation before settling the basics. I just wanted to argue that there are benefits to this approach.

And, sorry if I've gone a bit off-topic for the core trajectory planner discussion, this is discussion of a hypothetical feature after all! Happy to carry on discussing this somewhere else!