Advanced Search

Quick Update! I have found a 12V Power supply in my control unit which created a lot of RS 485 connection issues. I have Tested it briefly with a new power supply and the connection seems to be stable. Further testing ongoing. If it's stable I am planning to integrate more features to the classic Ladder Version as soon as time allows.

Hi all

My retrofit control box is starting to take shape. I use a 7i96s + 7i85 (+7i84D smart serial) card. I would like to use the Mesa modbus  on the 7i96s' smart serial port for Modbus (to control my VFD).

Is there a firmware for that available or can someone compile one for me?

Do you think standard mesa modbus works with Huanyang VFD (since these VFDs don't use proper Modbus)? In the comp file I can only define the registers but not the whole data stream to be sent and received form the vfd.

Cheers,
David

but may be I got one dependency wrong as axis is complaining that there is a TCL error in async code:

Bad menu entry index "G-code properties..."

Looks like something related to a recent commit:
github.com/LinuxCNC/linuxcnc/issues/3065

[edit]
Actually there is a typo in that commit. Line 1786 in 'share/axis/tcl/axis.tcl' is missing an underscore before 'G-code':
ISSCHOULD BE

Yes qtdragon can embed panels in specific positons without modifying the main screen.
I would recommend building the panels in Qtvcp though.

Some of the qtdragon Sims have embedded panels as demonstration.. usually vismach graphics.

I have bought 8 of these limit switches uk.rs-online.com/web/p/limit-switches/7768560 to use with my LinuxCNC machine. I was wondering how I wire them to a MESA 7i96s. The machine has 2 motors running on the x axis, 1 on the y axis and 1 on the z axis. Am I able to get away with just using 4 switches in total that will work for homing and as limit switches. Or should I use all 8 and have separate homing and limit switches. I assume that the switches get wired to the input pins on the mesa card. However, I don't see enough ground connections for them. Shoud I connect the common pin (the one besides the inputs) to a breadboard and then wire all the commons on the limit switch to it through that, while connecting the other pins of the limit switch to the respective input pins?Thanks

Mecanix wrote:

Only source code I've had to change was for the board family to be recognized as a its high-speed C7/i6 type.

/riocore/riocore/boards/MecanixDev/board.json
[-] "family": "GW1N-9C",
[+] "family": "GW1N-9C7",

/riocore/riocore/generator/toolchains/gowin/toolchain.py
Line 103:
[+]  if family == "GW1N-9C7":
[+]  prj_data.append(f' <Device name="{family_gowin}" pn="{ftype}">gw1nr9c-017</Device>')

That was the reason my PIN03, PIN13, PIN 15 (high speed bank) was not working. The Gowin was always compiling for a C6/I5 fpga type
But allpins works now!!

fixed in the dev branch

The first post has been updated to include images for 2.9.3.
The Pi 5 is tested and working.
Any feedback about the Pi4 would be appreciated

updated for Linuxcnc 2.9.3 
Newer kernel 6.6.44
Better screen support for the Pi5
Now includes ethercat repos. Following the sticky in th eethercat section to install/

Pi 5 Image  drive.google.com/file/d/1iwQpbMoNdI6wnv7...MyZ/view?usp=sharing
Pi4 Image  drive.google.com/file/d/1Fg2CPTezUyrRFrO...ytT/view?usp=sharing  
 

You have it set as IN mode, so only pins 1, 14, 16, 17 are outputs, and those can drive very low currents, but if using a BOB that should be OK.

Image for Pi 4b now is linked in the previous post.

Not near a PC, but do not chose shared switches, that means shared between axis/joints, choose ... i can not recal what exactly, but it has a lot of choices so choose min or max limit with home for the respective axis/joint, or both min/max and home, if the switches are set up for that.

We are doing a project by spending a lot of time, writing macros, making a plc program. ethercat.xml file,hal files, how can we protect them from our competitors.

Hi,

I am considering changing from ProbeBasic to QtDragon.
While setting up my newest machine I started with ProbeBasic but I needed to update vom LinuxCNC 2.8 to 2.9 t get some new features.
I usually modify modify my VCP quite a bit to fit my machines. But with ProbeBasic I always ran into trouble to bring this changes to a newer version. 
So here are my questions:
I can develop my one tab in QT Designer in embed it into QT Dragon without touching the main ui file, so when there is an update I don't lose my work? 
Are the Hal Widgets includes in QT Designer?
And not for my current machine, but maybe I swap my lathe later. Are the lathe Macros already implemented somehow? or easy to integrate?

Are there some best practices?
I Usually use the custom parts for monitoring the machines additional functions, like lube, spindle gears, hydraulic chuks, Column control and status IO's

Thanks Patrick
 

Apologies for the delay here. I was putting this off in preference to other Linuxcnc projects but its time has come

Pi 5 Image drive.google.com/file/d/1iwQpbMoNdI6wnv7...MyZ/view?usp=sharing
Pi4 Image drive.google.com/file/d/1Fg2CPTezUyrRFrO...ytT/view?usp=sharing 

Kernel 6.6.4 as per the raspberry pi's kernel git
Tested as working by Joco who bought a pi5 yesterday for the occasion!
Monitor support now fixed. He was using a 34" 3440 x 1440 monitor 

Ethercat apt repos now included
QTPYVCP repos a work in progress with the QTPYVCP team now VTK is in the Debian Repos.

There are no added programs, What was suggested was a bit out of left field as none of it was included in our AMD64 build.
Please read the downloads page on how to configure wifi, timezones and locales

 

Solved: really this time!

The SII eeprom image created by siitool based on the manufacturers ESI xml file did not configure some PDI bits, such as enable sync0, which is important for the open source ethercat master. I had to graft some bytes of an older image onto siitools output and rectify the crc checksum. With the attached files I am confident one can integrate Metronix ARS2000 series and some Festo CMMP series servo drives into a linux-run ethercat network.