Thanks Andy
now to read the code :-|
BTW you note about using 'no interface' from mesa to g540 worked very well.
( all 3.3V compatible )
Previous max velocities of 1300mm/min at 1/2 step
( max constrained by PICnc and machine resonance)
have increased to a reliable 1500mm/min
( 1/10 step using 5i20/G540's higher steprates)
and in pncconf, over 2000mm/min sounded/felt ok !
So there's a big advantage to smoother motion
And a disadvantage of micro-stepping needing higher step rates for same
velocity :-(
( I have some triaminic TMC2130 drives on the way :-)
I'm playing it safe until the parts are inside the cabinet and nailed down
.Thanks!
I can return to RPi/PICnc later
( brand new old PIC32mx150f128s arrived from Texas with a 4 day turn
around :-)
tomp
On 03/31/2019 02:41 AM, andy pugh wrote:
On Thu, 28 Mar 2019 at 01:38, TJoseph Powderly <tjt...@gmail.com> wrote:
Thats another problem, can a comp have its own modules?
Like, can a generic SPI host comp have specific client sub-comps?
How to talk to different devices with same protocol?
Sort-of. For example the Mesa driver has two or more parts.
You first need to load the Holstmot2 driver, and then you load the
hm2_pci, hm2_eth, hm2_spi etc drivers to access the various types of
cards.
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
