Advanced Search

Hi Tommy,
I did it, and there was no Lan card reported. Even, if I tried to add new connection, didn't work.

  With the RPI4 being a viable contender albeit marginal for linuxcnc I thought I'd share some results i got from a stock RPI5 with a SD and with the addition of a nvme hat. I think they have knocked it out of the park with this one.The first one is with a nvme ssd hat added and the second one is with the standard SD card.  

Hello,

Sometimes try to tinker something that roughly corresponds to functionality, which I am looking for for Qtdragon.
I have little idea what I copied together. But it only runs in studio code how to explain the Linuxcnc, so I am light years away to understand it.
Here is the code snippet:

import cv2

cap = cv2.VideoCapture(0)
cap.set(cv2.CAP_PROP_FRAME_WIDTH, 1600)
cap.set(cv2.CAP_PROP_FRAME_HEIGHT, 1200)

while True:
ret_val, img = cap.read()
down_width = 800
down_height = 600
down_points = (down_width, down_height)
img = cv2.resize(img, down_points, interpolation= cv2.INTER_AREA)
cv2.imshow('my webcam', img)

if cv2.waitKey(1) == 27:
break # esc to quit
cap.release()
cv2.destroyAllWindows()

Best regards and have a nice weekend, Frank.
Translation errors come from Google.

Maybe it is in the homing file? Perhaps I can change the homing file to rehome rather than return to home if that it is indeed the case that it is not actually rehoming?

Ok, thanks

No jumpers need to be changed, and you and run the logic side of the 7I76E on 5V, but
since the field I/O side needs 12/24V, there usually is not much point.

Hello,I would like to operate my Mesa7i76e with an external 5V power supply. Unfortunately, I cannot find any information in the documentation about whether I need to change any jumpers and, if so, which ones. Can you help?Thank you.

thank you as always for your help.
I managed to reverse the encoder scale correctly
I must have something wrong with my closed loop signal
If I jog, on the first order; my pid.x.command is stuck and don't go back to 0. don't pay attention to the enc-count, this is before the *-1 scale

 

Добрый день.
Подключил пульт, в виртуальном станке axis все работает, но реальный постоянно отваливается при попытке передвигать маховиком с ошибкой joint 0 following error при движении осью Х и остальными соответственно.
Управление клавишами при этом происходит штатно.
В чем может быть проблема?

1. Z is not connected to the joint. Check the hal file how it is done for X and Y and do the same way for Z.

2. To enable DC
refClockSyncCycles= -1000 (or any other negative or positive number you like to use, not 0)
Use the line  <dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
and remove the watchog line. Normally don't need to specify that, there is a default watchdog of 100 ms
If the drive absolutely wants a watchdog statement, use the line <watchdog divider="2498" intervals="1000"/>
 

Good work mate.

For those who like it, I've got an Armbian image ready with Linux 6.17 Cinnamon which is ready to go.
drive.google.com/drive/folders/1_WMbZC0k...ceNNI?usp=drive_link

Last core already isolated
Included sata overlay (which had to be adjusted)
LinuxCNC installed
HDMI audio works
GPU acceleration works
VPU acceleration doesn't work in the web browsers, 1080p on YouTube works fine
IRQ of ethernet automatically pinned to core 5

You rock. Thank you.

For the arc volts, from the torch-, it splits to two wires that go to 2 transformers? and then to the rectifier.
In the attached pic, I circled the torch- wire route in red and the work+ in white.
Should I just attach to one torch- wire at the rectifier or ?

Also, do you mean one 1Mohm/2w on each wire for a total of 2 resistors or two 1Mohm/2w on each wire for a total 4 resistors?

 

Yeah, somehow i managed to miss this.
When in doubt, more C4 !!!
Use relays as you have in the drawing for ARCOK, do not wire anything to Mesa, do a test cut and check if the relay closes while cutting. Do the same thing for TorchON but reversed, meaning contacts go to plasma and coil on the Mesa side but do not wire to Mesa just use whatever can give 15-24V and trigger the relay with it see if the torch fires. After this, you can wire stuff to Mesa, one at a time, test, wire, test....
As for the Arc Voltage, find the big rectifiers, usually with big aluminium heatsinks and find the positive and negative, wire two short wires to each, wire 2 of 1MOhm/2W resistors to each of those wires, on the other side of the resistors wire two thinner wires prefferably shielded and send those to Mesa THCAD, mind the polarity, although nothing will happen if you do mix the polarity but you will have no voltage reading on screen.
Make positively and ultimately sure you have the power cord and plug under your foot while adding this, i do that always to prevent someone somehow getting the idea that it belongs plugged to the wall...while i have both hands inside!

Glad you got that sorted John. Just wanted to mention that I did somewhat similar - wanted to "move the WiFi 10ft away to the top of the HMI box" since that's the highest point of the machine.  Looked at external antennas but none had a cable long enough. So have Rpi --> industrial USB hub --> 10ft USB cable to a tiny  8821CU  dongle with the antenna sticking out of the HMI.  Trap for young players: that particular dongle already has a driver included in the Rpi .iso, but that driver absolutely would not work.  Had to follow the directions at the link to compile a special new driver for it.  After a lot of head-scratching and configuration, have the on-board WiFi disabled and the dongle enabled, and it works a treat.  Cheers.