#emc-devel | Logs for 2008-09-16

Back
[00:05:27] <Lerman> Why not write to disk whenever it's changed?
[00:05:52] <Lerman> jmkasunich: are you here?
[00:06:46] <jmkasunich> yes
[00:07:09] <Lerman> Why not write to disk whenever it's changed?
[00:07:40] <Lerman> After all, goo tables aren't changed that often.
[00:07:41] <jmkasunich> cause maybe a program wants to make a change that only lasts for the duration of the program?
[00:08:09] <jmkasunich> I have an application where I'd "change" it every run
[00:08:57] <Lerman> Is that an alternate way of doing your measure then adjust before final cut?
[00:09:15] <jmkasunich> yes
[00:09:26] <jmkasunich> there are three ways to do it:
[00:09:49] <jmkasunich> 1) "touch off" after the measurement: pro - the DRO is accurate, con - all tools are affected
[00:10:20] <jmkasunich> 2) correct the cut, not the offset: pro - fairly easy, con - DRO reads funny
[00:10:55] <jmkasunich> 3) correct the tool offset: pro: DRO is accurate, only one tool affected, con: don't think it can be done today
[00:11:29] <Lerman> 4) like 1, except "un touch off" after the cut.
[00:11:50] <jmkasunich> true, dunno how difficult that would be
[00:12:40] <Lerman> The offsets *are* available as vars, so you should be able to record the present offset, set a new offset, do the cut, and then change the offset back.
[00:13:30] <Lerman> I had the impression that you were talking about a lathe for this. Is that true?
[00:13:41] <jmkasunich> yes, this is lathe work
[00:14:28] <Lerman> Can't you do tool diameter compensation on a lathe where "diameter" is actually length?
[00:14:46] <jmkasunich> I don't understand that question
[00:14:54] <jmkasunich> EMC already has X and Z comp for lathe tools
[00:14:59] <jmkasunich> plus nose radius
[00:15:56] <Lerman> On a mill, we specify stay to the right side of the path and the tool diameter is .125 (or the tool diameter correction is .001). Can we do that on a lathe?
[00:16:14] <jmkasunich> yes
[00:16:22] <jmkasunich> I'm not sure of all the details for lathe
[00:16:24] <Lerman> Isn't that what you want?
[00:16:38] <jmkasunich> no
[00:17:12] <Lerman> Can it be mapped to that?
[00:17:17] <jmkasunich> this isn't about compensating for a known tool length, it is about correcting that last 0.0003 when the length (or radius, or whatever) in the table isn't quite right
[00:17:35] <jmkasunich> whether that is because of spring, temperature change, whatever
[00:18:46] <jmkasunich> so I need to be able to cut, measure, enter measurement, and make a final cut
[00:18:51] <Lerman> I understand that the reason is different. But if you specified the "diameter" as .000 for the initial cuts and then changed it to be .0047 for the final cut, would that do the trick?
[00:19:09] <jmkasunich> sure
[00:19:27] <jmkasunich> probably wouldn't be using the diameter term, more likely the X term
[00:19:44] <jmkasunich> and the initial value would not be zero
[00:20:25] <Lerman> You don't have a turret, gang, or other automatic way to change tools, do you?
[00:21:15] <Lerman> If you had a gang lathe, you could put a probe in one station and do the measurement automatically?
[00:21:34] <jmkasunich> no
[00:21:52] <jmkasunich> I have a QC toolpost, but I don't have a probe
[00:21:59] <Lerman> How about mounting a probe on the back of the cross slide so that you could do it automatically.
[00:22:02] <jmkasunich> nor is the machine accurate enough to measure
[00:22:21] <jmkasunich> it is impossible to measure a diameter with a probe on the machine
[00:22:45] <jmkasunich> because you have to approach from both sides to measure diameter, so lash comes into play
[00:23:19] <jmkasunich> plus, the two measurements are made about 1" apart in X (diameter of part plus diameter of probe ball), so X screw errors come into play as well
[00:23:38] <Lerman> You would have to calibrate the probe. Of course, the tolerances you seem to be talking about seem to be pretty tight.
[00:23:55] <jmkasunich> I'm trying to do work to tenths, on a lathe that can only do thousandths "open loop"
[00:24:30] <jmkasunich> I'm basically trying to close the loop by getting very close to final size, measureing with better instruments, and then doing the final cut without changing anything else
[00:24:36] <Lerman> Do you have a set of gage blocks to calibrate your micrometer?
[00:24:41] <jmkasunich> yes
[00:24:56] <jmkasunich> not needed in this case tho, since I'm making a part to fit a bore
[00:25:11] <Lerman> Is this all for your spindle?
[00:25:19] <jmkasunich> as long as I use the same mic to measure the part and the bore, absolute accuracy not critical
[00:25:20] <jmkasunich> yes
[00:25:30] <jmkasunich> collet back diameter goes into spindle bore
[00:25:56] <jmkasunich> goal is to have something like 0.0002 to 0.0005 clearance
[00:26:10] <jmkasunich> I'd probably be happy to have 0.0001 to 0.0010
[00:26:30] <Lerman> Someone on CNCzone had a nice article about tuning ballscrews to fit bearings. Final few tenths done with emery cloth.
[00:26:52] <jmkasunich> yep - I'll probably be doing that - I did it on the first one I made
[00:27:18] <Lerman> How many do you plan on making?
[00:27:18] <jmkasunich> but uncorrected, my lathe tends to give me +/- 0.001 or even +/- 0.0015
[00:27:22] <jmkasunich> 16
[00:27:45] <jmkasunich> if I need to leave allowance for sanding, I need to make my target at least 0.002 large
[00:27:50] <jmkasunich> that is a lot of emery
[00:28:02] <jmkasunich> so anything I can do to tighten it up is a win
[00:28:13] <Lerman> What is the rough diameter>
[00:28:19] <Lerman> ?
[00:28:34] <jmkasunich> 0.875ish
[00:29:16] <jmkasunich> the first spindle bore is 0.8805 as well as I can measure, but I think for the rest I'm gonna aim for a 0.8750 +0.0005 -0.0000 bore
[00:29:59] <jmkasunich> since the bores are _very_ to cut and rather hard to measure, I'll probably make them first, and make the collets to fit
[00:30:29] <jmkasunich> so for the bores, I'll just run the program
[00:30:33] <Lerman> Are you reaming the bores or boring them?
[00:30:44] <Lerman> Or grinding them?
[00:30:46] <jmkasunich> just boring at the moment, might do some grinding or lapping
[00:31:02] <jmkasunich> doesn't help that the spindles are case hardened
[00:31:45] <jmkasunich> the first one I did was 0.8805 in the main part of the bore, but 0.879ish at the front, where the case intersects the bore
[00:32:06] <jmkasunich> I'll probably revise the machining so that front part is 0.885 or so, puts it "in the air"
[00:32:55] <jmkasunich> the design is evolving over time ;-)
[00:33:21] <Lerman> On another subject, I'm thinking of using HAL to run the thermostats in my house.
[00:33:46] <jmkasunich> that seems like overkill
[00:33:56] <Lerman> I have ten zones of hot water baseboard heat. Zone valves occasionally stick, thermostats go wonky.
[00:34:39] <Lerman> After a powerfail, the thermostats lose their settings. (The batteries are always dead.)
[00:34:57] <jmkasunich> after a power fail, PCs tend to reboot
[00:35:38] <Lerman> But not notebooks of PCs on good UPS's. And with the right scripts they tend to reboot OK.
[00:36:01] <jmkasunich> yeah, I suppose if you auto-restart the HAL stuff it wouldn't be bad
[00:36:28] <jmkasunich> if you get freezing weather, I'd have a backup t-stat set at about 50F anyway
[00:36:30] <Lerman> I'd like to be able to know that a zone valve was stuck open without having to go around to the rooms that are never used and check the temperatures.
[00:37:37] <jmkasunich> you could certainly do that
[00:37:50] <Lerman> So, I'd have ten temperature sensors, ten zone valves relays, ten sensors to tell if a valve is open (simple bimetallic sensors at 90 degrees or so.
[00:38:23] <Lerman> Then I could change the settings using a slider in pyvcp.
[00:38:29] <jmkasunich> aren't the bimetal sensors redundant?
[00:38:32] <Lerman> And monitor things the same way.
[00:38:40] <jmkasunich> hotter than commanded = valve stuck open
[00:39:22] <Lerman> Yes they are. True. Or it's a warm day, or the room next door is set higher and air is flowing from one to the other.
[00:39:43] <jmkasunich> "lots hotter than commanded" ;-)
[00:40:04] <Lerman> You might be right.
[00:40:17] <Lerman> Did you see the discussion about real time serial ports?
[00:40:40] <jmkasunich> sort of
[00:40:55] <jmkasunich> didn't make much sense of it, and didn't really care
[00:41:21] <Lerman> From a practical standpoint a hal driver for that would be pretty easy. Except that there are a few different chips out there.
[00:41:48] <jmkasunich> the guy never mentioned what he wanted to talk to
[00:43:49] <Lerman> That is a bit of a problem. I'm interested because I'll need some sort of data acq system for my thermostats.
[00:44:12] <jmkasunich> getting temperature into HAL you mean?
[00:44:15] <Lerman> That has to talk to HAL.
[00:44:38] <jmkasunich> do you have existing sensors of some sort, with A/D converters, and you need to talk to it serially?
[00:44:44] <Lerman> Yup. I assume that I can do all of that in user space.
[00:44:56] <jmkasunich> certainly
[00:44:57] <Lerman> No -- hardware has yet to be sellected.
[00:45:24] <jmkasunich> given your several-second timing requirements, you can probably do everything in user space
[00:45:54] <Lerman> I'll probably try to buy some kind of commercial beast. It's not clear yet what to do for temperature sensors.
[00:46:13] <jmkasunich> wiring will be the nasty part
[00:46:19] <jmkasunich> if you have lots of rooms, thats lots of wire
[00:46:28] <jmkasunich> unless you go crazy and do something wireless
[00:46:49] <Lerman> I already have regular thermostats in all the rooms. So, I could replace them with something else.
[00:47:15] <Lerman> One wire sensors might be neat -- although they aren't real precise, they should be good enough.
[00:47:17] <jmkasunich> regular thermostats with minimum 2 conductor cable back to basement or wherever the furnace is?
[00:47:51] <Lerman> Yup to the basement. -- Five foot high ceilings 200 years old. Think dungeon.
[00:48:30] <Lerman> New wiring is possible, though.
[00:48:39] <jmkasunich> I don't think HAL has been used to control a dungeon before
[00:48:49] <jmkasunich> how many conductors in the thermostat cables?
[00:49:07] <Lerman> Platinum resistance temperature sensors are accurate and cheap. But they require four wires to do it right and I have only two.
[00:49:20] <jmkasunich> I think my tstat has 4 because it can control air conditioning, fan, and heat
[00:49:43] <Lerman> That's pretty common.
[00:50:07] <jmkasunich> two wires means you need to send power and signal on the same pair
[00:50:10] <Lerman> For the upstairs, I can drop wires from the attic into the walls in most of the rooms.
[00:50:20] <jmkasunich> do you like electronics?
[00:50:42] <Lerman> The so called one-wire sensors are actually two wire. They should be fine for that.
[00:50:59] <jmkasunich> yeah, one-wire is marketing speak
[00:51:01] <Lerman> I do electronics. But I'd rather buy than make.
[00:51:14] <jmkasunich> they don't count ground - dumbasses
[00:51:38] <Lerman> My twin brother is a veterinarian. He does electronics and does most of our electronic layout.
[00:51:47] <Lerman> (for prototypes)
[00:52:05] <jmkasunich> the one wire stuff will involve "make"
[00:52:18] <jmkasunich> they are chips, not "units" that are ready to mount and connect
[00:52:32] <jmkasunich> at a minimum you'd need some bypass caps, terminal blocks, etc
[00:52:36] <Lerman> My current long term (other) project is to put together a laser interferometer. I just fired up the laser for the first time, last week.
[00:53:22] <Lerman> And a board to put them on. And a driver. And I don't think you can put a dozen sensors in parallel when you have lots of long wires going to them without having rise time issues.
[00:54:29] <Lerman> I'm thinking of using a serial pluto board for the laser interferometer electronics. Hey, I could use the same board to interface to my thermostats.
[00:54:37] <jmkasunich> heh
[00:54:56] <Lerman> It has lots of I/O. I could use one for each of the one-wire chips. Implement the protocol in hardware.
[00:55:15] <jmkasunich> sounds like a lot of programming and/or hardware
[00:55:22] <jmkasunich> and you still need to build the sensor units
[00:55:27] <Lerman> (A job for someone with lots more time than money. Probably also more time than brains.)
[00:56:03] <Lerman> I may take a look on the web for one-wire thermostats.
[00:56:31] <jmkasunich> you might also consider 4-20mA instead of digital
[00:56:45] <Lerman> My big budget items this year is probably going to be a change over from oil to natural gas for heat.
[00:56:47] <jmkasunich> you can filter the snot out of it on your central board, less sensitive to electrical noise
[00:57:28] <Lerman> I hadn't though of 4-20ma, but I bet I can find something that uses platinum resistance sensors that would do the job.
[00:58:06] <jmkasunich> google finds lots of 4-20mA temp sensors, but the prices are ridiculous
[00:59:02] <Lerman> Hell, even plain thermistors are pretty good. If I don't mind making little boards, a pic a thermistor, and a little hardware should give me a 4-20ma homebrew sensor.
[00:59:48] <jmkasunich> what is the pic for?
[00:59:57] <jmkasunich> just put the NTC on the end of the two wires
[01:00:03] <Lerman> The pic could linearize the sensor.
[01:00:09] <jmkasunich> bias circuit and A/D at the central location
[01:00:47] <Lerman> That should work. I've used some 10K 1% thermistors that are pretty cheap.
[01:01:16] <jmkasunich> nice thing about thermistors is they usually have a relatlvely rapid resistance change per degree
[01:01:30] <jmkasunich> compared to RTDs or (shudder) thermocouples
[01:01:43] <jmkasunich> not so great for accuracy over a large range, but that isn't a criteria here
[01:01:51] <jmkasunich> 40 to 100 F is more than enough
[01:02:25] <Lerman> The ones we are using are good to a fraction of a degree over that range. We use them for temperature correction in our anesthesia machines.
[01:02:28] <jmkasunich> if you get +/- 1 degree around 70F, and +/- 3-4 degrees over the range, that should be good enough
[01:02:44] <jmkasunich> there you go - you already have a source
[01:02:51] <Lerman> And at 10K ohms, serial resistance from the wires won't be a problem.
[01:03:09] <jmkasunich> are the ones you use potted or otherwise "ready to mount"? or would they still need a rudimentary board?
[01:03:15] <Lerman> I think Digikey has them. Made by GE, I think.
[01:03:45] <jmkasunich> if I was doing something like that project, I'd put one sensor outdoors too
[01:03:48] <Lerman> They have an epoxy coating. Solder them to the wires. Heat shrink the connections.
[01:04:19] <jmkasunich> are the existing thermostats passive - just bimetal contacts?
[01:04:23] <Lerman> Sure, extras are free.
[01:05:07] <Lerman> Some are passive. Others are computerized, multi-setpoints, days of the week, etc. A PITA to program.
[01:05:24] <jmkasunich> mount the NTC inside the thermostat housing (for appearance sake) and wire it across the contacts (if passive)
[01:05:25] <Lerman> I may have to add a day of the week component to HAL.
[01:06:11] <Lerman> I can even use PID control.
[01:06:53] <Lerman> I love it when a plan comes together.
[01:07:16] <Lerman> It's past my bedtime. Thanks for your ideas. I'll see you later.
[01:07:20] <jmkasunich> goodnight
[13:42:43] <alex_joni> could it be a sign error on the hostmot2 issue?
[13:43:10] <alex_joni> TP commanding a move in a certain direction, hm2-stepgen moving (or reporting) the other direction?
[13:43:47] <SWPadnos> they eventually match up, so I wouldn't think so
[13:44:33] <alex_joni> match up? why?
[13:44:43] <alex_joni> I would expect it to wind up and run away
[13:44:46] <SWPadnos> position-cmd -0.502
[13:44:48] <SWPadnos> position-fb -0.502
[13:45:02] <alex_joni> what if motion commanded 0.502 ?
[13:45:11] <SWPadnos> ah, ok
[13:45:23] <SWPadnos> could be
[13:46:19] <SWPadnos> I wonder why that wouldn't happen for Seb
[13:47:02] <alex_joni> he commands things by hand from HAL
[13:47:12] <alex_joni> he said he's not running the driver from emc2
[13:47:55] <SWPadnos> ?
[13:48:05] <SWPadnos> ah - now I get it ;)
[13:48:24] <alex_joni> the only thing I can think of atm :)
[13:49:18] <SWPadnos> if seb types "setp <blah>position-cmd 1, and the stepgen goes to -1, you'd think he'd notice :)
[13:49:55] <SWPadnos> I don't know if the position-cmd and position-fb are the actual pins or internals, but if they're actual pins, then position-cmd is what motion is asking for
[13:50:24] <alex_joni> yeah, my scenario only works if they're internals _and_ don't match the pins
[13:55:49] <alex_joni> sounds like the classic runaway scenario to me :)
[13:56:40] <SWPadnos> hmmm. so here's an interesting question (to me anyway)
[13:57:00] <SWPadnos> what happens if you have a position file and you use something like the hostmot2 stepgens?
[13:57:40] <SWPadnos> I mean, theoretically, position_file tells EMC where the machine is, but then again, in machine off state it updates command position from motor feedback
[13:58:19] <SWPadnos> and what happens to the motor-pos-cmd pins based on position.txt?
[15:37:15] <alex_joni> SWPadnos: I think that's internal to motion
[15:37:36] <alex_joni> but even if it changes, it gets changed while machine is not on yet,
[15:38:05] <SWPadnos> it's got to be an internal joint offset I guess
[15:38:13] <SWPadnos> since feedback starts out at 0
[15:38:15] <alex_joni> I think it is
[15:38:27] <SWPadnos> until we get absolute encoder support
[15:38:43] <alex_joni> and?
[15:38:51] <alex_joni> you don't actually use both :P
[15:38:58] <SWPadnos> actually, absolutes may work already, as long as there's some startup code to read them :)
[15:39:01] <SWPadnos> sure
[15:39:02] <alex_joni> position remembering and absolute encoders :)
[15:39:32] <SWPadnos> the general solution for absolutes is to allow machine zero to be offset from encoder zero, but I don't know if that's common
[15:39:46] <SWPadnos> or necessart
[15:39:48] <SWPadnos> y
[15:40:52] <alex_joni> yeah, homing sure needs a bit of work
[15:41:14] <alex_joni> you need to startup already homed
[15:41:23] <alex_joni> bll.
[15:41:24] <SWPadnos> right
[15:41:25] <alex_joni> bbl even
[15:41:29] <SWPadnos> heh - see you
[15:44:13] <alex_joni> back
[15:44:23] <alex_joni> was a short l
[15:54:41] <alex_joni> jepler: did you check that translation update? the diff shows some odd things
[15:54:54] <alex_joni> (might be my email client, that's why I'm asking..)
[15:55:22] <alex_joni> -msgstr "Selezione velocit. movimento angolare"
[15:55:23] <alex_joni> +msgstr "Selezione velocit. movimento angolare"
[15:55:46] <alex_joni> the first one looked ok, the second one looks like it has a wrong char in it
[15:56:22] <alex_joni> capital A with ~ ontop for the second, vs. `a for the first
[16:11:31] <jepler> alex_joni: no, I didn't look at it. I don't know Italian, after all.
[16:11:54] <SWPadnos> speed selection for angular motion, of course! :)
[16:12:11] <alex_joni> the new translations seem nice, but charset seems a bit borked
[16:24:46] <jepler> -"Content-Type: text/plain; charset=ISO-8859-1\n"
[16:24:49] <jepler> +"Content-Type: text/plain; charset=UTF-8\n"
[16:25:05] <alex_joni> aha, sounds better then
[16:25:11] <alex_joni> and it probably is my mail reader
[16:25:15] <jepler> the character set changed, so the diff will be nonsensical because it has one encoding in "-" lines, another encoding on "+" lines
[16:25:18] <alex_joni> (and browser)
[16:26:47] <alex_joni> yup.. with UTF-8 it looks ok.. sorry to have bothered you for nothing :/
[16:29:06] <jepler> that's OK
[18:01:11] <rayh> Our sense of "open" is that the authority to make decisions about what gets distributed based on merit and understanding and participation and leadership, not solely on employment or a title or a business plan.
[18:01:11] <rayh> Winifred "Mitchell" Baker, chair of the Mozilla Foundation
[18:01:11] <rayh> http://www.motherjones.com/interview/2008/09/inside-the-firefoxs-den.html
[19:45:25] <cradek> remember the multiple-user-interfaces-several-second-delay thing? it's back (in trunk)
[19:45:33] <cradek> I really thought it was fixed
[19:45:46] <cradek> (or at least worked around somewhat)
[19:46:06] <SWPadnos> UIs are all updated by polling, no?
[19:46:32] <cradek> let me come up with a good how-to-reproduce here
[19:50:02] <cradek> hm, might be AXIS-only
[19:51:19] <cradek> ugh, it's the mode-switch magic
[19:51:47] <cradek> change halui-halvcp to use axis. machine on, see how f3/f5 in axis are responsive.
[19:51:57] <cradek> in halvcp change mode, then try f3/f5 in axis again
[19:52:30] <cradek> it's not just modes
[19:52:42] <cradek> poke feed override + in halvcp, then try f3/f5 in axis again
[19:53:18] <cradek> it's only f3/f5. if you poke f9 in axis, you immediately see the spindle on/off message being sent in debug
[19:57:33] <cradek> the pause is at the first wait_complete() in ensure_mode
[19:59:04] <SWPadnos> ah, so it's timing out waiting for a command it didn't issue?
[19:59:40] <cradek> yes
[20:14:43] <cradek> I thought I fixed all those once before. you shouldn't wait on a command unless you just sent one. it's just a bug to do that.
[20:16:51] <cradek> arg, version 1.1
[20:25:49] <cradek> whee, fixed
[20:26:31] <SWPadnos> again? :)
[20:26:54] <cradek> yes, pretty sure I did this once before, but I must have missed some
[20:27:04] <cradek> it's easy to get wrong
[20:27:38] <SWPadnos> indeed
[20:29:32] <cradek> wow, you can get tons (ha!) of good used real machinery, possibly wanting an emc retrofit, for the cost of one of those cnc desktop mills
[20:30:03] <SWPadnos> or about half of a Tormach
[20:31:08] <cradek> the sherline cnc lathe is $2500. If you don't count buying the trailer, my very real lathe + retrofit (if time is free) cost less than that
[20:31:37] <cradek> I know they have different applications, but jeez it's a surprising comparison.
[20:31:45] <SWPadnos> yep, and I'm looking at an HNC also, which would be less than a Sherline (minus the trailer ;) )
[20:32:04] <cradek> it's a very cool machine
[20:32:12] <cradek> does yours say "super precision"?
[20:32:18] <SWPadnos> I don't think so
[20:32:36] <SWPadnos> there's a CHNC-II super precision on eBay I think
[20:32:49] <cradek> I hear, but cannot say for sure, that that name meant more than a difference in the control
[20:32:56] <SWPadnos> heh
[20:33:03] <SWPadnos> I imagine the screws are different as well
[20:34:09] <SWPadnos> here's a nice one, too bad it's 2-3x what I want to pay: http://cgi.ebay.com/Hardinge-CHNC-Super-Precision-Chucker-Model-CHNC4-16C_W0QQitemZ300229030525QQcmdZViewItem?_trksid=p3286.m20.l1116
[20:34:24] <SWPadnos> oh, and 1 ton too heavy :)
[20:34:37] <cradek> much more modern control - with a crt even
[20:34:46] <alex_joni> heh, 1 ton is next to nothing :)
[20:34:47] <cradek> might even be a microprocessor in there
[20:34:52] <cradek> wonder if it has encoders or resolvers
[20:34:59] <SWPadnos> this is the affordable one: http://cgi.ebay.com/Hardinge-HNC-Chucker-2-5hp_W0QQitemZ190201838136QQcmdZViewItem?_trksid=p3286.m20.l1116
[20:35:16] <cradek> difference between HNC and CHNC is just the control isn't it?
[20:35:39] <SWPadnos> manufacture date and CNC vs. NC
[20:35:59] <SWPadnos> the CHNC are newer in general. I don't know if they made them both at any time
[20:36:06] <cradek> 2250 seems high unless it's very close and convenient to get home at no cost...
[20:36:10] <SWPadnos> though the CHNC4 would be a more recent one
[20:36:33] <cradek> (I paid extra for my mill because of its proximity, and it was smart to do it)
[20:36:38] <SWPadnos> 365 miles
[20:36:41] <SWPadnos> not bad at all
[20:36:53] <cradek> a little bad :-)
[20:36:54] <SWPadnos> and interstate the whole way
[20:36:56] <SWPadnos> heh
[20:37:00] <SWPadnos> I went further for the mill
[20:37:13] <SWPadnos> and we grabbeda lathe on the way back through (not for me)
[20:37:27] <alex_joni> I gotta order shipment for the next robot I'll install in a couple of weeks
[20:37:36] <alex_joni> that's a bit more of a hassle than 1-2t :P
[20:38:33] <cradek> SWPadnos: what kind of power do you have?
[20:39:34] <SWPadnos> a 240V 40A panel I pulled from the main panel, and a 5HP rotary phase converter
[20:40:17] <cradek> my hnc was stamped as wired 440 but I found it was 240 like the guy said
[20:40:35] <cradek> so you might check before you buy - could be trouble
[20:42:02] <SWPadnos> it's almost universally possible to rewire a transformer to switch between 240/480
[20:42:10] <SWPadnos> unless it's a delta/wye thing
[20:42:13] <cradek> yes
[20:42:50] <cradek> but there are a dozen transformers (really) and only the couple biggest ones had straps
[20:43:00] <SWPadnos> oh
[20:43:03] <cradek> and I bet the coolant motor is not strapped
[20:43:05] <alex_joni> all 3-phase?
[20:43:12] <cradek> no, all single phase!
[20:43:39] <alex_joni> then you can solve it all with a big transformer :)
[20:44:14] <cradek> well I bet you don't care about the control anyway. forget what I said.
[20:47:19] <SWPadnos> heh
[20:47:23] <SWPadnos> if the control works ... :)