Sorry.  I thought I was asked what the ip was of the 7i92.  That's 
192.68.1.121.  The Pi is 182.168.1.1 I believe.  They aren't the same.  
Remember.  LinuxCNC works and moves motors.

Once I had the Pi running the only thing I had to 'repair' in the INI file was 
the speed of the Z axis.  The last time I ran the Pi the machine still had a 
stepper motor and Gecko on the knee.   Now it has the 750 Bergerda instead and 
can do 150 ipm instead of 24 ipm.  So the ratios and max speed/accel were 
different.

After that full speed ahead.  And then shut down linuxcnc and try from the 
terminal again and still no luck.

John


> -----Original Message-----
> From: Sam Sokolik [mailto:samco...@gmail.com]
> Sent: June-11-21 4:55 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> 
> The IP address of your pi is 192.168.1.121?  That is the normal IP address
> of the 7i92...  Might be your problem.   Also what subnet is your wireless
> network?  If it is also 192.168.1.x it also could cause problems.   That is
> why I normally set the jumper on the mesa so it is 10.10.10.10
> 
> On Fri, Jun 11, 2021, 2:59 AM John Dammeyer <jo...@autoartisans.com> wrote:
> 
> > Thanks Sam,
> > I'll check it out.  Just got out of the shop.  I remove the PC and plugged
> > the Pi4 back into the system.  Homed, then G0 X0 Y0 Z0 A0,  after that ran
> > a G-Code that cut a spiral.  All nice and smooth and quiet with the servos.
> > Closed LinuxCNC.  Then into terminal and cd ~/mesaflash.  Same thing.
> >
> > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > lbp16_access.send_packet: Resource temporarily unavailable
> > Aborted
> >
> > I'll check your link.   Has to be something really simple I think.  The
> > fact that the mesaflash compiles and runs on a PC and a BeagleBone (that I
> > didn't expect) suggests to me the problem isn't with mesaflash.
> >
> > ...
> >
> > OK.
> > Static ip_address=192.168.1.1
> >
> > I don't have the /24 but my 7i92 is 192.168.1.121 and the fact that I can
> > use the CNC suggest all is good.
> >
> > I can try adding that /24 to see if it makes a difference but first I'd
> > like to know why it's needed.
> > ...
> > No change.  LinuxCNC still moves things.  But mesaflash comes up with the
> > same error.
> >
> > John
> >
> >
> >
> > > -----Original Message-----
> > > From: Sam Sokolik [mailto:samco...@gmail.com]
> > > Sent: June-11-21 12:19 AM
> > > To: Enhanced Machine Controller (EMC)
> > > Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H
> > >
> > > I just used mesaflash the other day on the rpi4 for the 7i92.   It has
> > been
> > > a while but I think I followed the network directions here...
> > >
> > > https://gnipsel.com/linuxcnc/uspace/rpi4-eth.html
> > >
> > > On Fri, Jun 11, 2021, 12:58 AM Ralph Stirling <
> > ralph.stirl...@wallawalla.edu>
> > > wrote:
> > >
> > > > Did you set a static ip for the pi in /etc/dhcpcd.conf?  It worked for
> > me
> > > > after I did this.
> > > >
> > > > -- Ralph
> > > >
> > > > On Jun 10, 2021 8:02 PM, John Dammeyer <jo...@autoartisans.com> wrote:
> > > > CAUTION: This email originated from outside the Walla Walla University
> > > > email system.
> > > >
> > > >
> > > > Peter Wallace and I have been working on getting the Pi4 to work with
> > the
> > > > 7i92 mesaflash program.
> > > >
> > > > He asked me to do this but I get the error below.
> > > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid
> > > > lbp16_access.send_packet: Resource temporarily unavailable
> > > > Aborted
> > > >
> > > > When I do this on the PC with the same 7i92 it dumps the Pins table.
> > The
> > > > 7i92 is communicating with the board.  It can ping it.  It can detect
> > what
> > > > type of board it is.  But the --readhmid parameter always returns this
> > > > access.send_packet error.
> > > >
> > > > Any ideas on how to solve this problem?  It appears to be some sort of
> > > > network issue.  The Pi4 has successfully run my CNC hardware through
> > the
> > > > 7i92 so Ethernet works.  At least from LinuxCNC to the Pi.   Clearly
> > not
> > > > from the mesaflash to the pi.
> > > >
> > > > To get mesaflash onto the Pi4 you have to do the following.
> > > > pi@linuxcnc:~ $ sudo git clone
> > > >
> > >
> >
> https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgithub.com%2Flinuxcnc%2Fmesaflash&amp;data=04%7C01
> > > %7Cralph.stirling%40wallawalla.edu
> > %7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c8debfb75e7aa64%7C0%7C0
> > >
> >
> %7C637589773748714746%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M
> > >
> > n0%3D%7C1000&amp;sdata=yZ4IL4wTuuULCOB%2Fg9S9T3q2E1szCUPkKe5gaC2oIoc%3D&amp;reserved=0
> > > > pi@linuxcnc:~/mesaflash $ sudo apt-get install libpci-dev
> > > > pi@linuxcnc:~/mesaflash $ sudo make
> > > >
> > > > Once that's all done:
> > > > pi@linuxcnc:~/mesaflash $ ./mesaflash
> > > > Mesaflash version 3.4.0~pre1
> > > > Configuration and diagnostic tool for Mesa Electronics
> > > > PCI(E)/ETH/EPP/USB/SPI boards
> > > > Try 'mesaflash --help' for more information
> > > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --addr
> > > > 192.168.1.121
> > > > ETH device 7I92 at ip=192.168.1.121
> > > >
> > > > Any suggestions are welcome.
> > > > Thanks
> > > > John Dammeyer
> > > >
> > > >
> > > > "ELS! Nothing else works as well for your Lathe"
> > > > Automation Artisans Inc.
> > > > www dot autoartisans dot com
> > > >
> > > >
> > > > _______________________________________________
> > > > Emc-users mailing list
> > > > Emc-users@lists.sourceforge.net
> > > >
> > > >
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Femc-
> > > users&amp;data=04%7C01%7Cralph.stirling%40wallawalla.edu
> > %7C4f063130e6174fe6087c08d92c856741%7Cd958f048e43142779c
> > >
> >
> 8debfb75e7aa64%7C0%7C0%7C637589773748724742%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> > >
> >
> CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=maLrElZOTYs0pWjJlpt1FpNKzGRGca8Yhuz1Yjny8Q0%3D&amp;reserved=0
> > > >
> > > > _______________________________________________
> > > > 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
> >
> >
> >
> > _______________________________________________
> > 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



_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to