Advanced Search

Hi, to be really honest, this line came from ChatGPT, but indeed, I am still trying to understand where this comes from . Didn't found anything in the docs describing this include thing. What I am trying to do is to pass a variable from a macro (state of output pin) to a subroutine. Since subroutine variable can only be flaoting points, I changed the VALUE in the macro to be 1.0 if if true and 0.0 if false. Now the macro does work, however the subroutine gives the error message that there is a wrong command in the subroutine.... must indeed be the 'include' thing

Getting the ENA signal out to the original Hurco servo relay was problem as they draw 55mA. Solved by using a ULN2003 channel. Note that this needs to be done via a series 3k3 resistor and 1K resistor to ground.
Re the Estop.
I can trip the Estop relay, from the GUI, or pressing the Mechanical button, however, when I use the Mechanical switch, the gui doesn't register that the relay has tripped.
Is it possible to use the fact the estop terminal (OUTPUT0) is no longer conducting as a signal to change the GUI Estop status? If that's not picking myself up by my bootlaces...

Hmm. Seems I cant really do much without having the drives here. But how deal with the rs485 for the spindle?

I see some people using usb adapters, but I have a real serial port as well, can that be used instead?

Well, to get a basic config and axes moving, I would suggest running the pncconf wizard. (though I don't know for sure if that supports the 7C80)

Even if it doesn't you can choose a different board and at least get the required config files set up in the folder structure, even if the details of the board name are not 100% correct.

You might find some useful ideas here; forum.linuxcnc.org/30-cnc-machines/42100...up-questions?start=0
I wrote (most of) a special purpose system without any G-code for a press brake.

GladeVCP and Python is probably the well trodden path, but QT and C++ is certainly possible.

And you will need C for any realtime parts such as custom HAL components.

This suggests that something (like a remap) is calling a bit of G-code with the letter E in it.
Or possibly there is something in your actual G-code file that is making it see an E as a command?

yeah this implementation has been a long time coming, it wasn't a small undertaking and is still a work in progress, but it should really help users get going! pretty jazzed about it!

I would run an apt update to make sure you are on the latest probe basic to ensure your sim config contains the most recent updates

the user parameters require the var file to have the numbered variable listed in the file, this makes them persistent, if they are not in the file they are volatile which will work if entered in the ui for that instance but not be stored. the ui also has a settings storage method and this can become unsynched if the var file is missing the listed parameter numbers. it is an issue we are trying to resolve but as long as everything is in place it works as expected without issue.

the subroutines contain update parameter subs which are responsible for writing the newly ui entered parameters to the var file. so those need to be in place too!

is there enough cushion on the opposite side of the X extrusion to slide everything over enough to have a tool rack on the outside of the left side gantry upright? or maybe consider the cost comparison/complexity to be able to add a longer set of rails and a bolt on extension to make that possible?

Im an electronics technician located in Denmark with an hobby interest in mechanical design, cnc milling and additive manufacturing.

A couple of years ago I bought an cnc router with zero experience in the field. The building and electrical parts where a breeze and the grbl controller that I bought back then was an easy thing to flash with fluidNC and get going. 

Now I'm going into more advanced features and adding an self designed atc system hereby arose the need for a more capable controller. The choice settled on the Mesanet 7c80 due to form factor with the rpi and the number of i/o without the need for an daughterboard.

I have experience with rpi/arduino/esp32 projects and have worked a limited bit with commercial fpga cards before.

I have never worked with Linuxcnc before but settled on this environment and the mesa board due to:
1. active community 
2. Full customization

So the big question is, where do I begin? What would be a good course of action to get going in an orderly manner? 

The hardware:
clossed loop steppers and drivers
XYYZ + AB (possible used to manipulated the ATC later)
inductive sensors on all axis
several solunoidvalves (mist and air)
several relays (pumps and spindle light)
surface probe
tool lenght sensor
several failsafe and e-stops
ballscrews on all axis

The atc system will be an add on later and will not be a part of the initial setup.

The electrical part is going to be an non issue for me I have already planned this from the drawings in the 7c80 manual.

Thanks in advance



 

Hi Atlantis, did you solve the tool change procedure? I a also working on setting up a emco vmc100 and struggeling with the exact same problem

thanks for your advice.
 

Custom kinematics is likely the best way to go about it. I would recommend to use the 'userkins.comp' template as it can be installed using the 'halcompile --install ...' tool:
linuxcnc.org/docs/stable/html/man/man9/userkins.9.html

I can't thank you enough for your effort. This is a real time saver, I've spent hours just to understand what's behind a possible implementation of an atc.

Guess PB is going to be one of the most used GUI because it is cutting all the hardest parts to setup.

The strange thing is I haven't ran an update for quite a long time.
I have been doing a lot of configuration work in HAL and INI files.

I will check with meld, create a backup and perform an update anyway to see if it fixes the problem, thanks!