Advanced Search

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...

Now that I've solved the issues with getting EtherCAT drives to work, I'm looking at GUI options, however I'm wondering if there's any kind of guide as to pros/cons of each GUI option?

First machine I'd like to try this on is a plasma table, but potentially also re-retrofitting a mill, and I'd like some kind of commonality between them, but I'm kind of stuck in not knowing what to go for.
I know there's QtPlasmaC and QtDragon, but also the MonoKrom option.

ok, i think i see the problem but have to check how i fix it, i never used function code 3 for bit's

Unless there is something fundamental that i am missing, you can not turn the saw while cutting, never ever, so "motion.interp.heading" can not be used, so why Rod?

That is up to the users to find a use for it. The motion.interp.heading will be the exact direction of your saw blade is pointing as commanded by the gcode interpreter updated in real time. It may not be useful with a saw. But in the case of a tangential knife, it could be coupled to the A axis rotary angle so the knife always remained tangential to the direction of travel on G1, G2,G3 moves. I thought the machine would use a component to monitor the heading and do things like stop to lift and reposition the knife when transitioning from G1 to G2/G3 if the change in direction exceeded a safe limit. In your case that would be 0 degrees.

Hi,I am currently configuring a Modbus RTU I/O expansion board with RioCore / RioFlow, and I ran into two issues:1. Unable to read digital inputs (N4D3E16 board)

• Board model: N4D3E16 (16 Digital Inputs / 16 Digital Outputs over RS485 Modbus RTU).
• Current status: Controlling all 16 digital outputs works without any issues. However, I am unable to read the status of the 16 digital inputs.
• I am following the register addressing and function codes described in the board's documentation (which I have attached). Could you check if there is an issue with how RioCore handles the Modbus function code (e.g., FC02 vs FC03 / register offset) for this mapping?
  
  2. RioFlow device renaming bug in LinuxCNC
  • When I assign a custom name to the devices in the RioFlow interface, LinuxCNC throws an error on startup and fails to load.
  • If I leave the device names blank (default), LinuxCNC starts and runs properly.

I have attached the JSON configuration file and the board's documentation for reference.Thanks in advance for looking into this!

Thank you Tommylight, Timo and Rodw for the replies and ideas.I live in Algeria, so buying a commercial stone CNC is very expensive for me. That's why I'm trying to build one myself.I've built several plasma CNCs before, but I always used PNCconf. I don't really know HAL/INI manually, so I'm starting with the 4-axis configuration generated by PNCconf.For now, my goal is actually simple: cut slabs accurately. For an inside corner, such as an L-shaped countertop, I'm happy for the saw to stop before it overcuts the corner. I can finish that part with another tool later.The machine will cut from the top/front side of the slab.For the A-axis, my idea is simply:raise Z → rotate A to the next cut direction → lower Z → cut → raise Z → repeat.I understand that A should not rotate while the blade is in the material, and I will use an interlock for that.Rodw, your mention of . Could you explain how I could implement it starting from a normal PNCconf-generated 4-axis HAL/INI configuration? 

For now, I want to make the machine as simple as possible and just get it operational. Once I have it working and cutting slabs reliably, I can improve it and make it more efficient step by step.Thanks again everyone. I'm trying to keep the first version simple and build from there.