cradek: Anyway, I posted 4 lines that were something like (1) Parallel: Parallel port not found(?) (2) Parallel: Continuing anyway (3) PPMC: No USC/UPC for (something, controller?) (4) PPMC: shutting down
Oh wait, I remember. (3) PPMC: No USC/UPC for DAC at port 0, 0 (or something like that) John's BP2 has the optional spindle DAC.
cradek: John says hi.
cradek: We'll be at lunch a bit, then errands, then back after while. Any advice appreciated. Thanks! (And then I'd like to talk more later about your travel plans).
cradek: there is access on each axis to crank them off of the limits... I think that will work for us. ;)
KimK, are there two USC/UPC boards on that system?
oh your ppmc still doesn't work? ugh.
it is starting to seem like something must be wrong in my conversion to use the new hal_parport_xxx APIs but I haven't spotted it yet
KimK: what is the loadrt line like for ppmc? can you put the exact kernel messages online (pastebin or whatever)?
skunkworks_: great - that is definitely safest if it's accessible
that is how you did it with the old control... Never really had an issue.
soft limits should take care of 99% of the issues/
yeah it's not like you regularly hit limit switches anyway
I just tried 2.4.1 on John's BP2 again, still failing, I suspect these are the relevant lines (he has the optional spindle DAC):
[ 1817.879038] PARPORT: linux parport parport0 does not support mode 4.
[ 1817.879042] PARPORT: continuing anyway.
[ 1817.882883] PPMC: ERROR: no USC/UPC for extra dac at bus 0, slot 0
[ 1817.882893] PPMC: shutting down
Any advice appreciated as always. Thanks!
KimK, post ^
does anyone know if he has two cards?
I can imagine the enumeration order being different
that's one reason I was interested in the loadrt line
jepler: maybe this fixes the flakiness: http://www.panix.com/~dgarrett/stuff/0001-sim_ulapi.c-rtapi_init-should-return-a-unique-identi.patch
dgarr: that means each rtapi_init call in a process will return the same unique ID, but suppose you start process 111 which creates a component, and then process 112 which creates a component
oops -- whats a good way to make it unique then?
and now that you've rung that bell, I'm pretty sure 'halcmd unload' assumes the userspace component ID is also its process ID for killing them..
(sorry if 'bzzt' read as being rude, it wasn't supposed to)
hmm, looks like a component has a 'pid' field separate from the 'comp_id' field
so the 'halcmd unload' problem isn't
it looks like under rtai IDs are assigned from a pool of small positive integers because all the rtapi modules together maintain the module_array
under ulapi, userspace components get their PID for their ID and realtime components get 32768+small-number, since on typical unix systems PIDs over 32767 are never used
what about an id based on unix time or something
under rtai, the segfault problem is probably due to any call to rtapi_exit unmapping the rtapi shared memory areas
I haven't been paying enough attention. what problem are you trying to solve?
cradek: dgarr wants to be able to 'package require Hal' in the Tcl part of AXIS, for his own purposes
problem statement: http://www.panix.com/~dgarrett/stuff/q1.txt
(I think to be able to run 'halcmd' commands without a pipe)
and jepler pointed out problem (09:05:54) jepler: dgarr: git show 8f634b47
hal forbids this, and it does so because of various problems that allowing it lead to. In sim, all hal components in the same process get the same hal component id. In rtai and sim both, various weirdness can be provoked, usually when one hal_exit occurs before all other use of hal is done
Hi all, back after lunch and assorted errands. Thanks jthornton for posting those four error lines. Sorry, that's all I can get for you right now as the machine is in use. (Cleaning up opposite sides of castings with a 4" facemill before grinding, and doing nicely.) I should be able to get you the full error report in 2.5 hours, maybe?
np I just remembered them and was at the house for a few minutes
SWPadnos: Only one Pico-Systems Universal Stepper Controller (USC) in John's BP2, and it has the optional spindle DAC.
All running nicely under 2.3.5
Oops, I forgot that Synaptic gave an error on the upgrade. It said emc2 upgraded to 2.4.1, but emc2-dev was still at 2.3.5: http://imagebin.ca/view/MrK8cmn.html
Oh, I guess it's OK on the second try, all is OK now. I'll try 2.4.1 and post the errors.
pyvcp text button <disable_pin> 1, True, TRUE all work but true does not. Is that something with python or the pyvcp_widgets.py?
Widget button, Property disable_pin
NameError: name 'true' is not defined
OK, here are the EMC2 error window errors, and the tool table: http://www.pastebin.ca/1875693
Any advice appreciated as always. I'll be gone for several hours, but please post.