Advanced Search

Thank you, I managed to get the machine up and running now.
I fixed the errors in the ini and the glade file (wrong labels).

However, if I try to update to LinuxCNC via, I receive the following error:Stating that the repo is not signed.
This is my linuxcnc.list:The key lives in /usr/share/keyrings/linuxcnc.gpg
What am I doing wrong here?

Thanks.... I have working configs for TC3 and it works well but if I mirror them to lcec ... probing not working at all ... I did custom component to use the internal probing but I can not use them because of I do not know ...

I have contacted all members which are more suitable to do explain me whats going on from this forum but no answers from anybody at all ... 

maybe during the winter there will be more itteractions between us

I'm waiting for some parts to turn up, going to build a power supply- three phase rectifier and 4 large caps, the fanuc one I've been using is basically a bridge rectifier I'm not sure how good the caps are,  if I power it up it displays a fault code. It has been 2metres under floodwater (two washing machines in 'merican speak). So i don't really trust it. The issues I have are during hard acceleration from stopped, or high speed travel(rapid moves). Say I'm moving an axis 8in - 200mm, it will throw an error at around the 7in mark, this i can fix if I lower the travel speed a bit. I never lose encoder position but I geuss the mesa cards have that under control.  I would have preferred an Ethernet style card, but not much was available during covid etc. I don't believe the computer is the issue from tests I've done and the bios settings in place etc. It never shows any errors about realtime etc.

Ul wrote:

Ist ein Oszilloskop vorhanden? Falls ja, einfach ans Glasmaßstab anschließen, auf single shot stellen, Triggerspannung einstellen und die Achse joggen.
Ansonsten kannst du probieren mit dem Signal einen MOSFET und damit eine LED zu schalten (mit Diode in Serie am Gate, damit er auch geschaltet bleibt). Wenn bekannt ist, wo das Signal ist, kann man die Stelle anfahren und die genaue Spannung mit dem Multimeter messen. 


 

Nein, ich habe leider kein Oszilloskop und selbst wenn, es würde ja nichts ändern, wenn das Oszi ein schwaches Signal erkennt, aber LinuxCNC nichts damit anfangen kann weil es einfach zu schwach ist.
Ich habe mir einfach die falschen GMS ausgesucht, hätte ich da vorher danach recherchiert, dann hätte ich wohl andere genommen.

Es ist wie es ist und es bleibt auch so

Danke für den Tipp

Gruß
Olli

I just found out that I am subscribed to your youtube channel since over 4 years ago. Very interesting videos about your mill and linuxcnc. Thanks a lot.

Hi, JT! 
thanks a lot. 
Its works fine.
Also im used parent.slider1.setSliderPosition(int) for setting needed value with 'if' to controlling the range without changing min/max.

Best regards
 

I guess one way would be to loop back the commanded position to the feedback position
when homing, by using the mux2 component.

Sorry, put reply in wrong thread...

Hello friends,

I want to make LCNC "Unhome" when power-off (servo-off).

I'm using AXIS. 

How do I do that ?

 

andypugh wrote:

This isn't an answer to your question, but have you tried hal_gpio on the Odroid?

 

Actually no, I knew of the component but I don't think it dawned on me that it used gpiod. In that case it would certainly work for something like an MCP23017 or a different I2C IO expander. The catch there is I don't know if it would technically be "realtime" unless an IRQ was attached via interrupt GPIO. I believe that specific driver will run in polling mode if an IRQ isn't attached. I could be wrong about that. This would be limited to GPIO as they have to register as gpiochips. In my head I was thinking of a component that would pretty much do exactly this but be expanded out to use other types of chips like clockgens and ADCs. Some clockgens have good command control so they could be used like a Mesa stepgen with a GPIO pin for direction. Maybe it's better just to split up the components but then it's the whole segmentation thing, I've been messing with LinuxCNC for about a decade and it didn't even dawn on me that hal_gpio used gpiod. So it'd be great to do an all-in-one component but that might get very messy making sure all the drivers are loaded etc.

andypugh post=335457 userid=723I was actually wondering the same thing about the serial port las month:

sourceforge.net/p/emc/mailman/emc-develo...arg.org/#msg59226340

Maybe a realtime modbus driver through the onboard serial port could work, for example.

If you can drive the serial port by sending bytes with outb() / inb() it might work, though you would end up having to re-invent the drivers as non-blocking code.

I've been asking about RT serial around here for over a year now, you're popped in on one or 2 of the threads. I definately would not use modbus. RS485 is (generally) half duplex and requires flow control, it's multi-drop, etc. I don't think Modbus can ever be any more realtime than USB but I could be wrong. My Idea for using UART is single host interface just like Mesa SmartSerial and just sticking to simple full duplex just as Smart Serial does.

I've been banging chatgpt from every direction on the UART thing and the result is the Intel 8250 driver is pretty much perfect as is for real time with a custom protocol. Might sound like blasphemy to someone like you who know what they're doing but I've found that if you hit the bot with enough contention you can come up with fairly solid answers in the end. Seems just plain UART with the FIFO interrupts is just fine, no hardware flow control or anything else required.

Another somewhat sticky point that I didn't bother mentioning above is because there is no real GPIO on the H-series boards I need to get creative for a hardware interrupt for the I2C chips. These don't have a GPIO controller like some other boards do. It seems the CTS (and RTS) pins can be stolen from the UART and repurposed and likely still have a usable UART just without flow control. So I actually need a kernel module to set that up. That's what actually got me back on this kick, I was messing with an vendor I2C touchscreen kernel driver. That requires the I2C bus with an INT (IRQ input) and RES (output) GPIO pins. I was able to get about halfway there hanging the IO expander off the I2C bus and binding the MCP pins as the IO it almost worked, problem was I couldn't generate a real interrupt without an single IRQ capable input pin so I gave up at the time. Once I realized I might be able to steal the CTS pin for the I2C interrupt it snowballed back into me thinking "can I get this stuff working in LinuxCNC?"

So at the moment I'm just trying to get the CTS interrupt working with the MCP23017. If that works I might just try it out with the hal_gpio component. At some point I'll see if I can get a basic RT UART comp going. Once I know it all will probably work I'll try making it useful.

How to disable following error while homing ?

Background:
When we use "internal homing function" with EtherCAT servo driver, 
command position from LCNC and feedback position difference become large.
We can avoid this by setting f_error with large number, but I don't think it is good idea.

Are there any settings or something to do this ?
 

Hi Cmorley

I made some adjustments to the brushed_metal_color file. Mainly to improve gcode readability (the white font was difficult to see).

If there's a space between the axis letter and the value in the gcode, the letter and value colors aren't applied. Is it possible to fix this?

Another idea and suggestion. I'd like the macro button (the last, first, or maybe all buttons) to have a drop-down menu so I can easily add more macros within easy reach. Something similar to the screenshot.

Those photos are very clear and high resolution.

I can see the board better than I could with my own eyes.

Could you post some pictures of the non-broken board (so we can see what it should look like)?

I think film caps are usually ok.

You can probably get away with all the caps as they are as filter caps are usually oversized, meaning the drive should function fine, even if the caps have degraded, though I suppose it couldn't hurt.

I'm typing this on a keyboard which I accidentally plugged into reverse voltage (stupid Apple decided to use an identical connector, but changed the pinout); the chip got hot, I smelled "magic smoke", yet the keyboard somehow continues to function without any issue.

Burnt ≠ broken, though it's certainly not optimal.

Hi Endian, I don't have anything for LCNC but I think I have some probing routines in a TwinCAT project and I can see if there is anything helpful in there.

I also posted an issue to your codeberg page for your converter for the EL3074.