Hi Gene, You could use this:
http://mesaus.com/index.php?route=product/product&path=71&product_id=59 with this: http://mesaus.com/index.php?route=product/product&path=71&product_id=70 To get 7' between the 7i90 and the PC. JT On 12/24/2016 6:20 AM, Gene Heskett wrote: > Greetings folks; > > This is a heck of a thing to throw out on Christmas Eve. > > I am about burned out on trying to make the raspi 3b work. > > I saw it work once, for about 2 days, then an update blew it up by > replacing the rt kernel, and it has not worked since. In the sd cards > I've made since, probably 8 or more, following the recipe given, the > halrun;halc md loadrt hostmot2;loadrt hm2_rpspi test procedure works > perfectly. But linuxcnc refuses to load that hm2_rpspi driver. > > Mr. Martinjack built me an image and sent me the link to it. No gui, so > testing would have to be done over an ssh -Y login. He, I believe went > to quite some effort to do that, and I assume that it worked on his > raspi-3b. But when I wrote it to a zeroed 32Gb card, expanded the > filesystem on the first boot, then configured the networking in static > mode, making it immutable as I went so whatever raspian uses in place of > network-mangler can't tear it down on the next boot, the result can't do > the halrun test. > ------------------------------------------- > pi@raspberrypi:~ $ halrun > halcmd: loadrt hostmot2 > Note: Using POSIX realtime > hm2: loading Mesa HostMot2 driver version 0.15 > halcmd: loadrt hm2_rpspi > Unknown board: HOST???? > hm2_rpspi: rtapi_app_main: Operation not permitted (-1) > <stdin>:2: waitpid failed /usr/bin/rtapi_app hm2_rpspi > <stdin>:2: /usr/bin/rtapi_app exited without becoming ready > <stdin>:2: insmod for hm2_rpspi failed, returned -1 > --------------------------------------------- > which is the same failure I get when trying to start linuxcnc on one of > my builds. > > And this is the 2nd pi-3b I've put in. > > Does my use of a 32GB card have anything to do with this? > Does my use of the full jessie install instead of the jessie-lite have > anything to do with this? I can try that once. > > If that fails, I'll quit beating my head with a hammer and reset this > 7i90 to an epp interface and go back to an x86 computer to drive it, but > that brings up the next $64K question. The big old Dell I have to drive > it with isn't swarf proof by any means, and it will take at least 6 or > even 8 feet of ribbon cable to get it far enough away from the swarf to > be safe from flying chips. Can I use a ribbon cable that long with good > results? The man page says it could be a problem but doesn't say how > long is too long. And I've no clue if the parport on this old Dell can > be made epp-1.9 compliant. TBD I guess. > > Thanks everybody. And have a Merry Christmas. > > Cheers, Gene Heskett ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users