Advanced Search

Are you trying to install a dev work station or just a machine control? If a machine control, use the apt installation.

kcjengr.github.io/probe_basic/stable_quick_start_apt.html

Hello,
this is my almost working postgui. This works is Input-04 is a switch. But i want to use a push button. What can i do?

#[Startknopf]
loadrt or2
addf or2.0 servo-thread

loadrt not #mit diesem Befehl wird ein not.in/out in die Pins geladen
addf not.0 servo-thread
net Start.not.out => not.0.out # hier wird not.0.out startbar gemacht

net Start.ext.an <= gladevcp.Start => or2.0.in0
net Start.ext.an1 <= hm2_7i76e.0.7i76.0.0.input-04 => or2.0.in1
net Start.or <= or2.0.out => hm2_7i76e.0.7i76.0.0.output-05 => halui.machine.on => not.0.in # Eingang not.0.in wird über den or2.0.out gesetzt

net Start.not.out => not.0.out => hm2_7i76e.0.7i76.0.0.output-06 => halui.machine.off
net MachineLED <= halui.machine.is-on => gladevcp.led_Startstopp

cakeslob wrote:

Hey, Ive been meaning to work on this and Dmitry's up camera, but before that I needed to build/install/configure my hardware with c axis before I started on this.

Nothing against qt/glade, but for simplicity I am trying to do everything in an Axis tab with tk/tcl/tkinter, and probably using usercommand file so that is my challenge.

The usercommand file Ive included is your initial file, but with a camera tab created in axis. I am using this as a starting point.

first hurdle : conflicting mainloops between axis and opencv

here is solutions, but Im trying to understand them first (I struggle with OOP)

stackoverflow.com/questions/72318466/how...ow-inside-tkinter-ui
github.com/furas/python-cv2-streams-viewer




Hello,  this is a bit off topic, but does the axis C component work perfectly? Thank you for your feedback

 

Hello, here is a functional version for port // that may help.

Thanks Peter,
Can you shed any light on whether the Mesa Modbus page (linuxcnc.org/docs/stable/html/drivers/mesa_modbus.html) relates to hm2_modbus?

My antique Dell Optiplex does not boot from CDROM anymore.  LinuxCNC 2.9.4, which has worked beautifully for many months, is now hanging the PC.  I attempted to use Package Manager to reinstall it.  It fails.  I tried to uninstall it.  It fails, so I guess that I need to reinstall from a USB drive, which is how I installed the now Zombie version.  I do not remember how I burned the ISO to USB drive from Windows.  ImgBurn only burns to CDROM drives.  Rufus does not give me a way to select a USB drive.  Help!

I don't have access to it today but I have an example GS10 VFD configuration for hm2_modbus
that I can post tomorrow.

It's been running on a test config for several months 24/7 without any issues.
 

Hi all,
I'm working on a machine with 7i96s for brains and a 7i75 for IO. I'm adding a fuling BD612 VFD so i can use the high rpms that the spindle is capable of, and I'd like to do this via modbus.

I'm aware of the hm2_modbus and mesambccc manpages as well as the docs page Mesa Modbus, but... I can't tell if they are referring to the same thing. It seems clear that vfd_modbus and mb2hal are different ways to do this.
I'd be grateful if someone could confirm that these refer to the same thing or different things...

It's clear that hm2_modbus and mesambccc are parts of the same system - does anyone have an example file(s) for setting these up? I'm happy to spend hours with the manpages and guide but get on far better reading and tweaking existing code, than trying to write it myself from scratch.

I've flashed the 7i96s_pktv3.bin bitfile successfully, not sure of next steps. 

Many thanks,
Andy

 

Does the drive itself power down on a fault?

7I96S        DRIVE CN3

ENCA+          9
ENCA-         18
ENCB+        17
ENCB-           8
IDX+             7
IDX-            16

STEP+         2
STEP-         11
DIR+           4
DIR -          13

GND          12   (encoder ground= 7I96 TB2 pin 9 )
 

I see where you're coming from. I very much don't agree with it, but that's just me.

I compiled my first kernel for RedHat 7 in 2001 I think. had no idea what I'm doing but since then, the novelty of compiling kernels - or anything, really - has worn down, mildly speaking. I'm a software engineer by trade, very lazy at that, and I prefer to a) update things as soon as possible, because the more versions I skip, the harder the update would be, and b) don't do work if I can avoid it - don't write code if I can use a library, don't compile my own kernel if a pre-built one is available, don't configure things that I don't need configured, etc., because if I do that, it means I now own that thing, and if there is an issue with it, it is my responsibility if not to fix it, then to at least investigate if the issue was caused by my changes.

I guess we have differing world views, and that's perfectly alright!

Config attached.

One of my previous posts as a zip archive of the rpi-image builder used to build the RPi5 & RPi4 images.

I'm of the opinion of keeping the kernel locked is not such a bad idea. It prevents users from messing things up.
It can also save "I've updated my kernel and I have xxyyzz issues" and sometimes trying to help some people out is like pulling teeth. Sometimes you have to ask for the same information a couple of times because for whatever reason they don't think it's relevant. And sometimes Linuxcnc is a users first venture in Linux, after maybe using Mach or grbl. There's no reason why an experienced user can't use alternative kernels if required or wanted.
And TBH I don't think kernel building is such a large task. The first one I built was around the time of Redhat 6.0 on a 486 with 32MB RAM (Maybe around '99 or something like that). Yes it was a very, very slow task. Back in the day were one had to hand edit files to get a dial up connection.

As for updates.....there's some user's that have machines running on Ubuntu based versions of emc2. Bit like the ecu of a car\truck\snow mobile\jetski\road bike\off road bike or similar, not often an owner will think of updates if any are available.

unknown wrote:

Could you point me to any papers, references or any such peer reviewed articles explaining why the 16k page kernel is broken by design.

yeah no, sorry, I have used too strong wording there - 16k pages used to cause compatibility issues with older software, but I believe that has been a non-issue for several years now.

unknown wrote:

Ok you're telling me not to use a kernel that I have practical experience and have not had a single crash or anything similar.

not really, because I - still - have not seen the exact kernel configs that you've used in your images. are they on github somewhere?

all I'm saying is that the ONLY difference between bcm2711 and bcm2712 configs is that the latter enables 16k pages. we don't need them, the performance increase is practically zero for our application - LinuxCNC does not allocate huge amounts of memory in runtime. 4k pages work just fine and have been used since forever, bcm2711 config works perfectly on Pi 5, I've been making chips with it for a few months now without issues.

I don't get it - if you have a working vendor-provided RT kernel that you can just apt install, why bother building your own with a useless feature that no one needs?

Faults from stepper drivers are wired as inputs on mesa card. When fault is triggered mesa triggers emergency stop.

Ok you're telling me not to use a kernel that I have practical experience and have not had a single crash or anything similar. Neither have any users reported any crashes. I think an uptime of 39 days and being able to start Linuxcnc at anytime during that period with no crashes, latency errors or any other such issues proves to me that the kernel is solid and stable.
Before using it on the mill, I had been using to test some Mesa clones one based on a 7c81 and another more less based on the 7i92 design. I've also tested Ollie's riocore system, on the same 7c81 clone hardware early this year, before Oliie got his hands on a genuine Mesa 7c81 that he has made riocore formware for.
Could you point me to any papers, references or any such peer reviewed articles explaining why the 16k page kernel is broken by design.

So this time I will stand by my choices for the RPi5. Unless of course you can provide hard evidence as requested above.

Even this page says to config 2711 for RPi4 to RPi3 and 2712 for RPi5.
www.raspberrypi.com/documentation/computers/linux_kernel.html