USC pico systems with Qtplasmac

More
2 years 7 months ago #296237 by edgemir
Is possible to get work GUI Qtplasmac with an USC board from Pico Systems. If is it possible, someone can explain please?

Please Log in or Create an account to join the conversation.

More
2 years 7 months ago #296242 by PCW
Replied by PCW on topic USC pico systems with Qtplasmac
I would think that QtPlasmac is fairly independent of
interface hardware.
 

Please Log in or Create an account to join the conversation.

More
2 years 7 months ago #296260 by jmelson
The plasma torch needs to send some information to the CNC control about the arc voltage, so the torch height controller can move the torch up/down. This may take two digital inputs and two digital outputs, or could be controlled as an axis (Z).
Jon
The following user(s) said Thank You: edgemir

Please Log in or Create an account to join the conversation.

More
2 years 7 months ago #296280 by phillc54
If you got the plasma table working as a three axis machine using the AXIS GUI then we could probably create a script to convert the config to QtPlasmaC. The conversion could certainly be done manually.
The following user(s) said Thank You: edgemir

Please Log in or Create an account to join the conversation.

More
2 years 7 months ago #296284 by edgemir
Thanks for your reply. I've been working with the sample configuration that comes with linuxcnc 2.9.2. I have already managed to get the motors to work without using encoders, I am trying with the times and speeds that come by default. I'm using Gecko G201X Drivers and there seems to be no loss of steps or excessive vibration. I am confused by the fact that there are no pins where the axes are assigned to each step/dir generator for each axis, I understand that the pulses are generated by the hardware and not the PC, but if my configuration uses two motors for the "X" axis, I don't know how to tell it to the USC card. And in the same way I don't know how to indicate which axis I am going to use to control Z in Qtplasmac. I thank you in advance for the help

Please Log in or Create an account to join the conversation.

More
2 years 7 months ago #296322 by jmelson
The simplest way to have a gantry axis is to just connect the step and dir outputs to TWO motor drivers. If you really want to have separate control for each motor, such as to have the homing sequence square up the gantry, then it gets more complicated. In the file univstep_motion.hal the position counters and step generators are linked to hal pins, and then in univstep_servo.hal they are linked to the "joints" in LinuxCNC. Actually, if you plant to use encoders, it is best to start with the set of files under USC_encod, which has separate ini file settings for the encoder counter and step generator scale factors.
Jon
The following user(s) said Thank You: edgemir

Please Log in or Create an account to join the conversation.

Moderators: PCW, jmelson
Time to create page: 0.336 seconds
Powered by Kunena Forum