Advanced Search

I know you already have two 7i96 cards, but perhaps using only one of them with a 7i78 daughter card connected to the expansion port of the 7i96 might be a better option than the two 7i96 cards to get extra stepgen outputs?

Did you change the IP address on one of the 7i96 cards so that they are not the same? Set the first as 10.10.10.10 and the second as 10.10.10.11. You have to use the Mesa flash utility to set the address on the card. Set the static IP for the nic on your Linuxcnc PC to 10.10.10.100 (or something other than 10.10.10.10 or 10.10.10.11 but in the same range.)

I believe you can use a switch, but the switch and the PCs ethernet port need to be dedicated only to this use. If you want to also have an ethernet network/internet connection you will need a second nic on the pc for that.

Here's a thread with instructions from Peter at Mesa
www.forum.linuxcnc.org/38-general-linuxc...sa-7i92-via-ethernet

Hello,
When I implement the XHC-WHB04B-4 handwheel in LinuxCNC, my milling motor no longer receives a speed command. I had to remove some commands from the *.hal file to prevent errors from occurring at startup. My files are attached.
 

Am I understanding correct your brushed DC servo motors are 140 volts? That leads me to think your analog servo drive is likely designed to operate on 120V power. 120VAC rectified to 170VDC is plenty good.

If the analog servo drive uses a bridge rectifier, then, no, you cannot connect negative to ground. You will have smoke and sparks. Unless it is powered by an isolated 120VAC source (some do it like that) Then they sometimes ground the negative side. I would check how it was wired and keep that the same.

More detailed photos of the servo drives would help a lot.

Your power-up test might get more realistic results if you leave the servo motors wired to the drives and rather mechanically uncouple the motors from the axis drive-train to avoid run-away accidents. 1.5 volts DC should be perfect for the speed command test. If your servo drives have good speed regulation, trying to do this without a motor wired to it would cause it to either go full power or fault because it did not receive speed feedback from the motor.

I have got my repaired 7i76eu board returned from Mesa, Thanks again Peter. I have all the limits and estops showing now on Hal show and they are working correctly. I try to home all or jog and the machine just vibrates and shacks until I hit the estop. I have checked everything I can think of. Except for the inputs for limits and estops etc that weren't working before I could get the machine to move, now I can't???? Everything was hooked up as it was before I don't think anything has changed.

Yes. I shelved this idea. The faceplate on the VFD made it quite clear that it isn't going to take 240. I have a buckboost to take 240 to 272. Hoping that this will give me enough power for the analog drives. Will use 240V single phase to power a VFD for a much lower HP spindle. Will also use 240V single phase to power any additional drives. Not super sure exactly which MESA setup I'm going with yet. Have to confirm that the analog drives are good first. I was wondering if I could just hook up the 10V to a 1.5V battery and make the drives move the steppers.

- I'm going to first disconnect the brushed servos from the analong drives. Power leads, encoders, everything.
- I guess I can first check the DC bus this by sending in 120V. This should give me close to 170VDC.
- If math serves me right, the DC bus should be 390V rectified with the single 277V leg. With my transformer, it should be 385V. Wondering if the drive cares whether the negative leg of the DC bus input is tied to ground. If it does matter, I'm not sure how to proceed from here. Not exactly sure how to check.
- From here, I am guessing that connecting a 1.5V battery to the drive "should" make the drive send out a tiny bit of the DC bus DC voltage. Since I'm not connecting it to anything, i should be fine. 

Will try to understand more from first principles but most appreciate any pointers.

I thought maybe I could be missing some package, so searched apt for things which might be related to Qt and platform theme, and found that only qt5-gtk2-platformtheme was installed - none for qt6.  So then I tried installing qt6-xdgdesktopportal-platformtheme and qt6-gtk-platformtheme but neither made any difference.  So this appears to be more involved than initially suspected.

Hi all, I'm working on moving from an older (Linuxcnc 2.8) Axis config to a Probe Basic config after getting a new spindle for my router.

I have successfully gotten the basics working and have even gotten the ATC functions mostly where I want them. (Huge thanks for the the starting point that is the Probe Basic screen set and all the macros)

I am running into trouble integrating my XHC-WHB04B-6 pendant. It works just how I want it to in the old Axis configuration, and in fact that configuration runs just fine under Linuxcnc 2.9 and the pendant works in that config.

However, in Probe Basic the pendant produces stuttery motion when jogging both in step mode and in continuous mode. It also will not register all pulses or clicks of the jog wheel when the wheel is spun quickly. If I slowly click the wheel in step mode (say 1 click per second) I get each step translated into machine motion, but if I quickly spin the jog wheel, I will only get a small fraction of the wheel clicks actually translating into machine motion.

General info:
-  What Linux OS being used including kernel type?
> Debian GNU/Linux 12 (bookworm)
> Kernel version: 6.1.0-44-rt-amd64

-  What version of Linuxcnc is installed?
> 2.9.8

-  What version of QtPyVCP and Probe Basic is installed?
> Probe Basic version: 0.6.6

-  How did you install Probe Basic? Quickstart guide? Dev Guide? 
> Probe Basic APT stable install following the guide here: kcjengr.github.io/probe_basic/index.html

-  Have you gone through your ini and hal files and compared to the sim config files to make any changes needed?
> Yes, Probe Basic is functioning, just the integration with the pendant is giving me headaches

-  Have you added all of the necessary files in your config folder that probe basic needs to run?
> Yes

I attached the hal files ini files and pendant hal files for the two configs. (note i renamed the pendant.hal file for the Odroid config so that there were not two of the same file name)

Please take a look and let me know if more info will make the problem easier to diagnose.

Thanks!
 

You need two network cards for that, no switch.

Rod, i refrained from giving up such info.

tommylight wrote:

I can not find Borax here, nor Boric acid, nor KCl, nor well anything really, even IPA i have to ask friends that own shampoo making factories for it.
But we have 18% HCl and 25% H2SO4 anywhere... and you can buy ammonium nitrate in 50KG bags for 20 Euro! With no permit or any paper!
I can not build a hobby rocket nor get rid of the bugs (every spring tiny flying ants, by the millions), but blowing up half a city is easy!

Just add diesel and perhaps a detonator and you will be golden! I once watched (from a distance) mud blown out of a dried up water hole with 6 bags of nitram fertiliser and a small stick of gelicnite to hold the detonator and the results were spectacular! Even more amazing was the guy was actually was still live. He hid behind a tree and fired the detonator with the battery from his tractor and a far too short (for me) roll of electrical cable. Car sized blobs of mud beside the hole!

 Hello. Recently I’ve had problems controlling XYZAB because in fact I have two YY motors, so I need 6 Stepgens to avoid some issues I was having.  I added a 7i96s card and a switch, and added 10.10.10.11 and 10.10.10.12 in the Ethernet connections, also with gate 8. I’m not sure how to proceed with the ini/hal changes, tried some ideas around adding a second card IP, card1 read and write, and others, but no matter how, I couldn’t power up the system with both cards. Is there a base config o could work with to have both cards working? Any tips in having both cards working? I can ping both IPs, but I’m not sure if i won’t have other connectivity issues. Thank you in advance.

You are welcomed, always.

By the way, this is the HAL and COMP I have gotten working to control the turret.

 

"On second thought, in this kind of project I might use nested PID" that sounds super fancy, but I see two problems with it for me. For one, I would not know where even to start implementing this. And second, the motor RPM that I get is way too inaccurate for PID to effectively work.

I get the value from a 4–20 mA current from the VFD. I then have a 470 ohm resistor very close to my 7i84 that has the ADC to give me the signal I then process to get an RPM. The signal is rock solid, with no noticeable jitter at all, but it is only an 8-bit ADC, and my voltage is between 1.7 V and a little over 9 V, using less than half of the ADC range.

For getting an approximate gear ratio, this seems fine, but not for actual speed control, at least that is what I think. I may very well be wrong.

The feedback that I used for the spindle is an encoder on the spindle, so I am very confident in this feedback being good. The stuff I am doing with the motor RPM I really do not trust too much. The encoder also has an index, so threading is possible. I don’t want to change that either.

As to “This still leaves you to have to measure the adjustable gearing ratio between spindle and motor for properly scaling the speed command,” the variator is infinitely adjustable. That is why I think even a not completely accurate motor RPM and a really accurate spindle RPM to calculate the gearing ratio every servo cycle would do the trick.

So in a sense, this would only scale the error, as in: if commanded is 1000 and feedback is 800, the error would be -200. Now let’s say we are close to 1:1, then that does not really change, and we actually want the motor to go 200 RPM more.

Let’s say with the same commanded and feedback but a ratio of about 2:1—in that case, we need only about a 100 RPM change on the motor, so scaling the error with the ratio should do that. And as it is just a factor, it will never wildly change the system.

I am sorry if that makes sense only in my head. I have been banging my head against a wall here for some time now.

Regarding my problem 1, I think I have found the reason why the output is between 3000 and -3000. It is this line: [HMOT](CARD0).pwmgen.05.output-type 1
If I read the documentation correctly, it has to be:[HMOT](CARD0).pwmgen.05.output-type 0 to be 0 to 3000. I will see if that helps tomorrow.