Advanced Search

No expert by any means, but I got it to work so here are some snippets from that

in custom_sinusM.hal

In sinusM_spindle.ini
 

The above communication works with the vfd. But hal code is probably mixing Hz and rpms so it won't necessarily work for that reason.

Mesa 7c81 over w5500 - Ethernet on RPI4 with qtdragon_hd (3.3Khz loop)

www.youtube.com/shorts/agf3f0MJxv4

Thanks for reply. I just tried it, and the NativeCam tab remains completely empty.
 

works for me:
www.youtube.com/shorts/Tp3savo-MGs

Oh good, sorry was busy till now (1:39AM here).

I think I know what you may be trying to achieve.

If you have a look at the sample as shown in the screenshot, yes it is a pyvcp panel, it should give you the logic require if using your own panel or physical button.
 

Many thanks! I am away today but will give it a try tomorrow and report back. I might also try making an even simpler test machine configuration with only xy coordinates, trivkins, drive by just one 2CS3E-D507 dual-stepper drive, This should hopefully be easier to debug due to having less confounding variables

So sorry, I miss read the documentation, it says that the keyboard arrow keys are DISabled by default and to enable them just check the box. Where is the box? I don't see one on the screen, the settings page or anywhere else that enables the arrow keys. Can someone shed some light on where or how to enable the arrow keys?

Kind regards,

I suppose you are using German as interface language.
Have you tried to use English?

Got it.. Homeing without errors, coordinate system looks correct orientation, pull off is good.
I'm happy.... now... to get all the relays and stuff going to coolant, and toolheight

Hi guys and gals. I have been spending hours and hours trying to get a H-100 inverter to talk to linux cnc. The documentation is just foggy enough that I am at a loss. I can connect the spindle(0) bits to the MB2hal transaction names but apparently I'm not using the correct addresses and int's / float's. And the limited instructions don't give me enough crayons. I have defined a pin called mb2hal.readhldreg.start but do not know how to tie it to the correct register. 

All I see is mb2hal.m.n.float or int or bit. I do not know what m or n is.

This is rather embarrassing as I spent a career in plc's and programming.

If someone could give me some examples, it would be greatly appreciated.

Thank you, David

After a few days trying to get UART to work on my Pi 5 I came to realize it was my TTL/RS485 board that was faulty.  I bought a USB RS422/485 adapter with a terminal block and was able to connect right away to my VFD.My next challenge was using mbpoll to scan the registers, after hours of errors I recall reading in a forum somewhere that there is a limit to  how many responses my VFD can provide at one time.  After testing, I confirmed on mine the limit is 4.This command structure worked for me after reading the mbpoll help file.  This is the command structure that worked for me in case someone has the same VFD and is trying to find out what the settings are without going into the front panel every time:

On my system I have it set to RTU, 38400 baud rate and 8E1:

mbpoll -m rtu -a 1 -b 38400 -d 8 -P even -s 1 -r 160 -c 4 /dev/ttyUSB0

Where:
-r is the register number you are trying to scan.  From 1-199 on my VFD
-c is the number of registers in total to scan.  On my VFD the range is 1-4.  Outside of that range is fails.  There is an offset that you'll need to match up.  For instance, scanning  -r 160 -c 4 returns the values for  F163-F166 on my VFD

I've attached a txt file that contains the script that I  had ChatGPT help me with to document all of my register settings.  The script iterates through every register and cross-maps it to the name of the register.  The output is a file named vfd_register_scan.csv.  It is output in the same folder you run the shell script from I manually entered the Register name from the manual.  Here is a copy of the manual:

images.thdstatic.com/catalog/pdfImages/b...a62-3f425c50eff9.pdf

The hal file text showed 2.9 master, not a standard release.

ISSUE RESOLVED


Problem: unknown, could not locate source of the error

Solution: Updated to 2.9.4

lesson learned, dont forget to try the simple stuff