Advanced Search

PCW wrote:

It may be that firmware that better matches your application can be made
(MPGs are better with MPG encoders rather than motion encoders because
MPG encoders support 1X mode which works better with MPGs having detents)

 

Interesting, I have some MPG style encoders on order, I suppose I can look into this when they arrive.

After looking at the TVS's I put on my little daughter board I came to the conclusion that they were not going to help (not Schottky and Vmin specified as -0.3V) so I replaced with actual digital isolators. Presently the first two P1 encoders are routed to my scale encoders and the next two for MPG's.  So before I hit the send key can I assume that if a version with MPG friendly logic is available it will map the MPG encoders to P1 pins 7-13 or would they move to pins beyond the as is 4 encoders (P1:1-15), it would be easy for me to move my MPG inputs down to say IO:46-49 so they don't interfere with the original 4 encoder inputs if that make sense?
 

 

>Whether it is your present depends on a lot of factors. Usually money

OK. In my case, Pulse/Dir has been working reasonably well for my needs so far, and most importantly I was able to get it working with very limited (aka known) knowledge to start with.

However, since I chose the most simple/cheapest way using parport and basic Bob, I have no room to implement things that would be really useful, such as 4th axis, tool gauge, feedback to LinuxCNC, etc... Any solution that would remove these limitations would require money, so I might as well go for some sort of industry standard, or at least a solution that is not strictly dependent on a single vendor.

This discussion conforts me in the idea that EtherCAT seems a logical choice in this respect, so thank you all for sharing your knowledge and experience

rodw wrote:

Sorry, I have not had a chance to look at this over the weekend.
 

Yeah I figured that cos building an image with the 6.12.y branch fails when creating the final image. 6.1.y with the 6.1.69 kernel commit seems to build ok, image is created with Linuxcnc binaries and when patch has spi on at first boot. This was just seen by mounting the image and having a quick browse through the filesystem. Too effing late to test.