Advanced Search

That is were i built mesaflash from, however it only nets version 3.4.6 (unless im doing something wrong)

however, this evening i have discovered that you dont actually need to be able to connect to the card with MesaCT in order to build a config. ive had some positive progress with getting one servo&encoder wired in. the encoder shows movement and the servo blips when trying to turn the machine on before it errors out due to following error.

the tricky thing now, is i cant find the specs for these encoders to verify the PPR.

i would still love to know the answers to the original questions ofcourse, as im sure i may need to sort those errors sooner rather than later

Hi community,

Thanks to the help of several members, I’ve been able to upgrade my machine and it’s now working better than ever. So I wanted to give something back.

I mainly use Fusion 360 to create my toolpaths, but I noticed I couldn’t easily use multiple tools within a single G-code file. Fusion360 requires saving each operation as a separate .ngc file. To streamline my workflow, I wrote a small Python script that merges all the generated .ngc files back into one file.

To be clear: I’m still quite inexperienced with CNC (this is just a hobby for me), but I am a software developer—so any feedback or improvements are very welcome! I’m still testing and iterating, but maybe it’s already useful for some of you.

You can find the project here:
github.com/npostma/GSeam/

don't really remember, maybe 1 minute, but a USB blaster for 5USD is worth it

You can build from source by following the instructions here:

github.com/LinuxCNC/mesaflash

As for the Linuxcnc version I doubt whether 2.1 could be built on a recent linux distro due to python issues.

This should work for 2.8 and up, notice the hal command at the end for refreshing the Gremlin (plotter).

Not sure where you got that information from but I don't see an 'axisui.refresh' pin:

 

i did some rework on the mounting for my air cylinders and have been getting stuff gathered and sorted for driving this chuck while i have been working on the clamping needs for soft jaws for this thing. i did some testing to see how good things will center and with out to much effort i looks like things will at least be within .015 off center at the worst 90 degrees from the air cylinders. centering and around .005 off in the line of the two air cylinders. so things look promising so far.

I'm not sure what would realistic since stock tubing is not going to be perfect to begin with but i have one last thing to try to see if i can get things in line better to get as good as i can get and produce repeatable results every time. If i can get within .005 of center all the way around i don't think it's going to get much better than that or at least on a repeatable level.

accurate clamping and centering will open up better options for programming a rotary, so this is my end game. i also think once you add a second chuck that will help quite a bit as well.

Good evening all

I was really holding off on asking for help as i much prefer to figure things out for myself but i'm running up against a few specific struggles and i'm starting to get the feeling that i'm just missing something that perhaps you experienced folk may know about due to experience. 

I have setup a nice pc with Linux Mint 22.1 using the ISO Tommylight provides. the LinuxCNC included in this was 2.1 which seems old and this is however the first detail i might be missing the mark on, in hindsight 2.1 seems to old to be logical so perhaps its a different variant? Regardless, i uninstalled that and installed 2.9.4 which went without a hitch, but did not make anything work any better. 

I then came across MesaCT as pnfconf doesnt support this card. I set the card jumpers as per instructions in MesaCT and i can ping it on 10.10.10.10 but i cannot connect to it.

MesaCT reports that the LinuxCNC version is "version error" - my gut feeling is that the linuxcnc version is newer than the latest update for mesaCT and its just not able to report on it correctly - can anyone confirm if this is preventing operation?

Finally, the detail that i believe is actually stopping MesaCT connecting to the 7i97T - the mesaflash version is reporting (correctly) as 3.4.6, MesaCT notes that for the 7i97T connect, Mesaflash 3.5.3 is required, however i cannot for the life of me find where this is to be obtained, or even any reference to a mesaflash above 3.4.6 other than a few posts on this forum where users mention they are setup with 3.5.x and don't seem to suggest that this was at all difficult. Those posts were all a couple of years ago, has something changed with the version numbering? 

I am not at all new to computers but i dont have a large amount of experience with linux, happy to do the learning but it looks like i need a swift kick in the correct direction! 

Any help greatly appreciated

p.s. i couldnt decide if this should go under "installing" or "general" apologies if i picked wrong. 

Hello Aciera, thanks for the reply.

I haven't had anything to do with the kinematics module yet. I'll stick with the experiment in the HAL for now.
(but ​​that will definitely happen sometime...)

I've been experimenting a bit with "moveoff-external." With a fixed offset value, it looks quite promising.

Now it's about creating a variable from the B-axis value to put it into mv.offset-in-4 (C-axis).

For the calculation, I'll use mult2 with a fixed constant of 1/51

mv.offset-in-4 = mv.pos-3 * (1/51)

I've looked at some values ​​in the HAL show and I'm not quite sure which would be the best:
bpos-cmd, bpos-rel, or mv.pos-3.

I'll play around a bit more.

Best regards,
Kai
 

If standard Modbus works one can wonder why there is a hal componenet for this vfd?
The old Huanyang vfds use something similar to but not quite Modbus so there it is needed.
 

Yeah I'd take what that user says with a grain of salt, unfortunately he can be a little unreliable or completely off the mark.

Try this command to see what is installed

Confirmed is a SW issue.

I replaced the hy_gt_vfd driver with mb2hal, which is a generic modbus HAL component, no HW changes, and it works.

nice....thanks

For configurations with specific daughtercards, the daughtercard 
name is included in the file name and you can use the .pin file
to determine the content and pinout of the firmware, for example
the 7i76eu_7i76x1_pktv2d.pin file shows that the configuration
includes a V2 PktUART ( the TX and RX halves )

Thx.
Just out of curiosity…
Is there an overview what all those firmwares do / are meant for?

Or how could I have found that out myself?

Regards

7i76eu_7i76x1_pktv2d.bin 

Would be the correct firmware

You will also need to update LinuxCNC to the lastest version
sine the hm2_modbus driver is quite new.