Hello Guest it is April 25, 2024, 04:12:30 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - joeaverage

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 »
171
Mach4 General Discussion / Re: Screens BUG
« on: March 18, 2023, 07:19:51 PM »
Hi,
Mach4 is predominantly a CNC software solution, its meant to control a machine. As it turns out NFS have built in a screen editor, and by in large it does pretty well,
for the benefit of users to customise it for their installation, but its not a software development environment. It is not, nor was it ever intended to be a software
development tool,......Mach4 is a machine controller....and that it does extremely well.

The sort of features that you are talking about are commonplace in development programs like MS Studio, not so much in Mach4.

Craig

172
Mach4 General Discussion / Re: Script da mach3 a mach4
« on: March 18, 2023, 07:12:42 PM »
Hi,
Mach4 can be programmed to do as you wish, but......this is the big but......Lua is quite different to VB as is the structure between Mach4 and Mach3.

There is no direct translation from one to the other, there is a distinct learning curve, and most people find that they come to hate Mach4 before they
get accustomed to it and come to love it. It would be reasonable to expect that it could take a month of some very intense learning before you
would be confident to start writing your own code.

The Auto Tool Zero is commonplace and you will find that there are many examples from other forum members that you can copy and adapt to your machine.
Tool changers are much harder because it seems that every tool changer is different to the next, and copying someone else's code is not likely to work,
you have to generate your own.

Mach4 has a very distinct learning curve. You would be advised to allow plenty of time for a transition...if you are under strict time constraints for a business
for example that could make something which is just challenging to really bloody hard!

Craig

173
Mach4 General Discussion / Re: mpg "Velocity mode"
« on: March 18, 2023, 07:00:59 PM »
Hi,

Quote
Is there a way to implement the Mach3 mpg Velocity mode in Mach4?

Yes there is but its not straight forward.

If you have an MPG, that is connected to your breakout board and thence to your motion controller. Your motion controller then passes the numeric number of clicks to Mach
which then issues the move instructions depending on the selected current increment. It works fine....proivided you don't spin wheel too fast and end up with a whole bunch of after-run,
that can ruin your day!

That describes how incremental mode works, but what about velocity mode.? For this purpose I would suggest you experiment with Mach by writing some macros that do
velocity jogging using the API's:

Code: [Select]
LUA Syntax:
rc = mc.mcJogVelocityStart(
number mInst,
number axisId,
number dir);

Description:
Start a velocity jog on the given axis.

and:
Code: [Select]
LUA Syntax:
mcJogVelocityStop(
number mInst,
number axisId)

Description:
Stop a velocity jog on an the given axis.


Basically you start a velocity jog and then some time later you stop it, usually by lifting your finger off the jog button on your keyboard.

This does not work with an MPG, it sends a series of pulses which are ALWAYS interpreted by Mach as incremental moves.

What I did is modify my pendant, I made it so I figure that I can do what I like with it, such that when I want Velocity mode jogging I hold a sprung loaded
toggle switch, and then the microprocessor inside my pendant issues a continuous signal but ONLY WHILE I spin the MPG at at least one click per second.

If you like the MPG becomes the logical equivalent of a keyboard button, when the MPG is spinning (above some minimum rate) the button is pressed, and when its not spinning
the button is released. Thereafter its simply a matter of writing jog scripts to match the 'button presses'. The axis select switch works per normal.

Note that this relies on a small microprocessor in my pendant, and that you can program it. This is the complication that I refer to.

Craig

174
General Mach Discussion / Re: Mach4 and Gecko G540
« on: March 18, 2023, 06:42:59 PM »
Hi,
there is a legacy parallel port for use with Mach4, its called Darwin and attracts a $25 license fee. I think its called Darwin because its the last of the breed.
It was written by Art whom also wrote Mach3's parallel port driver at the beginning of time.

It was meant and intended as a cheap way for people to try Mach4.....but it has limitations. For instance a lot of the realtime supports are missing, lathe threading for example,
and THC for another. They will not EVER be included in the driver, so don't get your hopes up.

Secondly it is still a parallel port driver and MUST run on 32 bit Windows OS's, Windows 7 and Windows XP. The same problems that beset Mach3's parallel port driver like
stuttering and stalling should other software compete for CPU service beset Darwin also.

So provided you have a 32bit PC you might be able to get the G540 to work from a DB25 parallel port. Note that does NOT include any USB to DB25 converter, they may drive
a printer OK, but no good for Mach. The UC100 that Tweakie recommended has an FPGA inside and is way WAY WAY cleverer than any USB to DB25 converter, not withstanding
that is exactly what it looks like. If a UC100 appeals do not buy one of the many hundreds of Chinese rip-offs on Ebay or Amazon, buy genuine or don't waste your money. The rip-offs
are not a patch on the real thing.

In reality Mach4 is intended for use with an external motion controller as Tweakie has recommended. I use an Ethernet SmoothStepper and have done for eight years.
It is arguably the best, modestly priced ($200 or less) Mach4 motion controller on the market. Some of the other competing modestly priced motion controllers like the UC series form CNCDrive, the PoKeys57CNC
etc miss on some of the realtime supports that the ESS has as standard, the most glaring, but not the only one is realtime THC. The Hicon has all the normal realtime supports but is very much
more expensive, but otherwise a good unit.

There is one Chinese made Mach4 ready controller made by XHC, but the plugin is hopelessly buggy. It does not support the editable GUI for instance, you are restricted to wxMach as a screenset.
Avoid like the plague.

Craig

175
CS-Lab / Re: update to M4 .5000 version
« on: March 16, 2023, 04:48:20 PM »
Hi,
there has been some discussion on this matter on the Mach4 General Discussion board. It would appear that build 5000 caused problems for more than just CSLabs.

Apparently certain sections of build 5000 code run very very much faster than had been the case with earlier build and various controllers including CSLabs have been caught out,
it causes a 'race' condition.

NFS has contacted all the manufacturers of Mach4 ready controllers and they are working towards a solution.

CSLabs responsiveness to this sort of issue used to be legendary, but in recent years their commitment to fixing plugin problems has diminished markedly. Shame really, CSLabs had an
enviable reputation.

Craig

176
Mach4 General Discussion / Re: Mach4 default scripts
« on: March 16, 2023, 03:46:26 PM »
Hi,
that is exactly how I handle my own m3/m4 scripts also.

This is where using lowercase is important. When Mach encounters an m3 it searches in the macros folder of the current profile, if it find it then it uses it. If it does not
find it it searches up the file tree until it does. Using lowercase will ensure, or at least increase the probability, that Mach will search and find the macro
that you intended to be used as opposed to the in-built macro.

Craig

177
Mach4 General Discussion / Re: Mach4 default scripts
« on: March 16, 2023, 03:26:37 PM »
Hi,
I have never seen the scripts published anywhere. May I suggest you look at the SpinOn/SpinOff buttons in the Sreen editor.
The SpinCw and SpinCCW scripts are in the ScreenLoad script excerpted here:

Code: [Select]
---------------------------------------------------------------
function SpinCW()
    local sigh = mc.mcSignalGetHandle(inst, mc.OSIG_SPINDLEON);
    local sigState = mc.mcSignalGetState(sigh);
   
    if (sigState == 1) then
        mc.mcSpindleSetDirection(inst, 0);
    else
        mc.mcSpindleSetDirection(inst, 1);
    end
end
---------------------------------------------------------------
-- Spin CCW function.
---------------------------------------------------------------
function SpinCCW()
    local sigh = mc.mcSignalGetHandle(inst, mc.OSIG_SPINDLEON);
    local sigState = mc.mcSignalGetState(sigh);
   
    if (sigState == 1) then
        mc.mcSpindleSetDirection(inst, 0);
    else
        mc.mcSpindleSetDirection(inst, -1);
    end
end

Next suggestion is you need to write all your scripts in lower case, eg m4, m4 and m5. Mach's interpreter parses all Gcode to lowercase, strips out leading zeros and
whitespace. Usually human readable code is interpreted correctly but sometimes its not and it's a devil of a bug to find. Get used to writing all Gcode in lowercase.
I tend to still include whitespace for the sake of readability, but write Gcode in lowercase to better match Machs interpreter.

Craig

178
Mach4 General Discussion / Re: I don't see the "SIMULATOR" tab
« on: March 14, 2023, 06:12:14 PM »
Hi Steve,
thanks for the clarification.

Quote
Perhaps you could investigate the possibility but it will likely be much more expensive.

Crikey.....I'm still reeling from the thousands spent on the hardware for my fourth axis ($2000NZD)  and the hardware investment for
the fifth axis ($1700NZD and counting), not looking to spend any more money at the moment, and may not ever again!! ;D

Craig

179
Hi,
using a torque limit to detect the presence of the plate is to drive the tip of the plasma into the plate...if you think that is good for your $500USD watercooled Hypertherm plasma tip ....
go for your life. I'm saying that NO servo should be used in this manner. Lets ay you set a torque limit of 1Nm being a suitable value to get worthwhile acceleration
of the axis. Then that same 1Nm would be applied via the ballscrew to the plasma torch before any over-torque detection could occur. It does not matter how
fast the servo can react it will and must apply its torque BEFORE it can detect that the torch has impacted the plate. The force will likely destroy the tip.

That is what a G31 probing move is for. There will be a certain amount of after-run AFTER the plasma tip has contacted the plate, depending on the speed of the probing move
and the deceleration of the axis. At 50mm/min probing speed and 0.15g acceleration the after-run of my mill is 1.15um. The force between the tip and the plate at 1.15um
interference is minimal. This is the strategy used by nearly all manufacturers to set torch height and is supported by all controllers.

Fact: Clearpath has one, and only one digital output, and by PWM of that output one, and only one, analog variable.
Clearpath servos use an encoder of 12800 count per rev
Clerapath want $517 for a 400W servo

Compare to these facts: Delta (B2 series) has six digital programmable digital outputs, two analog outputs, a full suite (A,B,Z) auxillary output encoder
and an analog input for velocity and torque modes.
Delta (B2) has a 160,000 count per rev encoder, vastly better.
Delta (B2) 750W kit (servo, drive and cables) costs $438.

With Delta I get twice the power of a Clearpath servo for less money.

My opinion is that Clearpath have poor IO capability, modest (at best) encoder resolution, and are expensive for what you get. This is assessment of FACT. It is not misinformation
or disinformation, but a personal assessment of FACT. I can well understand that you don't like it....but tough, I have an opinion and am entitled to it.

I understand also, and certainly approve that you should wish to correct any factual misinformation about your products but I do not have to agree with your conclusions or opinions,
facts yes, opinions no.

Now lets talk about OP's actual situation.

He needs a signal to indicate when the plasma tip touches the plate. Lets say you devise a strategy to use the HLFB to indicate that condition, then how would you indicate
a Following Error or overload condition? You only have one output, and by definition if you use it to signal one condition you cannot use it to signal a fault as well, its one or the other.

Quote
the Mach controller can still easily stop the other axes from moving and crashing when any motor shuts down. I’m not sure why you think this is not possible;

Of course its possible, that is after all the primary purpose of the HLFB.....but you can only use it once.

Quote
What you said about the ClearPath being designed specifically to appeal to “first time servo buyers” is incorrect. You’ve mentioned this on other forums before, but I wanted to address this here because others reading your post may not realize it, so I will quote/paraphrase what a colleague of mine recently wrote to you:

Design decisions made for the ClearPath motors were done with our typical OEM user base in mind (generally experienced controls engineers in a wide variety of machine automation industries). In addition to high-performance and value, these companies tend to value overall system reliability very highly. By incorporating many features into the motor’s firmware, we were able to remove the need for many additional inputs and outputs, thus increasing the overall system reliability.

Our experience over more than thirty years of technical support has proven that the biggest cause of malfunction in machines using servos is electrical corruption of the input and output signals, or intermittent or bad connection of one or more signal wires. We, and our customers, have found that overall system reliability is greatly enhanced by reduced wiring.

Despite the fact that Teknic products are designed for the OEM market (see the About Us page on our website), a side effect of the reduced wiring problems and the ease with which a ClearPath servo system can be implemented, is that many corporate end-users and hobbyists have been attracted to ClearPath. And even though we didn’t set out originally to sell to end-users and hobbyists, we are happy that ClearPath has been well-received, and we enjoy supporting such a wide range of people and applications. Supporting first-time users has been an interesting experience for us over the years since ClearPath was introduced, and it has led us to create even better website features, documentation, and support videos among other things. And that is a win for everyone.

All opinion only, and not all of which I agree with.

For instance your name for your servos 'Stepper Killers', is that or is that not designed to entice first time buyers?

I would agree that Tecknics do a a masterly job at supporting customers, and I have never claimed otherwise. I would also commend that Tecknics follow on-line forums for any issues related
to your products, to whit, you and your colleagues have taken me to task about my opinions on forums other than this one. As I have stated I base my opinions on the facts of Clearpath servos
and and willing to change my opinion in light of new facts, but refuse to be badgered out of my opinion without new facts. That you don't like it is immaterial to me.

180
Mach4 General Discussion / Re: I don't see the "SIMULATOR" tab
« on: March 14, 2023, 04:00:20 AM »
Hi,
kool, tell us how it works.

I have a fourth axis but the toolpath display is fine for tree axis but crap for four. I'm building a fifth axis and it sure would be nice to see a
3D render of the toolpath.

Craig

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 »