#emc-devel | Logs for 2006-08-14

[12:58:01] <jepler> Your SourceForge.net password has expired - You must now choose a new password before logging into the site.
[12:58:04] <jepler> offs
[12:58:18] <jepler> Please note: passwords should contain only letters and numbers. Inclusion of other characters in your password may result in inability to access some SourceForge.net systems.
[12:58:22] <jepler> offs
[12:59:19] <jepler> 500 - Internal Server Error
[12:59:20] <jepler> offs
[13:13:45] <alex_joni> :D
[13:13:53] <alex_joni> hi jeff
[13:29:22] <jepler> hi alex
[13:31:51] <alex_joni> what's up?
[13:32:42] <alex_joni> * alex_joni wonders where chris might be ;)
[13:38:58] <jepler> I hear he's taking some vacation
[13:46:26] <alex_joni> oh.. that's nice
[20:45:37] <jepler> I want AXIS to be able to create some HAL pins which can then be connected -- specifically, some pins for the active axis, so that a physical jogwheel can move the axis selected in the AXIS GUI
[20:45:57] <jepler> right now I do this by creating some parameters in a .hal file, and 'setp'ing them when an axis is selected, but I feel I should do this with HAL pins instead
[20:46:09] <jepler> the problem is that the pins will (obviously) be created by AXIS, but that is executed last after all the .hal files
[20:46:14] <jepler> so what should I do?
[21:42:45] <SWPadnos> jepler, can you have axis execute a short hal scipt after it's initialized?
[21:43:05] <SWPadnos> you can even pipe the commands into halcmd from axis
[22:05:14] <jepler> SWPadnos: yeah, that's what I do now (I run halcmd to change the signal values)
[22:05:19] <jepler> SWPadnos: I was hoping for something a little more elegant
[22:05:39] <SWPadnos> what I meant was, use halcmd to set up the signals after the axis pins have been created
[22:05:44] <SWPadnos> then change pins
[22:05:50] <SWPadnos> err - pin values
[22:06:48] <jepler> so basically have AXIS run one user-defined HAL file?
[22:06:53] <SWPadnos> yep
[22:07:04] <SWPadnos> or a hal file that's part of axis itself, in the pipe scenario
[22:07:21] <jepler> I suppose that's better than what I have now
[22:07:55] <SWPadnos> at least it would be "normal" signals - connected to pins at both ends
[22:08:14] <jepler> yeah
[22:09:01] <SWPadnos> I think even the waitforpin function has a race, unless the runscript could try all the HAL files, then run the display program without waiting for them to finish (which has problems of its own)
[22:13:33] <jepler> hm, I'm not sure what you mean
[22:13:52] <SWPadnos> sorry - I may not know either :)
[22:13:59] <jepler> if you have one partition on a disk, and you type 'df', it deletes it.
[22:14:05] <jepler> I mean, if you type 'df' into 'fdisk'
[22:14:36] <SWPadnos> is that a lament, or preventitive wisdom?
[22:14:52] <jepler> I just did it on a system without anything on the disk
[22:14:54] <jepler> so, no big deal
[22:15:01] <SWPadnos> bummer - almost
[22:15:03] <jepler> so .. funny
[22:15:06] <SWPadnos> delete / force?
[22:15:19] <jepler> "d" is delete
[22:15:27] <jepler> I don't think it even looks at the letter 'f'
[22:15:45] <SWPadnos> I'd think there would be a confirmation step in there