× Forum Header

new error since upgrade to 2.6 - broken pipe

More
30 Nov 2013 01:13 #41225 by Glamplitude
Dear Forum

Thank-you all for all the help so far in my other post. I've opened a new post because of another error. Seriously, guys; I've tried valiantly to fix this one but I'm so lost... Now, in my reading of all of the other posts I can find, I've learned to attach dmesg output and also to run from the command line and all that, but it's achieved nothing.

When running Stepconf, even from the command line, I get a broken pipe error. Saga ensues:

gareth@cnc-01:~$ stepconf
Xlib: extension "RANDR" missing on display ":1.0".
/usr/bin/stepconf:1220: Warning: g_path_get_dirname: assertion `file_name != NULL' failed
self.xml = gtk.glade.xml_new_from_buffer(doc, len(doc), domain="linuxcnc")
/usr/bin/stepconf:1220: GtkWarning: gdk_pixbuf_new_from_file: assertion `filename != NULL' failed
self.xml = gtk.glade.xml_new_from_buffer(doc, len(doc), domain="linuxcnc")
/usr/bin/stepconf:1220: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
self.xml = gtk.glade.xml_new_from_buffer(doc, len(doc), domain="linuxcnc")
/usr/bin/stepconf:1220: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
self.xml = gtk.glade.xml_new_from_buffer(doc, len(doc), domain="linuxcnc")

============= I'm sure those errors are unimportant; I'm running over VNC
============= The following happens when I open the "Test axis" dialog

/usr/bin/stepconf:2225: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
widgets.testvel.set_range(0, maxvel)
/usr/bin/stepconf:2226: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
widgets.testacc.set_range(1, 100000)
/usr/bin/stepconf:2227: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
widgets.testamplitude.set_range(0, 1000)
/usr/bin/halrun: option requires an argument -- f


================================================================================

==== But when I press Jog or Run, another dialog opens with the following error:

================================================================================


Stepconf encountered an error. The following information may be useful in troubleshooting:

Traceback (most recent call last):
File "/usr/bin/stepconf", line 2035, in on_jogplus_pressed
self.update_axis_params()
File "/usr/bin/stepconf", line 2024, in update_axis_params
halrun.flush()
IOError: [Errno 32] Broken pipe
Attachments:

Please Log in or Create an account to join the conversation.

More
30 Nov 2013 02:59 #41226 by Glamplitude
Incidentally, if I run halrun -U, I get the following:

root@cnc-01:~# halrun -U
RTAPI: ERROR: could not open shared memory (errno=2)
RTAPI: Locked memory limit is 64KiB, recommended at least 20480KiB.
This can cause the error 'could not open shared memory'.
For more information, see
wiki.linuxcnc.org/cgi-bin/emcinfo.pl?LockedMemory
ERROR: rtapi init failed
HALCMD: Release Mutex failed!
RTAPI: ERROR: could not open shared memory (errno=2)
RTAPI: Locked memory limit is 64KiB, recommended at least 20480KiB.
This can cause the error 'could not open shared memory'.
For more information, see
wiki.linuxcnc.org/cgi-bin/emcinfo.pl?LockedMemory
/usr/bin/halrun: line 35: 1723 Segmentation fault halcmd stop
RTAPI: ERROR: could not open shared memory (errno=2)
RTAPI: Locked memory limit is 64KiB, recommended at least 20480KiB.
This can cause the error 'could not open shared memory'.
For more information, see
wiki.linuxcnc.org/cgi-bin/emcinfo.pl?LockedMemory
/usr/bin/halrun: line 35: 1724 Segmentation fault halcmd unload all
ERROR: Module hal_lib does not exist in /proc/modules
ERROR: Module rtapi does not exist in /proc/modules
ERROR: Module rtai_math does not exist in /proc/modules
ERROR: Module rtai_sem does not exist in /proc/modules
ERROR: Module rtai_fifos does not exist in /proc/modules
ERROR: Module rtai_sched does not exist in /proc/modules
ERROR: Module rtai_hal does not exist in /proc/modules

Please Log in or Create an account to join the conversation.

More
30 Nov 2013 17:27 #41247 by Glamplitude
Dear All

I never got to the bottom of the broken pipe problem, but I am no longer using Stepconf because my XYUV configuration is not compatible with it. I have now leapt head-first into hand-coding my configs.

Thank-you all!

Gareth

Please Log in or Create an account to join the conversation.

More
30 Nov 2013 18:16 #41248 by cncbasher
i'd guess that this is picking up the older version of stepconf rather than the version for 2.6

Please Log in or Create an account to join the conversation.

Time to create page: 0.091 seconds
Powered by Kunena Forum