Pathpilot plasma
20 Dec 2020 12:42 #192525
by snowgoer540
There's no other mention of another encoder in the hal file, save for the firmware pinout they are nice enough to add in:
At any rate, I don't see any secondary power supply for the ohmic effort, nor is a second encoder velocity dealt with at all. That seems...odd?
Replied by snowgoer540 on topic Pathpilot plasma
That's why I posted itIf you trace the wire marked CAP back, that refers to the Ohmic CAP on the torch and the probe signal connects to the encoder pins that the Mesa Plasma bit file would call "encoder 2". So they can use the same board for other machines.
There's no other mention of another encoder in the hal file, save for the firmware pinout they are nice enough to add in:
# IOPortTag & x"00" & QCountTag & QCountIdxPin, -- I/O 26, spindle encoder Z / ohmic J9-6 (Z+), J9-7 (Z-)It could also be that we quietly benefited from development work being done for them...I think they've quietly benefited from the open source development and put together a good package.
At any rate, I don't see any secondary power supply for the ohmic effort, nor is a second encoder velocity dealt with at all. That seems...odd?
Please Log in or Create an account to join the conversation.
20 Dec 2020 13:23 - 20 Dec 2020 13:24 #192533
by rodw
I don't think development from Tormach around Plasma has fed back to Linuxcnc. Heck it took years (at least 5) to get State tags developed for them into the core code. But I do wonder if the experiments I did for Mesa that led to Hypersensing was not an experiment to prove concepts that fed into the Tormach machine.
You forget that Tormach are using a custom FGPA and therefore use custom firmware so what we do in HAL for probing, they could do in firmware. I did not follow the extra input on the high voltage side back to a source or look through the rest of their schematic but I assumed that there was inputs for a common ground (workclamp), a torch and a probing connection.
I do see similarities with the material interface I suggested here forum.linuxcnc.org/plasma-laser/35449-an...nent?start=10#119922 back in 2018
Replied by rodw on topic Pathpilot plasma
That's why I posted itIf you trace the wire marked CAP back, that refers to the Ohmic CAP on the torch and the probe signal connects to the encoder pins that the Mesa Plasma bit file would call "encoder 2". So they can use the same board for other machines.
There's no other mention of another encoder in the hal file, save for the firmware pinout they are nice enough to add in:# IOPortTag & x"00" & QCountTag & QCountIdxPin, -- I/O 26, spindle encoder Z / ohmic J9-6 (Z+), J9-7 (Z-)It could also be that we quietly benefited from development work being done for them...I think they've quietly benefited from the open source development and put together a good package.
At any rate, I don't see any secondary power supply for the ohmic effort, nor is a second encoder velocity dealt with at all. That seems...odd?
I don't think development from Tormach around Plasma has fed back to Linuxcnc. Heck it took years (at least 5) to get State tags developed for them into the core code. But I do wonder if the experiments I did for Mesa that led to Hypersensing was not an experiment to prove concepts that fed into the Tormach machine.
You forget that Tormach are using a custom FGPA and therefore use custom firmware so what we do in HAL for probing, they could do in firmware. I did not follow the extra input on the high voltage side back to a source or look through the rest of their schematic but I assumed that there was inputs for a common ground (workclamp), a torch and a probing connection.
I do see similarities with the material interface I suggested here forum.linuxcnc.org/plasma-laser/35449-an...nent?start=10#119922 back in 2018
Please Log in or Create an account to join the conversation.
Moderators: cncbasher
Time to create page: 0.090 seconds