586,385 active members*
3,457 visitors online*
Register for free
Login
Page 2 of 2 12
Results 21 to 33 of 33
  1. #21
    Join Date
    Apr 2006
    Posts
    402
    Thats kind of cheap. This part in Norway, goes for 37$ or something...
    But then, which applies for electronics in general: if you can buy it in low quantities, not per tube or minimal ordering amount of 250 Euro. Then if you completed your design, they take your selected chip out of production and replace it with a chip with changed and reduced capacities. And if possible with complete new to learn software.
    Chips: the nearest to Unobtainium you can get.

    But cheers to Analog Devices: credit card orders directly at the factory, no minimum amount, 1/10th of retail price and speedy shipping from local warehouses!

  2. #22
    Join Date
    Sep 2004
    Posts
    223
    Quote Originally Posted by RadekCX
    You find this bug? :-)
    It's the timing of the direction line switching from forward to reverse at zero degrees it would seem. If the direction switch is after the zero point the "notch" disappears and the motor has the same sound forward and reverse.

    Is _this_ the bug of which you speak?

    Alan.

  3. #23
    Join Date
    Mar 2006
    Posts
    15
    Bingo.

    Direction can you change only when current is zero amps.

    I report this bug to National Semi and wait for their reply.

    Why many peoples with your FW not locate this bug? Nobody else have not problems?

    RadekCX

  4. #24
    Join Date
    Mar 2006
    Posts
    15
    Note:

    Timing is not important only when change direction (this bug is fundamental) - timing currents through coils is important always.

    RadekCX

  5. #25
    Join Date
    Sep 2004
    Posts
    223
    Fixed.

    PICStep now has a V2.0 firmware available.

    It has a new 1/16 mode (1/16, 1/8, 1/4 and 1/2, lost full), a 5 1/2 minute auto shutdown and the direction line bug fix.

    The motor should sound exactly the same in either direction.

    I'd like to thank RadekCX for pointing this bug out, but then again the goose chase and the headaches caused by deciphering his posts probably doesn't warrant any.

    http://www.fromorbit.com/projects/picstep/

    Alan.

  6. #26
    Join Date
    Mar 2006
    Posts
    15
    Alan good job - source code is correct, but you can make this code faster.

    RadekCX

  7. #27
    Join Date
    Sep 2004
    Posts
    223
    Quote Originally Posted by RadekCX
    Alan gut job - source code is correct, but you can make this code faster.

    RadekCX
    At 20MHz the entire lookup and step decisions are done in ~65 instructions which equates to 0.0124 milliseconds per step (200ns per instruction). I could probably shave 10-15 instructions off, but I think it's fast enough.

    Plus you said yourself, yours is written in Pascal and is 7.5K versus my 1.59K and mine has the timeout function too. In embedded processors smaller is usually better. That's 4.716x better!

    Alan.

  8. #28
    Join Date
    Mar 2006
    Posts
    15
    Quote Originally Posted by Garfield2
    At 20MHz the entire lookup and step decisions are done in ~65 instructions which equates to 0.0124 milliseconds per step (200ns per instruction). I could probably shave 10-15 instructions off, but I think it's fast enough.
    Problem is bad regularity in your code, no velocity and quantity instructions. Quantity instructions affect mainly max input frequency. Bad regularity affect resonance and torgue.

    Quote Originally Posted by Garfield2
    Plus you said yourself, yours is written in Pascal and is 7.5K versus my 1.59K and mine has the timeout function too. In embedded processors smaller is usually better. That's 4.716x better!
    Uaaaa, problem is in words "usually better". :-))))

    Good luck
    RadekCX

  9. #29
    Join Date
    Sep 2004
    Posts
    223
    Quote Originally Posted by RadekCX
    Problem is bad regularity in your code, no velocity and quantity instructions. Quantity instructions affect mainly max input frequency. Bad regularity affect resonance and torgue.

    Uaaaa, problem is in words "usually better". :-))))
    Whatever... if I was designing this for an orbital satelite I might be worried. It's for homebrew CNC machines and the like, it's really not *that* important, any decent CAM software should take care of the velocity and "regularity".

    As for this pissing contest, I conceed you are the bigger pisser. Well done, be congratulated, here is your trophy...

    Alan.
    Attached Thumbnails Attached Thumbnails ist2_958973_trophy.jpg  

  10. #30
    Join Date
    Mar 2006
    Posts
    15
    :-((((

    Sorry, rather keep mum.

  11. #31
    Join Date
    Apr 2004
    Posts
    733

    Bug fix

    Stephen,

    Please email me your email address so I can send updated software fix for the EAS microstep board.

    regards,

    jimf at embeddedtronics.com


    PS
    Alan Thanks for figuring out the LMD problem and posting the details.

  12. #32
    Join Date
    Mar 2005
    Posts
    339
    RadekCX,

    Thank you, too.

    Zoltan

  13. #33
    Join Date
    Nov 2004
    Posts
    389
    Entertaining thread

    Just wanted to say, updated to latest Picstep software and it's running fine.

    Thanks for the quick turnaround Alan.

    To be honest I never noticed any problems with the old version but any improvements are worthwhile.

    Treat yourself to a Fosters....

Page 2 of 2 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •