Advanced Search

I've been doing some research but I'm not sure what I'm doing.

Is there any mpg compatible with probe basic?

I edited a post above to indicate that the three BOBs have now been fully tested. Previously I had checked all the paths with an ohm meter, powered up one of the boards and checked some signals.

 

All three boards have been powered up and tested. All inputs were connected to 3.3v or 5v. The corresponding output was checked for a high (5v or 3.3v). The input of the line being tested was then connected to ground, and the corresponding output checked for a low. The input was again connected to 3.3v or 5v, and the corresponding output checked for a high. Every input and output was verified to work correctly.

I have 100% confidence in the BOBs. If anyone purchases all of these components for $500, and the BOBs don't function properly, I'll refund $100.

Best, Gene
This email address is being protected from spambots. You need JavaScript enabled to view it.

ok, i got it to build.
RHEL9 seems to have some stuff backported from kernel 6.x, so ifdef macros go the wrong path.
For me a quick fix was to just remove the ifdefs, like this:

*** cdev.c.orig 2025-03-02 10:05:18.704523437 +0100
--- cdev.c 2025-03-02 10:06:13.589430791 +0100
***************
*** 227,237 ****
EC_MASTER_DBG(priv->cdev->master, 1, "mmap()\n");

vma->vm_ops = &eccdev_vm_ops;
- #if LINUX_VERSION_CODE >= KERNEL_VERSION(6, 3, 0)
vm_flags_set(vma, VM_DONTDUMP);
- #else
- vma->vm_flags |= VM_DONTDUMP; /* Pages will not be swapped out */
- #endif
vma->vm_private_data = priv;

return 0;
--- 227,233 ----

The same problem was in module.c.

Now the driver builds and loads into the kernel.

OK ping times look OK

Make sure the servo thread period is set for 1ms (1000000 ns)

What actual error do you get from LinuxCNC?

 

did you sort it out? the issue i saw with external controls being tied to the ui was a synchronization problem. the only thing i think that would work would be momentary buttons for each increment. a rotary switch such is on most mpg's could not remain synch's with the ui if changed in the ui.

that may be the latest already, if you run sudo apt update doers it update probe basic and qtpyvcp?

Excellent! do you have a build log somewhere on social media?

You should be able to program a 7I95 bit file (or one you created from source) directly
into the flash chip. Then re-program the user firmware and fallback via mesaflash over Ethernet
to fix the fallback/boot sector if you care about that feature.

A: All I/O pins are inputs unless selected for other use in the driver
(man hostmot2) or the hal file.

B: To program the firmware using mesaflash you would
download the firmware and then:

mesaflash --device 7i95t --addr [card_ip_address] --write 7i95t_5abobd.bin --reload

I would ask in the MesaCT section how to do this using MesaCT.

大家好，我正在尝试从 7i92 原理图构建 mesa 7i95。按照 7i95.ucf 的引脚文件进行构建，这是我的原理图  和我的印刷电路板 (PCB)  ,My problem is that there is no JTAG reserved on my PCB, so I can't use the programmer to write the firmware. Can anyone help me extract the firmware from the 25P16 Flash using a CH341?

Hi,

a. Does these have inputs in the firmware for the 5ABoB on p10, p11, p12, p13, p15?

b. Also please guide as how I can update this new firmware on the 7i95t using Mesa CT.
Your help will be truly be appreciated.

so far it looks like some mild rain. I hope it stays that way.
I have the live view going on my computer at work.
I don't log into my Youtube channel at work. So yes I am watching just not from my channel.

Overall it looks like you aren’t blowing the molten material out correctly, or the odd material type you mentioned is really bubbly when it oxidizes.  You really shouldn’t get that kind of dross on either the part or the sheet.

Two thoughts on things to check:

1.  Ive seen this in testing when the torch to material distance becomes too large.

2.  That material looks too thick for fine cut.  Try the same cut with 45amp nozzle using 45amp material speed settings.  Eventually if it works you'll have to re post to account for the different kerf width.  I was like you thinking that “fine cut” = greater precision.  It’s true but only in thin sheet metal.  For anything else, while there may be cut settings in the hypertherm manual, you should steer clear.  I’ve had better success with 45amp consumables and settings in materials similar to what you show.  The kerf width of the arc in conjunction with the thickness doesn’t allow the molten material any place to go.  And thus it can’t blow it away correctly.

 

Air pressure is the same and so should be the speed. Say I cut out a 1” x 4” rectangle. If I start at the bottom right corner and cut left in the -x direction I will get tons of slag on the part but non on the sheet. Once I cut up in the y and then start cutting right in the +x direction the slag moves from the part and goes to the sheet and the part is slag free. That’s why this is confusing me and quite frustrating.

Got Linuxcnc loaded onto the replacement drive. I just hope setting it up is easier than it was 3-4 years ago. I really struggled the first time I set it up as I am not a Linux guy at all so it was very confusing.