Advanced Search

i have LINUXCNC - 2.9.4 the last version but where can i find man hm2_modbus, can you show me how to use hm2_modbus, mesambccc, give me examples please

hi there...

This tool is basically my external memory device... I saved my experiences and knowledge to them because my brain has limits too ... Maybe you will try the TC3.. it is very powerfull enviroment with tons of usefull stuff 

Have a try and let me know!

see U

hm2_modbus is an alternate modbus interface to Mesa FPGA cards with 
PKTUART firmware. It supports additional features such as multiple devices
per interface, one time initialization code etc etc.

You need to have the latest LinuxCNC to have hm2_modbus

if

man hm2_modbus

Gives you a manual page, you have a late enough version of LinuxCNC
to use hm2_modbus.

hm2_modbus will work with your existing firmware.

 

FYI The lathe sold to a Company in North Carolina. We had it on our Auction site and it sold for $3K. Just another huge loss for our company. But when you are going belly-up it's just the way it is.

I dont understand what is hm2_modbus new firmware ?
How to use it, what i should do ?
in mesa modbus i just find this
PktUART
MB2HAL
vfdmod
Classic Ladder
i want to use Classic ladder but i dont know how

nothing wrong with race to the bottom timo. its like running doom on everything. we are having fun.

I think the real question is, why arent i mining crypto when my machine has downtime? make the mesa fallback to a crypot miner

hmm. gonna need to add a something about bootloader to the board specific docs pages.

Did you check index enable?

To test whether the index hardware is working (assuming you can move the axis past
an index mark), you would:

With LinuxCNC running,  use halshow to watch the signal b-index-enable
and then with either halshow or halcmd, set b-index-enable true"

halcmd sets b-index-enable true

halshow should now show b-index-enable true

now, if you move the axis past an index mark, b-index-enable should go false.

This is how you test for correct index operation.
 

timo wrote:

Driver issues (Linux) not available software (Linux), .....

I really have to disagree with this, hard, it was true 25 years ago, now those are valid for windoze, not for Linux.
I have at any given time at least 10 different PC's and laptops in use, i change them very often, never have driver issues, ever, from quite old to new, like B650/R7 new.
And as long as we have OBS-Studio and Blender, windows should feel insufficient, not Linux as those as primarily made for Linux. And some DAW's and ....
You are aware that there is nothing with OBS-Studio functionality even in the 5 figure range, right? And is absolutely free...
And Blender is a monster, in all regards, used by huge movie studios but never ever mentioned in the credits.

The original modbus driver only supports one device per interface
(its basically for VFD spindles or just single devices)

For multiple devices, use hm2_modbus

man hm2_modbus

man mesambccc
 

Hi, several times I have borked the Rpi5 install for various reasons.  So, decided to make a script to backup the entire /boot folder.  Perhaps this will be useful.  Have tested the backup and it works, have not tried the restore yet (and hesitant to.)  But just having a backup alone might be worth it's weight in gold.  P.S. it looks like there is a /boot partition and a / partition, however the / partition also has a /boot folder... so unsure if a restore would clobber anything.

boot-backup:
boot-diff:
boot-restore:

You are right.
I read out eeprom from a slave I know has SDOs.
But nothing with the SDO names in the eeprom bin file.
So, it is possible the siitools -m could produce a good eeprom.
I'll test later this evening, I have a device I can experiment with.

I deleted the 3 lines without success Z undetectable.
My axis turns at slow speed during the homing phase but never stops.
Should it stop when it finds the puls index?

compared to mesa which uses memory map with peripherals mapped to addresses in the memory and need cpu parsing to read write addresses. but this allows dynamic configuration of the driver.

I should note that a CPU is not required with HostMot2 and no interface CPU is  used in PCI, SPI or EPP
interfaced configurations. Interface CPUs are only used with  Ethernet, USB, and serial interfaced
configurations to support the more complex wire protocol.

 

Thanks for the response and my apologies for delay and update - retired life got super busy for a couple weeks... I'm not sure I explained the whole episode clearly - I'll try again.

1) LinuxCNC was reinstalled on the same hardware but with an SSD instead of spinning disk.
2) StepConf was invoked to create new .INI and .HAL files for this new installation - there was no attempt to 'configure' anything using StepConf because I planned on copying over the .INI and .HAL files from my previous working install (spinning disk)
3) For grins and giggles - I attempted to load and run LinuxCNC before overwriting .INI and .HAL - of course it didn't work
4) I overwrote the initial .INI and .HAL files with my copies from the working installation (spinning disk)
5) Initial loading and running of LinuxCNC worked fine
6) Thinking I again had a functional system, my mind went into autopilot and my fingers took over - I wanted to move the router to the center of the workspace an pressed the SHIFT-RT Arrow for a rapid move 'X' and... it jumped a bit and stopped
7) Exactly the same with SHIFT-LT Arrow, SHIFT-UP Arrow, SHIFT-DN Arrow, SHIFT-PgUp and SHIFT-PgDn.

I have not yet run a job to see if it works - I doubt it because any rapid moves would cause a problem. I've done some reading on steppers, timing and BASE_PERIOD and I'm trying to find the timing charts for my steppers. I'm thinking that since LinuxCNC uses software step generation, the new SSD may be just too quick? Although - the configured BASE_PERIOD should be independent of the any HD speed.

My other thought is - my latency test resulted in > 70,000 nS Jitter in the Servo Thread and almost 56,000 nS Jitter in the Base Thread. With Steppers - I'm not sure I'm concerned about the Servo Thread numbers, but when using StepConf, the maximum entry allowed allowed for Base Thread jitter is 50,000. While the instructions for the Latency Test say 'abuse' the system when testing... when running a job - I don't much touch the computer for anything significant - certainly no web surfing or multi-tasking other apps.

Not sure any of that update helps you all help me - I'm reading LinuxCNC forums, documentation and Wiki as well as trying to find timing diagrams or tables for my steppers. Anything anyone can suggest would be really helpful... possibly reduce the acceleration?

EDIT: I should have included some hardware specs...
Dell Optiplex 7020
I3-4150 @ 3.5GHz
8G RAM
Samsung 256G SSD