Advanced Search

thanks jt, that was making me go bonkers trying track that one down. found that in one of my other machines configs and it worked!

as for the pwm voltages, i just got through checking everything and i shouldn’t have any load on the pwm at all. the 7i96 is powered with a dedicated 5v 0.55a psu. i adjusted the pot to 5.42v(i dare not go any more) and i get 5.31v between +5 and gnd and at 24k rpm which is max, i get same between gnd and pwm- when i have the cable to the vfd box disconnected. when i connect the cable it drops to 4.86v. is the converter actually pulling a load?  i can get close to 10v if i boost the input voltage to 14v which is within the range of the board, but is that just a hack or will that work?  or is the psu for the mesa board under powered? i saw that in a post that 250ma was enough without any loads. 

     

scotta wrote:

I'd always recommend calculating the joint SCALE based on the hardware. ie steps per revolution of the stepper motor and then the leadscrew pitch etc. If the actual movement achieved is not correct I'd be suspicious of lost steps, especially if micro stepping.

the seller does not give me any documentation. The only things I have are:
Driver

Stepper: Step angle1.8∘±5%

in the TXT file i have set: 

Frame:
SFU2005 and SFU1605 ball screws Repetitive positioning accuracy: 0.05mm

I've learned C for a semester in university, didn't get it at all. It was so not nice to me.

I do program Arduinoes these days, because the other colleagues don't want to, but isn't that C++? Any way I hate it too

When I need C I use Rust instead, it's a pain too but at least I can usually figure out where I made a mistake. Which is usually forgetting the ';'

I am so confused. the setup does still works after I deleted userkins.c, so the problem must have come from the old userkins.so. According to our git history, userkins.comp never changed, and we did run halcompile when we set up the project, so I don't see why userkins.so changed. Not important, maybe someone accidentally copied an older version from somewhere.

As for the other issues with userkins, I don't know, this is how I received the configuration. I'm slowly trying to figure things out.
 

Electrical Cabinet makeover. 




 

Because you can edit a nc code file directly in Flex I'm working on a search function so you can search the nc code and change things without loading an external editor.



JT

Ouch. I swear I knew that before. Thanks a lot for your reply.

For anyone else that stumbles on this, here is what I added to my personal operations manual:

Q: Ohmic sensing is triggered early
A: This is most often caused by slag or water getting into the shield. 

With the torch shield away from anything conductive, tap the ohmic test button. If the Ohmic light comes on then the ohmic sense circuit is shorted. If you are doing test cuts on scrap, tap the Torch Pulse button to blow out any water in the shield. If that doesn't work, turn off plasma cutter and blow the tip with compressed air. If this does not work, remove shield and clean out any debris. Look for slag that is stuck to the electrode and/or shield cup. 

In the case of slag, consider increasing pierce height as this almost always happens during pierce. In the case of water, add G0 to your program to rapidly move the torch away from water being sprayed by the a torch during postflow.

Thank you for your responses.
I see now how to call another subrutine. If I'm in a running subroutine and stop it, do I have to end it (END SUB) before I call the new subrutine?

I meant "work offset".

If I am undestanding this L20 P0 would change the axis for all subroutines relative to the machine coordinates and not change the WCS offsets for each location i.e. G54...5,6,7. Is this the same as using the Axis Screen offset for P0?

Essintially the program ran the first opertion to all 4 locaions then lifted up and stopped. I want to be able to move it back to the first location and change the tool and set the Z work offset for the nest operation.

Many thanks

Raw counts will be set to 0 when LinuxCNC starts so its still
just a relative count number.

What is the spacing between index marks on your scale?

You have

setp hm2_[MESA](BOARD).0.encoder.00.filter 0

(on all axis) You might try:

setp hm2_[MESA](BOARD).0.encoder.00.filter 1

In case it's a noise issue.

Yeah, sorry, I copied them from a 7I96S halshow and forgot to delete the "s"

Thank you very much, I will try those fixes and get back to you.

I also wanted to mention that when we manufacture this machine with new pc hardware and this new software we get the latency warnings but the machine performs without issues. I don't know if that is relevant or not.

Fixed the outputs and inverts for 7i95t, 7i96, 7i96s, 7i97 and 7i97t.

JT

Yes, that is the BOB with very slow optos, and as long as you get latency warnings, the steps might and will be missed, so
-Set the base period to 100000
-set the drive microstepping to 1600
-set the parport reset time to 10000 in the hal file
-set the step time and space to 10000 in the ini
If you still get latency warnings, in BIOS:
-disable hyperthreading
-disable TPM
-disable "aggressive PCI-E power something or another"
-disable any power saving option, like C states, turbo, speed step, etc

The drift might be something physically slipping. Mark any shaft-to-pulley or coupler joints to be sure.
Hopefully it isn't the encoder slipping on the motor shaft, that would be very difficult to detect or fix.

It is unlikely to be lost steps in a closed-loop system, and also unlikely to be lost encoder counts, but it's not entirely impossible.