Back
[13:28:16] <CIA-67> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/hal/images/softstart-scope.png: add image
[13:43:46] <CIA-67> EMC: 03bigjohnt 07v2_3_branch * 10emc2/docs/src/hal/images/softstart-scope.png: add image
[14:30:12] <CIA-67> EMC: 03bigjohnt 07v2_3_branch * 10emc2/docs/src/hal/hal-examples.lyx: add hal example for soft start
[14:31:21] <CIA-67> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/hal/hal-examples.lyx: add hal example for soft start
[17:11:29] <CIA-67> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/hal/tutorial.lyx: add info about exiting hal
[17:13:39] <CIA-67> EMC: 03bigjohnt 07v2_3_branch * 10emc2/docs/src/hal/tutorial.lyx: add info about exiting hal
[17:15:07] <CIA-67> EMC: 03bigjohnt 07TRUNK * 10emc2/src/hal/components/thc.comp: start of torch height comp
[17:52:37] <SWPadnos> hey jepler, did you ever use an Atmel-build AVR programmer under Linux?
[17:52:43] <SWPadnos> gah. Atmel-built
[17:53:00] <SWPadnos> like the AVRISP (serial) or the AVRISPII (USB)
[18:05:11] <jepler> SWPadnos: no, I've always used the simple parport ones, and later AVRs with bootloader support
[18:05:19] <SWPadnos> ok
[18:05:31] <SWPadnos> it looks like avrdude supports all the programmers I have anyway
[18:05:45] <SWPadnos> now to actually compile/assemble some code on Linux
[19:11:13] <CIA-67> EMC: 03jepler 07TRUNK * 10emc2/src/hal/components/thc.comp: fix compile error
[19:18:58] <BigJohnT> jepler: thanks for fixing that
[19:19:10] <BigJohnT> * BigJohnT wonders why it didn't error out for me
[19:21:53] <jepler> BigJohnT: not all versions of the C standard accept 'bool', but I guess the one you're testing on did
[19:22:09] <jepler> BigJohnT: (it can also depend on stuff like compiler flags, which in turn depends on kernel version and rt vs sim)
[19:22:27] <BigJohnT> ok, thanks
[19:24:56] <jepler> BigJohnT: a couple more notes -- Use "variable" when the state needs to be kept from one invocation of a function to the next. Otherwise, declare it in the function. abs_x_vel, abs_y_vel, p_error and d_error are examples of this. on the other hand, you're right to use variable for last_p_error, since you want to refer to a value set by an earlier invocation of _.
[19:25:55] <jepler> http://emergent.unpy.net/index.cgi-files/sandbox/thc-use-locals-not-variables-when-appropriate.patch
[19:26:33] <jepler> finally, for a "variable" or a local that is to hold a number that is not a whole number, use "double". This stores the number with greater precision. for pin and param, you're right to use "float".
[19:27:28] <jepler> varible double i_error; and so on
[19:41:48] <BigJohnT_> BigJohnT_ is now known as BigJohnT
[20:21:20] <BigJohnT> jepler: thanks for the help and tips