> John you have Linuxcnc working on a BBB using a Mesa ethernet card ? > > If so would you mind if I started a new topic to pick your brain. > > To the OP please accept my apologies for going so far off topic. > > > Cheers > > Rob
Hi Rob, Not quite and given the problems I've had with the Linux I out into a dual boot laptop this week (i686 and mesaflash RTAI that predates 7i92) my guess is that although I can talk to the 7i92 with the mesaflash on the beagle I doubt it will actually run. That beagle isn't a machinekit OS. Just normal Stretch for developing Lazarus Free Pascal code for CAN bus. (That's another project and story). The attached very preliminary install instructions for setting up the Pi4 to work with the 7i92 I followed to the letter on the Beagle. And to my amazement it worked. Especially since the Beagle had a pretty strange IP number. And it worked without needing the --addr 192.168.1.121. Thing is. The Beagle with the PRU's can do very simple CNC when using MachineKit which I understand has even itself split with all the work done on the bottom end and nothing on the actual LinuxCNC part so it's apparently a bit long on the tooth. But now with the Pi4 4GB for about $70 compared to a Beagle for about $60 the extra capability of the MESA family by far outweighs what you can do with the Beagle without adding yet more I/O and being stuck with a crappy slow HDMI video interface. Now having said that, and this _is_ off topic, with an SPI + I2C based touch screen in the 7" to 10" size a Beagle with a cape that does the rest of what my ELS does would be a great solution since a lathe has only two axis and needs really only quadrature encoder support and for the most part PWM for 0-10V. But whether that sits on top of MachineKit instead of Axis and is an ELS with some limited G-Code capability is the question. Is it worth it? One saves the money spent on a 7i92 and frees up all sorts of pins without the HDMI. In fact the pocket beagle at even less money would probably be great. So I wouldn't use a Beagle with the 7i92. A Pi4 4GB + 7i92 is a better and cheaper solution since you get more I/O along with the support. And if you haven't yet bought a PMDX or CNC4PC or other $160 BoB then one of the other Mesa Ethernet products might be the best choice with the Pi4. My two cents. And I really have spent way more than that in time trying to get the 7i92 to talk to the Pi. John > -----Original Message----- > From: Robert Murphy [mailto:robert.mur...@gmx.com] > Sent: June-11-21 9:06 PM > To: emc-users@lists.sourceforge.net > Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H > > Sorry a bit OT > > > > On 12/6/21 1:33 pm, John Dammeyer wrote: > >> From: Peter C. Wallace [mailto:p...@mesanet.com] > >> On Fri, 11 Jun 2021, John Dammeyer wrote: > >> > >>> Date: Fri, 11 Jun 2021 17:05:53 -0700 > >>> From: John Dammeyer <jo...@autoartisans.com> > > > >>>> I don't think this is his problem, since his rpi Linuxcnc talks to the > >>>> 7i92 just fine. Only mesaflash is having trouble. > >>>> > >>>> Have you tried explicitly specifying --addr 192 168.1.121? > >>>> > >>>> -- Ralph > >>>> > >>> There is no electrical difference. Just one DB connector and one header > >>> for > >>> the non H variety. It turns out setting the address as --addr > >>> 192.168.1.121 > >>> or if the W5 and W6 are changed to reflect EEROM IP address of default > >>> 10.10.10.10 then all commands must have --addr 10.10.10.10. > >>> > >>> Reading the manual again it appears that --addr is only needed if the > >>> default > >>> 192.168.1.121 is not in use on the 7i92. That's incorrect with a Pi4. > >>> It's > >>> correct with a PC and a Beaglebone. > >> Looking at the code, thats pretty strange. The address default is just > >> "192.168.1.121" Have you tried without the "sudo"? That's not needed > >> for Ethernet connected cards > > Makes no difference if the sudo is there or not. > > First just to show that from a physical perspective the 7i92 is there on > > 192.168.1.121 > > > > pi@linuxcnc:~/mesaflash $ ping 192.168.1.121 > > PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data. > > 64 bytes from 192.168.1.121: icmp_seq=1 ttl=64 time=0.120 ms > > > > But the mesaflash software doesn't know it's supposed to use the default ip. > > pi@linuxcnc:~/mesaflash $ ./mesaflash --device 7i92 --readhmid > > lbp16_access.send_packet: Resource temporarily unavailable > > Aborted > > pi@linuxcnc:~/mesaflash $ ./mesaflash --device 7i92 --addr 192.168.1.121 > > --readhmid > > Configuration Name: HOSTMOT2 > > > > General configuration information: > > > > BoardName : MESA7I92 > > FPGA Size: 9 KGates > > FPGA Pins: 144 > > > > > > BTW. The upside is that now we have something reproducible. It may well > > be something outside of mesaflash but the issue > doesn't show up with older versions of the OS and what really amazed me is it > worked on the Beagle. Has me wondering if booted a > machinekit onto the beagle would it work? Probably not. The hm2_eth is > probably not compatible with machinekit but just curious. > > > > > > > > _______________________________________________ > > Emc-users mailing list > > Emc-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-users > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users
Mesaflash_Install_Instructions.pdf
Description: Adobe PDF document
_______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
