Advanced Search

tuxcnc wrote:

ESP32 is 3.3V and it is too low for some drivers, but some will works.

Sorry i forgot about this, mainly because i tested several drives and all worked fine.

I'm more interested in the inner workings of the different GUIs, like why I'd choose Qtvcp vs QtPyVcp vs GladeVCP, as the looks/layout can always be changed.

From somebody who's just started to look at LinuxCNC in detail, it just seems to be a variety of options with no clear reason why you'd pick a certain one.

 
Now that I've got my basic setup running, I'm looking at the more detailed setup, and have a few questions.

How are people monitoring that all the EtherCAT devices are still connected?
I've been testing, and if I simply unplug a cable or power them off, no immediate fault is generated. LinuxCNC only finally disables when I try moving an axis due to a following error. Is there some form of pin available that will detect if a device(s) have lost communication?

Is anybody reading the status from drives during operation?
I know I could connect the drive error variable to a suitable HAL pin. but is anybody also reading the error code?

I know that the last two questions are probably as much GUI based, but I'd be grateful to any pointers on how these things can be implemented.

So, I've run into the same problem. 

I run on 15,6" (system see it as 16") touch screen which I've mount vertically, so my resolution i now 1080x1920.
After trying with screen physical size, screen DPI and few other things, nothing worked...
I've changed to 2.9.10 with debian 13 (i had 2.9.3 with debian 12) and for a brief moment it was ok, until i uploaded old configuration for linuxcnc and problem went back again. 

In my case source of the problem is  probe_screen_v2.9  it requires resolution of 1280x1024 and I wasn't able to change it.
There is no fixed dimensions in glade file for whole window, it depends on sizes of single components. So it would be a hassle to change it. 

hi

has any one done a amada turret punch?

i have a amada Vipros587 Queen punch with C axis on punch stations

also is pure hydrulic on its punch unit

the machine its self would be easy, i am wondering if any one has solved the control of the hydrulic ram on the punch stations? for replacing the dedicated PHNC System

yes some custom punch cycles would be needed for slotting and profiling etc 

oh and on mine it has linear resistive measuring devices to track potion and they use this to control the proportional valve also.

this topic is grate so watching this closly to see how you solve this

i also have a nigribosi machine around 1998 eara , before they went full PLC type etc currently the conotrol keeps needing TLC on its many PCB boards due to age and drift , always down to the way it monitors position and control of its rams

in this machine there are a number of proportional valves , i looked at other controls out there but they are mostly aimed at VFD driven pumps and not many proportional valve outputs

mine has two proportional on the pump block
one for Flow and one for pressure , these work together during differant operations during the cycles to keep energy use down etc
also when the machine is first turned on, they use the platen valve block and pump in full flow to heat up the oil faster so no preheaters are needing only the pump is used. 

valve on the screw carriage to control distance and speeds seems to be a standard vale and they must use the pump to control the speed in pump flow. and they seem to do this for afew other things, where only 1 thing works at one time,

one on the molding machine platen is proportional doing distance and speeds for the multi point open and shut speeds and distance for open and close strokes, this would be due to the fact you can do ejection while platten is still opening by seting the 1st ejectoin distance start

also one on the ejection plate to set the distance and speed for ejecting the part from the mold must be a proportional as works during the high flow high presure on the plattern if enabled to eject during open stroke.

looking at it, the same seems to be on the screw for the screw speed control, not sure how they are controlling the back pressure on the screw and screw injection profile settings. 

i had through about using linuxcnc also as alot can be done in hal easy, not that much to address in a molding machine, more how you control its cycle in its little fucntion blocks as such.

mine has a safty relay for the estop buttons , not sure what else they routed through it

for safty guards, they seem to read these in on the control, the ones on the guard door and must work in the corrrect sequence when opening or closing the door or it does alarm out with guard out of sequence, i assume as on this machine you can move the safty switch and open the door extra day light which is good for loading in bigger tools over head

the control also has options for things like core pullers normaly 3/4 can be used
also air ejection is on this machine
also ability to read thermo couples from a mold tool 

also the control also controls the hydrulic tank temp but turning on and off a valve that pushes the oil through the heat exchanger for cooling from the cooling water coming into the machine.

as already pointed out, alot of the machine works on timers and waits for one section to finish before it starts the next, is alot the user can input and change during the machine working cycles. also a good handfull in the machine setup pages that are fixed like time out for screw back and screw injection etc, along with max presure for platten open and close 

they seem to be Bosh or Atos alot for the valves i find in nigri bosi 

lube cycle tends to be done on the number of completed ejection cycles

i do have some wiring diagrams and hydrulic i can share if it would help in understanding , can also share some control screen shots for reff

ESP32 is 3.3V and it is too low for some drivers, but some will works.
Wires are wires, the problem may be with poor quality connectors. Some are good, some can be repaired, some are useless, it depends on which ones you get.
I agree, the wires to W5500 must be as short as possible.

Current may flow, for example, from the controller terminal's power grid, through the controller input to the 0-10V board, from there to the 12V power supply, through the power supply to the homing limit switch, through the limit switch and your body to the housing of the device grounded to the other pole of the power grid. Believe me, there will be voltage and a closed circuit...

Yes, but there is an optocoupler between the KBIC and BoB I'm not sure where the danger is. Assuming that the optocoupler is functioning as it should mains shouldn't even reach the BoB.

tuxcnc wrote:

...the conversation about LinuxCNC should start with github.com/jzolee/HAL2UDP - the cheapest solution worth recommending (ESP32 + W5500 +OptoBOB or CNCshield), unfortunately with limited possibilities.

Correction, no need for OptoBOB nor cncshield, all new-ish china drives have their own optocouplers, so unless doing something out of the ordinary, there is no need for it.
Do not use those "arduino wires" to connect the ESP32 to W5500 though as it will cause a lot of grief, solder wires, short, 10-15cm max.
Here is such combo tested at 40kHz i think
www.youtube.com/shorts/55287Iaa4Y0

Logthor wrote:

I am doing this like I said, but I am still quite confused on how this could pose a shock hazard. It doesn't matter if the e-stop, homing switches, etc. are connected to the spindle control circuit if it is optically isolated between the KBIC and break out board. I just don't see how buying a separate supply and separate PWM to 0-10V analog unit is going to make it any safer.
 

For electric current to flow, two conditions must be met - there must be a potential difference (voltage) and a closed circuit. Until you close the circuit (e.g. by touching the controller and some ground with your body at the same time) you will not be aware that there is dangerous voltage there. Current may flow, for example, from the controller terminal's power grid, through the controller input to the 0-10V board, from there to the 12V power supply, through the power supply to the homing limit switch, through the limit switch and your body to the housing of the device grounded to the other pole of the power grid. Believe me, there will be voltage and a closed circuit...

I am doing this like I said, but I am still quite confused on how this could pose a shock hazard. It doesn't matter if the e-stop, homing switches, etc. are connected to the spindle control circuit if it is optically isolated between the KBIC and break out board. I just don't see how buying a separate supply and separate PWM to 0-10V analog unit is going to make it any safer.

After a bit more digging, I'm guessing the "# create a new component..." stuff is for creating a new component and not for just linking qtpyvcp hal widgets to hal.

Reviewing the terminal output during PB startup, it looks like 'exported hal' is working, or at least not throwing a warning:

 

Not sure what this warning is:

 

Attached the full terminal output during startup, halshow showing no pin being created, as well as a screenshot of the hal led indicator I'm trying to connect.

 

First of all, some users do not need LinuxCNC at all because they perform simple tasks for which GRBL/FluidNC is enough. LinuxCNC is just an unnecessary complication and additional cost for them. Secondly, the conversation about LinuxCNC should start with github.com/jzolee/HAL2UDP - the cheapest solution worth recommending (ESP32 + W5500 +OptoBOB or CNCshield), unfortunately with limited possibilities. Then there is riocore (recently active topic on the Forum). Later, Chinese cards compatible with 7i92 available on Aliexpress. And finally, the original MESA cards, unfortunately expensive and difficult to obtain in some countries, but widely praised. The most expensive and so far quite difficult to configure is Ethercat (I use it and I like it, but I don't recommend it to beginners).

Different GUIs are created to meet the specific needs of some users. There are no overall better or worse ones, they are better or worse for a given operator or a given machine. For example, I have vision problems, so Axis has too small a font, and QtDragon turns me off just by looking at it. But other people use it and praise it, but they don't even want to hear about Gmoccapy, which is a great choice for me...