Back
[00:13:29] <Guest179> jmkasunich: if you get a chance.. Do you think I need to worry about placement?
[00:13:30] <Guest179> http://www.cnczone.com/forums/showpost.php?p=486358&postcount=27
[00:13:35] <Guest179> Guest179 is now known as skunkworks
[00:13:57] <skunkworks> http://www.electronicsam.com/images/KandT/servostart/boardfinal4.PNG
[01:04:27] <jmkasunich> skunkworks: you always have to worry about placement
[01:04:54] <jmkasunich> I agree with the poster that you need to design the critical traces first, then fit the other stuff around them
[01:05:38] <jmkasunich> I'm not going to try to analyze your board in detail
[01:06:31] <jmkasunich> given the space you have and the number of components (and their size), I'm not sure if I could do any better
[04:06:31] <skunkworks> jmkasunich: thanks. I think I just am going to give it a go as is. What the hell ;)
[04:08:11] <CIA-35> EMC: 03cmorley 07TRUNK * 10emc2/src/hal/drivers/opto_ac5.c: fix for invert pins defaulting as true. Also meant outputs to hardware were being writteninverted. Change to ensure outputs are off when driver closes
[11:30:38] <CIA-35> EMC: 03jepler 07TRUNK * 10emc2/src/libnml/posemath/sincos.c: fixes a segfault reported by Nicolas HENRY on Debian Lenny systems
[11:30:56] <CIA-35> EMC: 03jepler 07v2_2_branch * 10emc2/src/libnml/posemath/sincos.c: from TRUNK: fixes a segfault reported by Nicolas HENRY on Debian Lenny systems
[14:32:29] <BigJohnT> is there a list of error messages anywhere?
[14:38:33] <jepler> no. the error messages are scattered through the program at whatever spot the error is detected
[14:42:26] <BigJohnT> is there any keyword that I could grep for that might find them all?
[14:44:08] <jepler> no, but there are a few terms that will lead you to most of the messages
[14:44:17] <BigJohnT> ok
[14:44:28] <jepler> RTAPI_MSG_ERR (errors produced by realtime components and drivers)
[14:45:12] <jepler> rcs_print_error (errors produced by motion and task mostly)
[14:46:11] <jepler> ERM SRF ERS ERP CHKS CHKF CHK CHP (errors produced by the gcode interpreter)
[14:46:32] <jepler> nf_dialog (errors produced by the axis gui)
[14:46:58] <jepler> the second item for gcode interpreter error should be ERF, not SRF.
[14:47:22] <jepler> I think that a document to exhaustive list all the possible errors is probably misguided, because it will almost always be out of date
[14:51:03] <BigJohnT> I was thinking of some of the ones that are most confusing to a newbee
[14:51:09] <BigJohnT> thanks
[14:51:21] <BigJohnT> I have to go to a plant now
[14:51:34] <jepler> see you later
[19:21:18] <alex_joni> BigJohnT: watering job?
[19:21:20] <alex_joni> :P
[19:34:10] <alex_joni> jepler: how's it looking for this weekend?
[19:34:50] <jepler> alex_joni: I think I'll have the time as long as we don't decide to stick more bug fixes in at the last minute
[19:35:22] <jepler> I have to remember to downgrade my amd64 machine to the older kernel so I don't make packages with an ABI problem
[19:35:56] <alex_joni> right
[19:36:12] <alex_joni> no side-effects from upgrading the rtai so far
[19:36:23] <alex_joni> * alex_joni is happy that worked out
[19:36:37] <jepler> good
[20:08:55] <BigJohnT> Hi alex_joni
