Hypersensing questions

So I have my hypersensing circuit wired up, and I have a few questions that I did try to self answer via search, but haven't been too successful.

1. For the 390K resistor, I assume 1/4 watt is fine?
2. In the .pdf that is in the hypersensing thread the wiring example shows the voltage divider jumper on F/1, but the .hal and the .comp both show F/32. Which is correct?
3. In one post, it is suggested to point the .ini file to the hal file Rod attached. In another, it's suggested to copy and paste it to the hal_connections file. In yet another, it's suggested to put it in the <config>.hal. Which is correct? (I am guessing the hal_connections).
4. 2.9 which I am running, comes with the ohmic.comp. But I haven't seen anywhere that says I need to modify this file to match my THCAD board's frequency calibrations. Do I need to modify this file, or is the numbers in there just an example of what the .comp file is doing, and it pulls this information from the .hal? Obviously I need to change these in the .hal, I just wasn't sure what else was going on/needed changed.
5. If someone had 2.8, where would they place the ohmic.comp?
6. In the ohmic.comp (again not sure if this is an example that is commented out or I need to change it) the encoder is pointed to the A encoder, and I believe it should be pointed to the B encoder, since most will use A for THCAD. (hm2_7i76e.0.encoder.00.velocity) Plus the PDF says to hook to encoder B.
7. In the .hal file, it uses "hm2_7i76e.0.encoder.02.velocity" which I believe would be the IDX pins, and not Encoder B... wouldn't Encoder B be "hm2_7i76e.0.encoder.01.velocity"?
8. One last point of potential confusion... the .comp data (probably example) and the .hal input THCAD data don't match (different frequencies).

I find that a lot of the stuff on the forums assumes a certain level of Linux/Linuxcnc proficiency, and new users dont necessarily have that, and may be afraid to ask, or easily frustrated to figure it out. So I figured the clearer this all can be, the more everyone benefits.

I think that's all for now thanks for the help! Really looking forward to trying this out.

Good deal, thank you both, this is very helpful!

I will be doing the rest of this in the next few days, I may have other questions.

Actually, I do have one. Somewhere I read that Plasmac can be configured to fall back on the float switch if the ohmic doesnt trigger for some reason. Is that done by default, or do I need to do something to my config to get this to happen?

You just need to have them both set up and working properly.
Floating switch means floating head with two sets of rails, one very short.

rodw wrote:

snowgoer540 wrote:

SomewPlasmac here I read that Plasmac can be configured to fall back on the float switch if the ohmic doesnt trigger for some reason. Is that done by default, or do I need to do something to my config to get this to happen?

As Tommy said this is done for you by default. With pending changes to the Plasmac probing algorithm to speed up probing and to reduce the number of probing errors, the float switch may become a requirement so that there is room for the torch to slow to a stop when the ohmic probe is triggered without breaking anything (Or a float switch is required to implement the new probing algorithm).

Please report back when you are up and running so the feedback can be incorporated into the component. Once we get this proven with some feedback, we should be able to get it deployed to V 2.8 as well.

Good to know. My float switch throw is very short, probably .030-.040... hopefully that doesn’t become an issue.

I enjoy testing things and finding bugs so if there is anything specific you want me to focus on, please let me know.

you can control that with your probing speed. Faster = more travel.

Not quite right, Probe Speed only comes into play after Probe Height is reached. It uses Setup Speed from the config panel to get to Probe Height.

From the yet to be completed docs:
The following formula can be used to calculate your machines approximate overrun.
0.5 × a × (v ÷ a)²
a = acceleration in units/sec²
v = velocity in units/sec
So with Z axis acceleration of 2000mm/s² and Z axis velocity of 33.33mm/s we would have an overrun of 0.278mm.
This is roughly 78in/s² and 1.3in/s for an overrun of 0.01"

acceleration is obtained from MAXIMUM_ACCELERATION from the joint associated with your Z axis in the .ini file
velocity is Setup Speed in the Config Panel divided by 60

In addition to changing the "num_encoders=" to 2 in the top of the main hal file, another critical piece of information is that you need the other setp values that are similar to the THC:

setp hm2_5i25.0.encoder.01.scale -1
setp hm2_5i25.0.encoder.01.counter-mode 1

I am honestly not sure if you need the filter or not (setp hm2_5i25.0.encoder.01.filter 1)? I've always been a little fuzzy as to what this did?

I think I read somewhere the filter was ONLY for the 7i96... but I could be wrong. Note that I DO NOT have an Ethernet setup, I am using a 6i25 with a 7i76 with Peter's custom Plasma firmware...