Advanced Search

JT wrote:

 

What bold text thing?

JT
 

There's a note in your docs:

NoteThere is an documented issue with Qt5 Designer and bold fonts not appearing properly.

Not sure if that's referring to the same thing but normal fonts set to bold appear fine in Designer. When run the bold text is missing. I've only tried the dark-tough theme so far but this:
 

Is turning into this for me
 
 

fully_defined wrote:

Okay. I am looking for known good values for Clearpath SDSK servos on an Avid router, specifically a Benchtop Pro. There is no way that I am the first person to set up this specific configuration.

[/quote]

Its rare to find people with identical setups. Start at about 750-1500 and see how you go once you are moving. The mass you have to move will affect the maximum value. Assume for now 3000 will be absolute maximum. Remember its a trapezoidal accelleration profile which means the deceleration is also affected by this setting. I have had to reduce accelleration to prevent the motor decelleration being overrun by the inertia of a moving mass which caused following errors.

Its better to get reliable motion instead of shooting for the stars immediately and failing.

Its likely you have only 1 encoder enabled in your hal file.

To check the pinout (and number of encoders):

mesaflash --device 7i96s --addr 10.10.10.10 --readhmid

The 200XT may be a HF start device. hyperthem machines that size are. This might mean you need to connect the thcad upstream of the HF generator. If not, It's likely to have damaged the THCAD or the 7l96 encoder. Tommy is the expert in this area.

But as PCW says, seeing 0 volt and 45 volts indicates it is working.

Rather than look at the reported voltage, check the encoder velocity pin in halshow. When not cutting, it should hover at or near the 0 volt frequency. Also it should be bouncing around. If it isn't and just a fixed value either there is an error on your encoder config in HAL or there is an issue on the high voltage side.

Using the plasma bit file, you have 3 encoders so damaging one encoder might have an easy  work around.

 

PCW wrote:

Looks like halcmd was run without running LinuxCNC

mesaflash --device 7I96s --addr 10.10.10.10 --write 7i96s_p1encd.bin

should work

mesaflash --device 7I96s --addr 10.10.10.10 --write 7i96s_p1encd.bin --reload

is probably better

 

Seemed to upgrade, but I don't see additional encoders.
Before I did the upgrade (Linux running) I captured all the hm2 stuff see: hm2names.txt
Then LinuxCNC closed,  I did the upgrade and followed up with reload, that seemed to work see upgradetxt.txt
Then captured hm2 names again see:  up_hm2names.txt
No apparent changes, and when I look in HalShow I only see encoder0, I was expecting to see a few more.

Not sure what I did wrong, unless I was supposed to do the write and reload in one pass instead of two?
     

OK, went through those, and i have to agree with PCW on number 2 here
forum.linuxcnc.org/10-advanced-configura...fb-mesa-7i76e#112557
It is pretty much useless as it does a lot of things but the thing it should do, it does not, namely amplifier fault!
I would not use it.

johnbl wrote:

I don't have the time nor money to sue Tormach to get it.

I am sure they did provide it several years back, but only on request. Did you try shoveling and e-mail in their direction?
-
Personally, i would think they should provide it publicly... but still, they were selling the full PathPilot on a USB stick for 35$, so i can not be angry at them.

Potential fallout to this issue??

 

Yes, they are in the file. Without them, the tool change cycle is not complete.
It doesn't work for me.
REMAP=T python=index_lathe_tool_with_wear
REMAP=M6 python=ignore_m6
when I use remap M6 and the carousel component.

@John,

I recieved the source and the message to not publish it on github.
If i recieve the source tonight from other source, i can just publish it right away.
And i have other source, i will ask.



 

Usually it's a Sauter revolver, but I have a test stand at home. It works the same.

tommylight wrote:

No idea where or how you got those numbers, but utmost respect for effort in getting things right.
Start with 300mm/s/s, do some tests, then go higher, but most probably 750 will be to much for short fast movements like Fusion360 does.
I am refraining from further "muddying the waters" for now as:
1. i have no idea what "HLFB" is
2. -deleted-
 

HLFB "high level feedback" is many things, but it can work like a drive alarm and that's what I will be using it for. There have been a couple of posts on it, but they all go nowhere and the OP never comes back and says "I did this thing exactly like this, and it worked. Here is how to recreate what I did."

For examples of dead ends, here you go:

forum.linuxcnc.org/49-basic-configuration/41375-clearpath-hlfb

and

forum.linuxcnc.org/10-advanced-configura...with-hlfb-mesa-7i76e

and

forum.linuxcnc.org/10-advanced-configura...ervo-with-mesa-7i76e

I just want to know what to enter into what box, and move on. I am at the pncconf step, so any talk about ini files or HAL or anything past pncconf is not yet relevant to me. I need to know what to tell pncconf what to do with the inputs I connected the HLFB circuits to. And I need to know if I have connected it properly in the first place. I don't know what I don't know.
 

tommylight wrote:

Do NOT fix drift!
All analog servo systems will have a bit of drift at 0V input.
Wire the control, it takes care of it when encoders are in use.
 

Well, I wouldn't go that far.  Make sure the velocity DAC is outputting zero, and then adjust the "balance" or velocity offset put to get minimum drift.  You will not be able to get it down to absolute zero, but any drift in the amp will offset your position when not commanding movement.  If you really have 12 - 16 V output to the motor with zero in, then something is QUITE wrong!  That could be an open connection to the tachometers.  If the machine has been sitting a long time, the commutator of the tachs might be oxidized, maybe running the motors a bit might clean them.  Or, it could be a dirty connector contact.
Jon

Send me .esi files for canOpen devices from your config... there are not supported startup SDO and it can not be generated automaticly ...

regards

No idea where or how you got those numbers, but utmost respect for effort in getting things right.
Start with 300mm/s/s, do some tests, then go higher, but most probably 750 will be to much for short fast movements like Fusion360 does.
I am refraining from further "muddying the waters" for now as:
1. i have no idea what "HLFB" is
2. -deleted-