Advanced Search

I added this to my g540.ini file in the HALUI section

MDI_COMMAND o<logpoint> CALL.

Then in in my PROGRAM_PREFIX directory (home//linuxcnc/nc_files)

I wrote logpoint.ngc containing:

o<logpoint> sub
(logopen, logfile.txt)
(log, #5420 #5421 #5422)
o<logpoint> endsub
m2

and created an empty file logfile.txt in the nc_files folder

What do I do to actually run the command? I get an 'unknown word' error typing logpoint into the MDI window. If I run the logpoint.ngc file from the main page nothing seems to happen.

I trried the links in Andy's post above and they went to 404 error pages.

Thanks. Like I said, I am no whiz at this stuff...

Boxford have been making machine tools for a long time:
www.lathes.co.uk/boxford/index.html
And are still around today:
www.boxford.co.uk/cnc-machining-centres/

It's called "Phil" to rhyme with "Mill".
Maybe they also had a Dave the Lathe?

Where did you get it from? This has a vague feeling of hackspace humour.

Cant do this anymore bye all wrote:

Whilst the Mesa hardware is quite complex (firmware wise) it requires a computer running Linuxcnc to instruct as to what to do.

This is true in the context of LinuxCNC (and this forum) but Mesa do have alternative firmwares that perform motion control in the FPGA. 

store.mesanet.com/index.php?route=produc...th=65&product_id=163

Is also on linuxcnc. But then in development. Just to cheer you up.


 

There's some generic information here:

linuxcnc.org/docs/html/getting-started/u...e_to_the_new_version

But it might be better to just ask here on the forum with an appropriate topic, like
 "How do I update LinuxCNC to the latest"

etc



 

Which one is that?

PCW,

Okay, I am trying to start with 2.9.3 but am having some trouble, is this just done through the terminal? Do you happen to know the commands to do it? Do I need to find 2.9.3 and install the package on my machine first? 

If it is not too much trouble I could go straight to 2.10.  But I have found zero info on how to do that..

I am running bookworm.  I know that I tried to download whatever was best and most recommended when I set this machine up. 

Thank you.

Best,
-Dylan

2.5 is quite ancient. Maybe have a look at
github.com/jethornton/position-logger


Or simply the subroutine posted above:

Ok,

Now, to cheer you all up,  i just put here some movies i made tonight.

It might be supported by 2.9.3 if not then you must use 2.10

You should be able to upgrade to 2.9.3 with the package manager
if you are running s normal Debian LinuxCNC release

PCW,

Thank you.

Okay, as best I can tell I am running 2.9.0 (that is what is show at the top of my axis gui and what I see when I use linuxcnc -v).  You reminded me that Peter said something about needing 2.10.. Do you know if I need 2.10?

Can I update linuxCNC? Do I have to wipe the entire machine or can I just update? Will I loose any system configuration data if I do this or will that all be stored in my machine folder? 

Best,
-Dylan

Looks like you are possible running too old of a LinuxCNC version to support the periodm
though in this case, LinuxCNC should report an unknown module number.

Here's what I get for periodm pins and parameters on the 7I96S

halcmd show all | grep periodm

    35  u32   I/O            0x00000001  hm2_7i96s.0.periodm.00.averages
    35  float OUT           0                    hm2_7i96s.0.periodm.00.duty_cycle
    35  float IN               0                    hm2_7i96s.0.periodm.00.duty_cycle_offset
    35  float IN              100                 hm2_7i96s.0.periodm.00.duty_cycle_scale
    35  float IN               1                    hm2_7i96s.0.periodm.00.filtertc_us
    35  float OUT            0                    hm2_7i96s.0.periodm.00.frequency
    35  bit   OUT             FALSE             hm2_7i96s.0.periodm.00.input_status
    35  bit   I/O                FALSE            hm2_7i96s.0.periodm.00.invert
    35  float IN                1                    hm2_7i96s.0.periodm.00.minimum_frequency
    35  float OUT             0                    hm2_7i96s.0.periodm.00.period_us
    35  bit   OUT              FALSE            hm2_7i96s.0.periodm.00.valid
    35  float OUT              0                  hm2_7i96s.0.periodm.00.width_us

 

Well I now see there is pos_desired and pos_error but it looks like maybe a relative position.
relative to synced position?

I'm currently rewriting the i2c stuff from scratch,
until now, each device needed its own bus with its own pins.
now i can configure several per bus and also separate them again via multiplexer chip

 

was a lot of work, but this is only the config of one i2c-master, you can also create several, on different pins with different speeds.

I'm still testing and not all the types I've created are working properly yet, but I'm hopeful