Is the attached what you are looking for? On Fri, May 12, 2017 at 1:14 PM, schooner30@btinternet < schoone...@btinternet.com> wrote:
> > On 12/05/17 17:56, Mike Cinquino wrote: > > /var/cache/apt/archives only has in it 1 directory called "partial" and > one file called "lock"? I am not sure where to find the package name? > > It is probably set to delete the packages after install, to save space, > not to worry > > > I attached the config sim folder. This is auto generated from the > Configuration Selector. > > It looks OK, you can check the contents against the repo to be sure > > What I need is the error output when the sim is launched and 'does not > work' > > > > > > On Fri, May 12, 2017 at 11:55 AM, schoone...@btinternet.com < > schoone...@btinternet.com> wrote: > >> >> On 12/05/17 16:30, Mike Cinquino wrote: >> >> The image I burned in relation to last message >> was: bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img >> >> >> Today I did: >> >> sudo apt-get update >> sudo apt-get dist-upgrade >> >> on the above system. >> >> I read the email string and am trying to figure out what other than that >> I would need to do. I do not see that he is getting the same error as I am. >> >> After doing the above I get the same result. >> >> I also tried: >> >> Downloaded file from: https://github.com/machi >> nekit/machinekit/blob/master/configs/sim/axis/xhc-hb04 >> >> The .hal files from the above link do not appear to be correct. They gave >> errors and I replaced with sim files generated through Configuration >> Selector. >> >> Same result. >> >> I also tried: >> >> user@INTEL-i7:/usr/src/machinekit/src/hal/utils$ realtime restart >> user@INTEL-i7:/usr/src/machinekit/src/hal/utils$ halcmd loadrt debounce >> user@INTEL-i7:/usr/src/machinekit/src/hal/utils$ halcmd show pexists >> debounce.0.0.in >> Exists >> user@INTEL-i7:/usr/src/machinekit/src/hal/utils$ halrun -U >> >> I am confused by this as the sequence of commands went in with no errors >> but nothing visible happened. Is the object of this to get the return >> "Exists" back? If so I got it back. >> >> Thank you for you patience. I am slowly learning I think.... well I am >> trying anyway :) >> >> >> That shows that you have a working version of halcmd :) >> >> The XHC is a horrible mess of tcl code, which checked for pins by parsing >> the output from halcmd show pin {pinname} >> >> The problem with that was that the output changed some years back from >> the original in Linuxcnc and it had not worked since. >> I replaced the parsing with a new function which just emits 'Exists' if >> the pin name is valid, simplifying everything and ensuring >> it works even if further formatting changes are made to halcmd. >> >> Changes on 7th February 2017 clobbered the fix and the halcmd part was >> fixed again on 6th March 2017. >> >> If you still get an error running the sim, you will need to attach it. >> I cannot be the same as you had previously, but there is still scope for >> problems :) >> >> Also look in /var/cache/apt/archives and see what the exact file name of >> the main machinekit package is, which will pinpoint exactly >> what you have installed >> If you updated today, it should probably be machinekit_0.1.1493733523-1mk. >> travis.master.git06e9c856~1jessie_armhf.deb >> >> >> >> >> >> >> On Fri, May 12, 2017 at 1:11 AM, schoone...@btinternet.com < >> schoone...@btinternet.com> wrote: >> >>> Please read the previous thread I linked >>> >>> You can't just burn AN updated image, from the ancient one you were >>> using. >>> >>> You need to use an image which has the halcmd pexists fix reinstated >>> after the multicore merge. >>> >>> >>> >>> On 12/05/2017 01:33, Mike Cinquino wrote: >>> >>> I burned an updated image. Looks like I made some progress. It looks >>> like it found it. I get the following error. >>> >>> Print file information: >>> RUN_IN_PLACE=no >>> LINUXCNC_DIR= >>> LINUXCNC_BIN_DIR=/usr/bin >>> LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc >>> LINUXCNC_SCRIPT_DIR= >>> LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc >>> LINUXCNC_CONFIG_DIR= >>> LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs >>> INIVAR=/usr/libexec/linuxcnc/inivar >>> HALCMD=halcmd >>> LINUXCNC_EMCSH=/usr/bin/wish8.6 >>> MACHINEKIT - 0.1 >>> Machine configuration directory is '/home/machinekit/machinekit/c >>> onfigs/sim.axis.xhc-hb04-1' >>> Machine configuration file is 'xhc-hb04-layout2.ini' >>> INIFILE=/home/machinekit/machinekit/configs/sim.axis.xhc-hb0 >>> 4-1/xhc-hb04-layout2.ini >>> PARAMETER_FILE=sim-9axis.var >>> TASK=milltask >>> HALUI=halui >>> DISPLAY=axis >>> Starting Machinekit... >>> Starting Machinekit server program: linuxcncsvr >>> Loading Real Time OS, RTAPI, and HAL_LIB modules >>> Starting Machinekit IO program: io >>> io started >>> halcmd loadusr io started >>> Starting HAL User Interface program: halui >>> Shutting down and cleaning up Machinekit... >>> Killing task linuxcncsvr, PID=5478 >>> xhc-hb04: waiting for XHC-HB04 device >>> xhc-hb04: found XHC-HB04 device >>> xhc-hb04: connection lost, cleaning up >>> Removing HAL_LIB, RTAPI, and Real Time OS modules >>> Removing NML shared memory segments >>> Cleanup done >>> >>> Debug file information: >>> Unknown 'show' type 'pexists' >>> while executing >>> "hal show pexists xhc-hb04.button-goto-zero" >>> ("eval" body line 1) >>> invoked from within >>> "eval hal show $args" >>> (procedure "show" line 1) >>> invoked from within >>> "show pexists $name" >>> (procedure "pin_exists" line 2) >>> invoked from within >>> "pin_exists $fullbname" >>> (procedure "connect_pins" line 24) >>> invoked from within >>> "connect_pins " >>> (file "xhc-hb04.tcl" line 400) >>> invoked from within >>> "source $filename" >>> invoked from within >>> "set result [source $filename]" >>> (file "/usr/bin/haltcl" line 55) >>> libgcc_s.so.1 must be installed for pthread_cancel to work >>> /usr/bin/linuxcnc: line 750: 5547 Aborted haltcl -i >>> "$INIFILE" $CFGFILE >>> 5478 >>> PID TTY STAT TIME COMMAND >>> Stopping realtime threads >>> Unloading hal components >>> libusb: error [do_close] Device handle closed while transfer was still >>> being processed, but the device is still connected as far as we know >>> libusb: warning [do_close] A cancellation for an in-flight transfer >>> hasn't completed but closing the device handle >>> *** Error in `xhc-hb04': free(): corrupted unsorted chunks: 0x0002d520 >>> *** >>> >>> On Thu, May 11, 2017 at 10:21 AM, schoone...@btinternet.com < >>> schoone...@btinternet.com> wrote: >>> >>>> >>>> On 11/05/17 15:06, Mike Cinquino wrote: >>>> >>>> Thank you. That may be the problem as I am using "linuxcnc" at the >>>> command prompt to launch. This is an older image I am using. >>>> It seemed to me that "machinekit" to launch did not work. I will have >>>> to check again. >>>> >>>> >>>> If it is that old, the XHC-HB04 is probably broken, I made the commit >>>> to provide a symlink of 'machinekit' in 34c00e0 >>>> <https://github.com/machinekit/machinekit/commit/34c00e082c6446dfbc541de6163a4382e8473dfe> >>>> on 13 Mar 2015 >>>> >>>> You need a recent image, I fixed XHC in commit 0d3f6b4 >>>> <https://github.com/machinekit/machinekit/commit/0d3f6b4d3c5aa89f1b75203be1efd4417a92182e> >>>> on >>>> 22 Aug 2016, so the image needs to be after that. >>>> >>>> >>>> On Thursday, May 11, 2017 at 9:49:38 AM UTC-4, Schooner wrote: >>>>> >>>>> >>>>> On 11/05/17 14:19, Mike Cinquino wrote: >>>>> >>>>> Hello, >>>>> >>>>> I am attempting to use a USB hb04 pendant. This is the hard wired USB >>>>> version 18 keys. I can't find any other model info or part numbers for >>>>> this >>>>> unit. >>>>> >>>>> I have verified that the pendant is being seen by using the lsusb >>>>> command and finding the expected id value. >>>>> >>>>> To start I am trying to get it to work in sim by using the prepackaged >>>>> sim configuration unmodified. I select it from the tree after launching >>>>> linuxcnc. >>>>> >>>>> I am running linuxcnc version 2.7.0 pre.... (I am going from memory on >>>>> this.) >>>>> >>>>> >>>>> This is Machinekit not Linuxcnc, make sure you are running the correct >>>>> system or there is no point going into this >>>>> >>>>> The sim works fine as per this thread, https://groups.google.com/foru >>>>> m/#!msg/machinekit/8mMHqZ_Zb80/onJM1rvsBAAJ;context-place=fo >>>>> rum/machinekit >>>>> >>>>> >>>>> I am using the Xylotex BeagleCNC BBB_DB25/26 cape. (Not that it >>>>> matters as I am working in sim) >>>>> >>>>> After I select configuration and LCNC tries to load.. I see it going >>>>> through multiple ports and it ends up not finding it. >>>>> >>>>> I followed the instructions on the read me file and added the >>>>> recommend .rules file to udev directory. Still no luck. >>>>> >>>>> Not sure what to try next. >>>>> >>>>> Any help would be greatly appreciated. >>>>> >>>>> Thanks, >>>>> Mike >>>>> -- >>>>> 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 machinekit+...@googlegroups.com. >>>>> 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 machinekit+unsubscr...@googlegroups.com. >>>> 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 a topic in the >>>> Google Groups "Machinekit" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>>> pic/machinekit/OvxRsCF3auI/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> machinekit+unsubscr...@googlegroups.com. >>>> 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 machinekit+unsubscr...@googlegroups.com. >>> 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 a topic in the >>> Google Groups "Machinekit" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>> pic/machinekit/OvxRsCF3auI/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> machinekit+unsubscr...@googlegroups.com. >>> 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 machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Errors
Description: Binary data
