Advanced Search

Chinese stuff is often a little hard to undertstand.

(The Chinese probably find our stuff even harder to understand)

SATA is usually magenta, orange, cyan, or dark grey.

PATA is a thin, wide black or light grey cable, which can have 2 or 3 plugs.

It's almost time to make V2....!!! (like for real)
Big enhancements in the work holding area. quick change 5 side vise indexing, and some other tricks. 430mm x 270mm/310mm travel And a 10 tool robodrill style tool changer.


 

 

 

For axis or joint jogging, there are HAL IN pins for jog-counts. For example, for axis jogging there is axis.L.jog-counts IN S32.

When movement is permitted (enable pin high, in manual mode, not at a soft limit etc) a change to the jog-counts pin will cause movement.
Since the jog is incremental, normally the value of the pin is increased incrementally by the control method (such as a jog wheel), not set to a specified value.

This means that there is potential for a backlog of incremental jog movements to be accumulated, if the rate at which the incremental logs are executed in one direction exceeds the rate at which the jog counts pin has changed.
This manifests as a continuous jog which ends once the backlog has been cleared.

My question is, is there currently any way of accessing the number of counts which make up this 'backlog'?
Or accessing an analogous value such as the DTG for the joint/axis if the backlog of jog counts is summed?
This data should exist in some form in the motion planner, so it should be possible to get it into a HAL OUT pin.

GStat does seem to have a get_jog_increments function, but since the other arguments reference GStat's internal jog parameters, so I think this just returns what was set by the set_jog_increments function.

In summary (as far as I know), there is an IN pin for jog counts, but no OUT pin which actually indicates how many counts are 'queued' in the motion planner.
Is it possible to make this into a HAL pin in a current installation?
Or what might be changed in the current motion planner to make this value a Stat/GStat attribute or HAL pin?

Thanks!

again, cheers once again for pointing me in the right direction.

unfortunately i'm still far to green to get a working hal snippet for pwm control, but chatGPT isn't... after a bit of back and forward this was the result:

setp lcec.0.0.PWM-OUT-0 98304000 #sets frequency to 1.5khz

loadrt scale count=1
loadrt conv_float_u32 count=1

addf scale.0 servo-thread
addf conv-float-u32.0 servo-thread

setp scale.0.gain 3.5

net gui-rpm spindle.0.speed-out => scale.0.in
net scaled-rpm scale.0.out => conv-float-u32.0.in
net rpm-u32 conv-float-u32.0.out => lcec.0.0.DUTY-OUT-0


i now have a working PWM out!

i did try outputting to analog out but there seems to be some problem with it, for example 20 000 rpm would output 3v, 10 000rpm would give 5v, 7500 rpm would output 2v. It's not the end of the world, but hopefully i can get it sussed at the very least for others that try this board.

once again,
cheers for the help to get a working PWM out!

Yes that may prove very valuable. The worst part I see is that this isn't a single country problem it's spreading
everywhere. It seem the powers that should never be don't like it when people don't follow the pushed narrative
or the easy in which things can be fact checked independently.  
I guess it's just another day in mouse utopia. 

It all started with websites like Quora and User Benchmarks back in the days and the subsequent invasion of blogs.
Now this is just a fallout form that as when so called AI hit and started multiplying like viruses, there is no going back to Wikipedia actually being very useful ever again.
-
While thinking about this, does anyone else think it is a good idea to make a topic about useful websites and video channels here on the forum? It might help a bit to slow down the extreme misinformation going on.

So I just came across this . All I can say is The internet is loosing it's usefulness.

It's in the image you downloaded. Look for the components folder I think it was called. Open that, you should see the Eth files. Open the terminal(command line) from here and run the halcomplie command that's in step 8 of the instructions. 

What did you do to fix it?

7i96/7I96S isolated inputs not working properly
usually means that the isolated input common
is not connected. (or connected to the wrong thing)

hi, i'm new to this cnc building and followed your guide on page 165 and was able to flash the firmware to the ec500v5 board but i'm a bit stuck at the moment.

i'm tring to complete step 8 install eth component but i have abolutely no clue what you mean with this step nor where to find the folder.

Hey group, 
Thanks for the help so far. I rewired my setup so that it looks nice now, but I have stumbled upon an interesting problem. Here is the description:

I added an earth connection to the power supplies and inside my breaker box. I rewired everything, and it was time to wire the home switches. Previously, I had wired them on the power supplies, which were for the motors, but now I got an extra power supply for them specifically (24V). 
I wired them 24 from the power supply to the normally closed AZ7121 home switches and from there to the Mesa 7i96s inputs (the optically insulated ones with the LED). For some reason, they were very dim, and the home switches were not working during home all. I started checking connections, and it seemed to be an Electrical problem.
First i found out that if i distributed how i wired them and placed them on multiple power supplies they lit up better.
Next i saw that the Init LED on the mesa card (RED LED) was on
Next i realized that if i took all of the input wires except one (the wires that went to the inputs of the card for the limit switches) the one input LED became dim, But if i simply plugged in another wire from another home switch into another input (but disconnecting it from its power supply, simply leaving it hanging) the LED on the input lit up (dimly) as well. 
Next, I opened the breaker box for the CNC machine and saw that the Earth connection was touching the metal rail on which the breaker is connected. Now, there was no visible connection of a Line wire to the rail, but when I moved the Earth away from the rail and restarted the Mesa card, The RED INIT LED stopped. 
Now, potentially, the earth touching the rail on which the breaker was connected somehow was a problem. (Don't know why)
But right now I still have the same problem where the input LEDs are properly ON, only when I have 4 Home switches connected to 4 different power supplies.
Also, measuring from Line to the Earth shows 18V, if that means anything. 

It definitely seems that I have done something wrong, but Nothing seems out of order. If anyone has experienced something similar or has any ideas I am open to trying. 

Thanks

I did try to follow the trail:

The error string displayed in the pop up comes from here:
github.com/LinuxCNC/linuxcnc/blob/master...cripts/axis.py#L1715
which calls
github.com/LinuxCNC/linuxcnc/blob/master...cripts/axis.py#L1579

The actual error is returned from 'gcode.strerror(result)' which seems to be this c++ function:
github.com/LinuxCNC/linuxcnc/blob/master.../gcodemodule.cc#L964

Why a user entry for a float value would be passed through all of that, I have no idea.

I had similar problems with my toolsetter, and initially used an AND gate - until the time I forgot to enable it (I used a manual signal, not motion.*) and crashed my toolsetter.  Then I tried smoothing, which worked OK.  It turns out the toolsetter is a good seismic monitor, and trips when I have issues with toolchanging

However, my comment here is... have you considered using a dummy probe move to retract the probe?