Hello Guest it is April 18, 2024, 08:28:20 PM

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 »
611
Hi,
this is from the Mach4 API document file. There is no equivalent document for Mach3 but the procedure is almost identical.

Code: [Select]
Probing
Motion plugin probing procedure.
The probe moves are really just G01 moves in exeact stop mode with the addition of being marked as EX_PROBE in the execution_t struct from mcMotionCyclePlannerEx().

When executing a G31, the core considers the move as an exact stop move and therefore will request a motor stop report. It waits on one of two conditions:

A probe strike condition where the motion plugin calls mcMotionSetProbeComplete().
An end of move condition where the motion plugin reports the motors as being still.
Until either of these conditions are satisfied, the core will generate no more moves after the EX_PROBE marked moves. In other words, all you will get out of mcMotionCyclePlannerEx() will be EX_NONE type data. In the event of a probe strike, this makes it safe to clear the planner and be sure that future moves are not removed by accident.

A motion plugin should implement probing in the following way:

Upon seeing the first move marked as EX_PROBE, the plugin should arm position latches on the hardware.
Then consume the EX_PROBE marked moves as normal.
If the probe stikes, the plugin should:
Cancel any motor stop report requests (retrieved from then execution_t::move_t::exMotors structure). (see below. VERY important!)
Report the latched positions via mcMotionSetProbePos() for each motor.
Clear the hardware of any additional moves.
Call mcMotionClearPlanner() to clear the Mach planner of any unretrieved EX_PROBE moves.
Update Mach with the hardware's current position via mcMotionSetPos().
Call mcMotionSetProbeComplete().
If any motor stop report requests has been received, do not acknowledge them. mcMotionSetProbeComplete() does this for you and a position sync as well.
If no probe strike, then the move continues to it's end point as if it is a regular move.
The plugin should ack any motor stop report requests with mcMotionSetStill().
The positions latches should be disarmed (if needed) when a MSG_PROBE_DONE is seen.
In the event that the probe move is aborted, the plugin should:
Call mcMotionClearPlanner() to clear the Mach planner of any unretrieved EX_PROBE moves.
Call mcMotorSetPos() for each controlled motor.
Call mcMotionSync.
Call mcMotionSetStill() for each controlled motor.
Probe Operation Overview.
Upon executing G31, the core will mark those moves as EX_PROBE in the data stream.
If the probe strikes before the end of the G31 move, the plugin aborts the rest of the probe moves as described above. If a probe data file has been opened via mcCntlProbeFileOpen(), then the positions recorded by the motion plugin are inserted into the probe data file in the specified format.
If the probe doesn't strike and the G31 move reaches its end point and a probe data file has been opened via mcCntlProbeFileOpen(), then the end point positions are inserted into the probe data file in the specified format.
Using the probe data file routines.
int mcCntlProbeFileOpen(MINSTANCE inst, const char *filename, const char *format);
The format argument is a printf style format with expanding macros for the axis values. AXIS_X, AXIS_Y, AXIS_Z, AXIS_A, AXIS_B, AXIS_C. It is used in the following manner:


mcCntlProbeFileOpen(inst, "myProbeFile.csv", "%.4AXIS_X, %.4AXIS_Y, %.4AXIS_Z");
This will produce a probe file in CSV format like so:



1.0000, 2.0000, -1.4356
1.0100, 2.0000, -1.4343
1.0200, 2.0000, -1.4324
...

A format of "X%.4AXIS_X, Y%.4AXIS_Y, Z%.4AXIS_Z" would yield:



X1.0000, Y2.0000, Z-1.4356
X1.0100, Y2.0000, Z-1.4343
X1.0200, Y2.0000, Z-1.4324
...

A format of "X%.4AXIS_X\tY%.4AXIS_Y\tZ%.4AXIS_Z" would yield a tab delimited file:



X1.0000 Y2.0000 Z-1.4356
X1.0100 Y2.0000 Z-1.4343
X1.0200 Y2.0000 Z-1.4324
...

int mcCntlProbeFileClose(MINSTANCE inst); Closes the probe data file.

Craig

612
Mach4 General Discussion / Re: MACH4 Manual Screen
« on: July 13, 2022, 06:47:13 PM »
Hi,

Quote
But how do install this screenset or screen,

Typically to change a screen set requires that Mach4 is running and with the <View> tab choose the <Load Screen> item and chose from the available screen sets. If you select a new screen set
when you shut down Mach your screen set preference will be updated courtesy of the ScreenUnLOad script.

Second way to do it is to create a new profile whereon you can select a particular screen set.

Craig

613
Mach4 General Discussion / Re: Loss of license
« on: July 10, 2022, 06:38:21 PM »
Hi,
the ScreenScript is conglomerate of all the smaller pieces of code that Mach puts together and compiles prior to runtime, it is not the actual source code and cannot
be edited. In the Operator Tab the menu item is 'View Screen Script', and that is exactly what it does, you can view it but not edit it. It is occasionally very useful
to be able to view it. If at compile time or runtime error occurs Mach will give you a stack dump to indicate what line number in the screen script it is. If you then view the Screen Script
you may then establish which fragment of code has the error, say one of the Lua macros you were just working on, and then using the formal editing procedures address that macro.

Craig

614
General Mach Discussion / Re: Stepper Motors and BOB LED’s
« on: July 10, 2022, 05:57:39 PM »
Hi,
the LED associated with the Step output will be ON when Step is high, and OFF when Step is low. Given that the Step pulses many thousands of times a second you might see a slight
diminishment in intensity only. The Dir LED will be ON when the axis moves in one direction and OFF when it moves in the other.

You are expecting the LEDs to confirm some high level Good/NoGood type information......they don't. ALL they is reflect whether that output is high or low....nothing else, nothing complicated.

Craig

615
Hi,

Quote
The biggest trouble I see is everything is so customizable it can be overwhelming for a newer person.

That is true, it is customizable and it can be overwhelming.....but you don't NEED to customize it.
The only custom code in my machine is to do with handling servo alarms and the wired pendant. Twenty lines of code or less,
hardly rocket science.

I do have  macros (written in Lua) that automate certain procedures that I use when making circuit boards. One has about
300 lines of code...so yes a newcomer might struggle with it. I've been using that macro unaltered for 71/2 years,. It took probably
twenty or so hours to write back then, and a steep learning curve it was, but I've used it tens of thousands of times since.

Craig

616
Hi,

Quote
Take it from a guy that has and STILL IS trying to upgrade from 3-4. It will make you very angry and there is a huge learning curve and anyone suggesting there isn't is full of it.

That is 100% correct. You need patience pills or Bourbon or both.

Quote
Mach4 is a good software for programmers and not DIYers.

This I disagree with. For regular 3 and 4 axis machines Mach4 is good to go out of the box. If any programming is required it amounts to
a few keystrokes to turn this feature on or turn that feature off, being able to program in Lua is not required.

Quote
not to mention the setup of the pins, spindle, etc.

Yes, you have to set up the ports and pins in a broadly similar manner to Mach3, and yes its challenging, but that comes
with building your own machine.

Quote
Here is a small example, my WORK ZERO does NOTHING so I have to go in and modify the script to tell it to work. You would think that would be a "from the factory" thing but evidently it isn't.

I've never had an issue with <Go To Work Zero>, it always worked out of the box, right from day one.

One of the big strengths of Mach4 is that it can be customized to your needs with Lua, the editable GUI and Mach4s modular structure.
Mach4s biggest weakness is that it can be customized to your needs. Yes, if you want to customize your machine then you will have to start coding,
and yes there is a lot of learning required to get good results, its not magic.

I've been using Mach4 for nearly eight years and its so vastly superior to Mach3 I'd slash my wrists before I'd go backwards.

Craig

617
General Mach Discussion / Re: Probe Wiring
« on: July 07, 2022, 09:24:39 PM »
Hi,
a block like:
g31 z-1 f20

will cause the machine to travel at 20 in/min to z = -1 inch or when the probe activates, which ever comes first. It does not turn around and drive upwards again.
It will, but you have to tell it explicitly what to do, for example:

g31 z-1 f20
g0 z1

The g0 z1 will cause the machine to drive to z =1 inch, presumably above the material, but only after Mach has latched the probe values into the pound registers.

Craig

618
Mach4 General Discussion / Re: Loss of license
« on: July 06, 2022, 08:02:01 PM »
Hi,
shouldn't have to. My machine PC has its licence file installed seven years ago and its still running. I've updated the Mach build about half a dozen times
over that period.

The only thing which will stop a PC from running is if you fiddle with the PC such that the PC ID changes, something like a new OS install, or a new hard drive.

Craig

619
Hi,
disconnect all the prox sensors from the power supply, and hook them up one at a time until you find the dud one.

Craig

620
General Mach Discussion / Re: Fine Tuning Stepper Motors
« on: July 04, 2022, 12:46:31 AM »
Hi,


with a 8 microstep per fullstep regime your stepper will require 1600 pulses to do one revolution. If the pitch of the screw is 10mm then:
1600 / 10 =160 steps per mm or 4064 steps per inch.

If the numbers you have supplied are correct this should be perfect, no further tuning or messing around required.

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 »