Advanced Search

Hi Arciera,

On my pc : libc6 is already the newest version (2.31-13+deb11u10).

Thanks, and will it run after this:

Since Mbed has been abandoned as a project many are saying that Remora is a dead end project.
What should Mbed be replaced with?
Save the libraries?
Make Remora compatible with something else?

I don't believe that the RP2040 version uses any Mbed libs.

Hawk83 wrote:

Hi Andy.

Thank you for your reply.

I have read a bit about the carousel-component and it looks very good, but if I understand it correctly I can’t use it to drive an axis? My tool-carousel is configured as the C-axis on my machine.

But maybe I have misunderstood something?

Correct.

Carousel.comp can drive (via other HAL components) motors, but not a named axis/joint.

Theoretically one could somehow connect carousel.comp's output to a named-axis' inputs, but LCNC would get 'confused' and not be able to keep track of the axis actual position.  Carousel would be moving the axis outside of the trajectory planner's knowledge.

So you generally either choose to use carousel.comp to manage the ATC/turret positioning, or you use an axis.  Both require some additional 'thing' to choreograph the full  tool change sequence.  That thing can be .ngc subroutines, or Classic Ladder, or some murky (to me) python programming.

Andy advised me some time ago to use carousel.comp instead of an unused axis to control my ATC if possible.  His point was that it's rarely necessary to have the ATC motion synchronized (at the same time) with other axis/joints.  You move the head up, then you do something else, then the ATC rotates, etc.  Tool changes tend to be sequential steps, not lots of concurrent motion.

There are plenty of successful examples of ATC's being implemented as an axis.  But without discussing with the author I can't think of a reason why ATC-as-axis is preferred over carousel.comp.  Maybe being able to have finer control (hardware dependent) of the actual motion (accel, velocity, etc.)?

[bonus]
Now that I think about it, just about anything is possible in LCNC.  It might be possible to use carousel to drive a named axis via the .ngc subroutines, but that seems like a horrible Rube Goldberg scheme.  I can't think of a scenario where that double-layer of complexity would be the most efficient configuration.

I would think that power (which is proportional to PWM duty cycle)
vs temperature would be quite non-linear by nature. The "lincurve"
component might be useful to linearize the PWM settings.
 

well after a few days messing with the ssr and the hot wire I have discovered that the relay definitely  doesn't like fast
switching speeds . Even if the wire itself doesn't care I can't seem to get enough linearity from the ssr. just running it
on a stand alone pwm controller. Fortunately I can find high amp mosfet 3D printer bed heater boards that can handle
it. I am still working on getting the linuxcnc HAL to work the way I want. Oh well if it was easy every body would be
doing it.

Hi all, hi scotta,
I still have a problem with my NVMPG, like in forum.linuxcnc.org/18-computer/44828-rem...rd?start=1710#298883 already stated. I have the same behaviour.
I can control the axis with the NVMPG, switch the axis and scales, but I don't see anything useful on the NVMPG.
Did someone succeed in making the display work?
I use a EC500 with the firmware Remora-RT1052-cpp version 3.1.2.

Regards, hanskuster

I have same issue, does anyone fixed it?
Thanks,
Bharat

I just tried the app-image on a new bookworm installation, Here is what I get;

Thanks for the reply!I tried the installation again.I got to the point where the machine was working, but REMAP didn't work.I want to get back to that point soon.MDI↓T1 M6↓Move to [CHANGE_POSITION]↓Nothing happens. No dialog box appears.I don't know why, but I'm sure I'm missing something.No matter how many times I try to configure it, I can't keep up with it.

Hi Jdowsonjr,

The project has moved from github to codeberg. The reason is the required 2 step verification github requires from it sheeps.

codeberg.org/skynet/hal-core.git

i see the last commit was 4 months ago on the branch of Grotius
Yes, i can't use this account anymore.

how are things going?
Currently working on the path deviation algoritme that processes the G64 P.. Q.. gcode values.

what can i do to help?
Validate if the app-image runs : filetransfer.io/data-package/wvAnmLrd#link

Then you could try to build & run the application from source.
Use qt to load the project by opening the cmakelists.txt file.
Then look around and get an idea how things are done. Then you can start adding code to the
subject you are interested in.

Unfortunately Mesa CT does not know which daughter card you might want use for a spindle when using a card like the 7i92T. But that gives me something to work on in between working the Flex GUI.

JT

wow you are truly awsome

Many thanks

I have a plasma with 6 steppers as well

It's working great with qtplasmac, 7i96s, 2thcads one for the one for ohmic, parallel port breakout for the other steppers board running on a ryzen 1600

Couldn't recommend it enough. Use 2.9.2 if you want the rotary to work 2.10 wasn't working with the sheetcam post as of a few months ago.

@kzali

have add new board config for the tangoboard, but not complete for now:

PYTHONPATH=. bin/rio-setup riocore/configs/Tangoboard/config.json

 

so at least have download 2.9.2-dev package and install it, upgrade ethercat as repositories suggested me ... NOT upgrade kernel. After these ethercat stop to connect to lcnc but not stop to work (lcsc_conf not find error become present) ..... so re-install linuxcnc-ethercat package and all work again like a charm.

for first problem, solution is: install -dev package, install a rip version until "make" stesp ...whitout really install .... only compile it. At these point all lcnc libs become avaiable for new c++ gui app.

May be not needed, never try, for sure hal-priv.h is difficult to reach if in root folder  ... for sure if need to compile a new kinematics for example .... have a rip install for only compile is an helph. After compiled kins or libs you can move in right folder of your lcnc real installation.

regards