I think I'm just too quick for it. Just because axis.ngc is gone off the screen apparently doesn't mean that MachineKit is done.
So editing a .hal or .ini file, saving the file, closing axis and then clicking on the desktop icon to restart machine kit results in this error. If I wait 30 seconds or more then I don't get the issue. Why it takes so long I don't know. John On Friday, May 18, 2018 at 10:55:07 PM UTC-7, Schooner wrote: > The problem with this run is right at the beginning of the error print. > > rtapi/rtapi_msgd.cc:247 ERROR: found existing RT instance with the same > instance id (0) > > > Your last run did not close down properly and when it tried to create a > new one found the instance number already in use > Linuxcnc was never conceived as being able to run more than a single > instance, so the numbers tend to be the same every time which is how this > error shows. > > Why it isn't closing down properly is another matter. > > On 5/19/2018 5:18 AM, John Dammeyer wrote: > > I'm running a BBB with Xylotex BBB-DB25/26. Often when I start up > MachineKit I get the opening banner, it vanishes and then a minute or so > later pops up with an error window. Attached is the dump. I can restart > and MachineKit begins normally. Or maybe it fails again and then runs > correctly the third time. > > Also, the Xylotex uses the DB25-1 pin as IOPWR# which is an active low > signal coupled through the ESTOP switch to DB25-10. I've added a pull up > resistor to DB25-1 and it's coupled to an active low Relay Driver circuit. > The relay connects the ESTOP DB25-10 input to ground. > > When MachineKit starts properly it blips the DB25-1 pin low for about one > second before it finishes starting up and then keeps that output off (at > +5V) until the ON button is clicked. And if the ESTOP button or ESTOP or > LIMIT switches are activated the IOPWR# also returns high and the relay > goes off. So everything works correctly except for the pulse on the IOPWR# > pin when MachineKit starts up. > > This does not happen when the Beagle boots from power up. Only when the > Icon for MachineKit with my G3616 ini and hal file configuration is clicked > and MachineKit starts rather than fails. When it fails and throws up the > log window the output is not blipped. > > I've mentioned them both because I don't know if they are related. > > Here's the failure. > Loading Real Time OS, RTAPI, and HAL_LIB modules > rtapi_msgd startup failed - aborting > > Debug file information: > rtapi/rtapi_msgd.cc:247 ERROR: found existing RT instance with the same > instance id (0) > /usr/libexec/linuxcnc/rtapi_msgd: failed to create global segment > /usr/bin/linuxcnc: line 750: 3503 Segmentation fault $HALCMD -i > "$INIFILE" -f $CFGFILE > > > Is this perhaps as simple as an older version that just needs to be > updated? If it's an error in the HAL file why doesn't it show up every > time? > > Thanks > > > -- > website: http://www.machinekit.io blog: http://blog.machinekit.io github: > https://github.com/machinekit > --- > You received this message because you are subscribed to the Google Groups > "Machinekit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > Visit this group at https://groups.google.com/group/machinekit. > For more options, visit https://groups.google.com/d/optout. > > > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
