Need help setting up HAL files for MESA THCAD10

More
10 Apr 2021 21:38 #205569 by PCW
No, arc voltage is read from the encoder velocity pin:

net plasmac:arc-voltage-in <= encoder.0.velocity

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

More
10 Apr 2021 22:09 #205576 by CCharles
So how do I tell Linuxcnc that the THCAD10 is hardwired to a specific parallel port pin?

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

More
10 Apr 2021 22:14 #205580 by snowgoer540

So how do I tell Linuxcnc that the THCAD10 is hardwired to a specific parallel port pin?


You did that with this line in your atomicplasma.hal file:
net arc-voltage-raw parport.1.pin-15-in encoder.0.phase-A

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

More
10 Apr 2021 22:19 #205581 by andypugh

2. You have a strange character (wrong dash) in your setp command:
...
This can happen if you use something other than a text editor


It can also happen if you copy from the HTML docs.

I _think_ we have that fixed now. it was one of those "complicated systems-engineering" issues.

github.com/LinuxCNC/linuxcnc/issues/1093

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

More
10 Apr 2021 22:40 #205584 by CCharles
Ok, gotchya.

So I did the "dash" fix in the encoder lines and it solved that error. I am still getting 0 volts. What should I specifically be looking at in the HAL configuration to see whats working?

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

More
10 Apr 2021 22:46 - 10 Apr 2021 22:47 #205585 by snowgoer540
Does your hal file look like this:

loadrt encoder num_chan=1
setp encoder.0.counter-mode 1
setp encoder.0.position-scale -1
addf encoder.update-counters base-thread
addf encoder.capture-position servo-thread
net arc-voltage-raw parport.1.pin-15-in encoder.0.phase-A

net plasmac:arc-voltage-in <= encoder.0.velocity
net plasmac:arc-voltage-in =>  plasmac.arc-voltage-in

Alternatively there has been a lot of back and forth, you could post your hal file again.

Also, have you done anything to set up the scale and offset in the config tab? If not, there is an online calculator linked in the manual (here: jscalc.io/calc/NTr5QDX6WgMThBVb) to help you figure it out. I think without that set up correctly, you should still see something. Does halshow show any velocity on the encoder? Even at 0v input the encoder should have velocity.
Last edit: 10 Apr 2021 22:47 by snowgoer540.

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

More
10 Apr 2021 22:56 #205587 by snowgoer540

2. You have a strange character (wrong dash) in your setp command:
...
This can happen if you use something other than a text editor


It can also happen if you copy from the HTML docs.

I _think_ we have that fixed now. it was one of those "complicated systems-engineering" issues.

github.com/LinuxCNC/linuxcnc/issues/1093


It was in the plasmac docs that way. I pushed a commit to fix it. Two less erroneous dashes :)

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

More
10 Apr 2021 23:29 #205589 by CCharles
I am now seeing a voltage.

I checked my file to what you typed and I still had this line commented out:
net plasmac:arc-voltage-in => plasmac.arc-voltage-in

I had commented it out previously trying to clear a previous error.

I also did set the scale and offset in the config tab using that calculator.

Now that I am seeing something. What should the actual displayed voltage on the plasmac screen be showing for the volts both when not firing and during a normal cut.

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

More
10 Apr 2021 23:39 #205590 by snowgoer540
Should be ≈0v when not cutting.
Cutting depends on your plasma cutter, distance from the workpiece, etc. etc.

To verify it, the easiest thing to do is attach a DC power supply and measure it with a multimeter. Multimeter meeting should match what you see on the screen.

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

More
11 Apr 2021 06:54 #205603 by Joco

Its the recommended program that automatically pops up when using Fusion360 for CAM post processing.


Honestly I would dump Brackets. It’s no longer being supported/developed. Adobe is stopping support in September 2021.

Visual Studio Code is the recommended replacement. I use it on Mac, Linux and Window. In fairness to Microsoft it’s a pretty slick product that is free.

Cheers - J.

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

Moderators: phillc54
Time to create page: 0.095 seconds
Powered by Kunena Forum