Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-12 Thread John Thornton
To create custom panels you use pyVCP as described here:

http://www.linuxcnc.org/docs/devel/html/hal_pyvcp.html#r1_5_10

John

On 12 Jan 2009 at 2:02, Steve Blackmore wrote:

 On Thu, 08 Jan 2009 06:55:51 -0500, you wrote:
 
  The new algorithm handles concave corners
 
 And here I am, halfway through writing the next installment 
 of Adventures in Filleting, explaining how to lay an arc 
 into a concave corner to avoid gouging. I am crushed, I 
 tell you, -crushed- by this horrible news!
 
 Are you guys reading the Mach forum? G
 
 Background developments seems to following Mach very closely!
 
 The big bit that's missing/difficult (nigh impossible for us new
 guys)
 in EMC is GUI screen editing (the user interface) and is the main
 reason
 I can't use it on a day to day basis.
 
 I need to write some custom turn screens for a large OEM. that
 include a
 tool changer screen that has user adjustable values. I'm stuck with
 Mach
 that has other technical issues. 
 
 Can anybody help, or point me in the right direction?
  
 
 Steve Blackmore
 --
 
 
 --
 Check out the new SourceForge.net Marketplace.
 It is the best place to buy or sell services for
 just about anything Open Source.
 http://p.sf.net/sfu/Xq1LFB
 ___
 Emc-users mailing list
 Emc-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/emc-users
 



--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-12 Thread Leslie Newell
Hi Steve,

What sort of time scale are you working on? I am working on a GUI where 
you can lay out the controls like you can in Mach. The editor is also a 
bit less frustrating to use than scream4! It includes scripting as well 
(Lua, not VBScript). The GUI itself will run in Linux, Windows or 
Mac(untested). It talks to emc through sockets so it can run locally or 
on a remote computer. As this is a non-profitmaking project it has to 
take a back seat to my real work. I am hoping to have something usable 
by mid to late February. It rather depends on my workload as to whether 
I will actually achieve that goal.

By the way, emc should shortly support radius programming if I can get 
the patch accepted.

Les

Steve Blackmore wrote:


 Are you guys reading the Mach forum? G

 Background developments seems to following Mach very closely!

 The big bit that's missing/difficult (nigh impossible for us new guys)
 in EMC is GUI screen editing (the user interface) and is the main reason
 I can't use it on a day to day basis.

 I need to write some custom turn screens for a large OEM. that include a
 tool changer screen that has user adjustable values. I'm stuck with Mach
 that has other technical issues. 

 Can anybody help, or point me in the right direction?
  

 Steve Blackmore
 --
   


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-12 Thread Chris Radek
On Mon, Jan 12, 2009 at 05:29:21PM +, Leslie Newell wrote:
 
 By the way, emc should shortly support radius programming if I can get 
 the patch accepted.

[diameter]

I was just thinking about this the other day.  I actually thought it
was in CVS but it's not yet.  What problems remained?  Let's talk
about it on irc again.


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-11 Thread paul_c
On Sunday 11 January 2009, Chris Radek wrote:
  Please send a patch that makes it build without warnings
  You can send it to emc-developers or to me personally.

Restore my CVS access, and you won't need to mess with patches.

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-11 Thread Alex Joni
I suppose you sent a ssh public key as described here:
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?DeveloperAccess

Regards,
Alex

- Original Message - 
From: paul_c pau...@users.sourceforge.net
To: Enhanced Machine Controller (EMC) emc-users@lists.sourceforge.net
Sent: Sunday, January 11, 2009 12:37 PM
Subject: Re: [Emc-users] New cutter compensation algorithm in TRUNK


On Sunday 11 January 2009, Chris Radek wrote:
 Please send a patch that makes it build without warnings
 You can send it to emc-developers or to me personally.

Restore my CVS access, and you won't need to mess with patches.



--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-11 Thread Chris Radek
On Sun, Jan 11, 2009 at 10:37:12AM +, paul_c wrote:
 On Sunday 11 January 2009, Chris Radek wrote:
  ?Please send a patch that makes it build without warnings
  ?You can send it to emc-developers or to me personally.
 
 Restore my CVS access, and you won't need to mess with patches.


Paul, this is tiring.  This game you play only makes you look bad.
Last time you played it (2008), you accused John K of taking away your
access:

http://thread.gmane.org/gmane.linux.distributions.emc.user/7223/focus=7321

Then I reminded you that you yourself declined access (2006):

http://sourceforge.net/mailarchive/message.php?msg_id=20060405140454.GY9018%40timeguy.com

If you don't want to help, that's fine.

Chris


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-11 Thread Steve Blackmore
On Thu, 08 Jan 2009 06:55:51 -0500, you wrote:

 The new algorithm handles concave corners

And here I am, halfway through writing the next installment 
of Adventures in Filleting, explaining how to lay an arc 
into a concave corner to avoid gouging. I am crushed, I 
tell you, -crushed- by this horrible news!

Are you guys reading the Mach forum? G

Background developments seems to following Mach very closely!

The big bit that's missing/difficult (nigh impossible for us new guys)
in EMC is GUI screen editing (the user interface) and is the main reason
I can't use it on a day to day basis.

I need to write some custom turn screens for a large OEM. that include a
tool changer screen that has user adjustable values. I'm stuck with Mach
that has other technical issues. 

Can anybody help, or point me in the right direction?
 

Steve Blackmore
--

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-10 Thread paul_c
On Thursday 08 January 2009, Chris Radek wrote:
 Today I merged my cutter compensation work.  The new algorithm
 handles concave corners and is not picky about entry moves.

You need to include cstdlib  cstring headers in interp_queue.cc and then it 
will at least compile with gcc-4.3.

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-10 Thread Chris Radek
On Sat, Jan 10, 2009 at 11:58:05PM +, paul_c wrote:
 
 You need to include cstdlib  cstring headers in interp_queue.cc and then it 
 will at least compile with gcc-4.3.

Thanks for helping test, paul.  I'm not surprised if I missed
something.  Please send a patch that makes it build without warnings
for you, and if it doesn't break my build with 4.0 I'll apply it.  You
can send it to emc-developers or to me personally.

Chris

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-09 Thread Alex Joni
It's a bit far from perfect at the moment.
There are basicly 2 different kinds of outputs:
M63/M64 Turn on/off digital output synched with motion

M64/M65 Turn on/off digital output immediately

It's been a really long time since I touched these, I know at some point 
they used to behave properly (they probably don't atm, and they would 
benefit from looking into them).
M64/65 are basicly executed when the command reaches the motion controller, 
so it's not at the exact time when the next motion starts.
M63/64 should probably get attached to motion commands and go on the TC 
queue. That way they would be handled by the trajectory planner at the right 
moment.
Although the right moment for a blended move is a bit hard to define.
1. Is it where accel starts on the next move? (we're starting to decellerate 
on the current move at the same time).
2. Is it when the next move is halfway through accel, and the current move 
is halfway through decel?
3. Is it where the current move decellerates completely?

I would probably go for 2, although I'm not sure how easy that is to 
implement.

Using exact stop it's easier to define the moment/position when to enable 
the output.

Just some thought to keep the discussion going..

Regards,
Alex


- Original Message - 
From: Leslie Newell les.new...@fastmail.co.uk
To: Enhanced Machine Controller (EMC) emc-users@lists.sourceforge.net
Sent: Friday, January 09, 2009 12:49 AM
Subject: Re: [Emc-users] New cutter compensation algorithm in TRUNK


I thought that would probably be what happens. Presumably it also exact
 stops to set an output?

 Les

 Jeff Epler wrote:
 No, I believe you'll find it exact-stops at that point.
 Jeff

 

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-08 Thread Ed Nisley
 The new algorithm handles concave corners

And here I am, halfway through writing the next installment 
of Adventures in Filleting, explaining how to lay an arc 
into a concave corner to avoid gouging. I am crushed, I 
tell you, -crushed- by this horrible news!

big grin

The timing is actually great. I'll add a note along the 
lines of by the time you read this, EMC2 should handle 
concave corners automagically, folks can download the Live 
CD, and everybody lives happily ever after. I love a happy 
ending.

I must do some prep for Cabin Fever (i.e., whack stock into 
bite-sized pieces  collect my toys into one untidy heap), 
but after we're back I'll see how it works. I don't do any 
of that fancy machining stuff, though, so most likely I 
can't contribute any useful checking; if it ran your 
testcase, it'll have no trouble with my parts.

Great improvement... many thanks!

-- 
Ed

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-08 Thread Jeff Epler
On Thu, Jan 08, 2009 at 06:54:37AM +, Leslie Newell wrote:
 Looks good. It would be nice if you could enable these:
 
 reading/writing motion's digital/analog ins/outs

I don't think it is possible to enable reading inputs.  Consider the
following:

( already in cutter comp mode )
N000 G0 X0 Y0
N100 G1 X1
N200 M66 P1 L0 (intended to say: immediately read digital input 1 to #5399)
N300 G1 Y[1-2*#5399]  ( so this line either goes to Y1 or Y-1 )

The move on N300 depends on the oucome of the M66 on line N200, but that
can't be executed until the compensated endpoint of the move on line
N100 is computed, which depends on the move on line N300, which depends
on the outcome of the M66 on line N200.

I don't see how to untangle this knot.

Jeff

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-08 Thread Leslie Newell
How is that handled currently?

Actually I am more interested in writing outputs than reading inputs. 
For instance on a plasma cutter you may want to turn off the THC on some 
corners to prevent torch dive.

Les

Jeff Epler wrote:
 I don't think it is possible to enable reading inputs.  Consider the
 following:

 ( already in cutter comp mode )
 N000 G0 X0 Y0
 N100 G1 X1
 N200 M66 P1 L0 (intended to say: immediately read digital input 1 to #5399)
 N300 G1 Y[1-2*#5399]  ( so this line either goes to Y1 or Y-1 )

 The move on N300 depends on the oucome of the M66 on line N200, but that
 can't be executed until the compensated endpoint of the move on line
 N100 is computed, which depends on the move on line N300, which depends
 on the outcome of the M66 on line N200.

 I don't see how to untangle this knot.

 Jeff
   


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-08 Thread Jeff Epler
On Thu, Jan 08, 2009 at 09:01:54PM +, Leslie Newell wrote:
 How is that handled currently?

  ( already in cutter comp mode )
  N000 G0 X0 Y0
  N100 G1 X1
  N200 M66 P1 L0 (intended to say: immediately read digital input 1 to #5399)
  N300 G1 Y[1-2*#5399]  ( so this line either goes to Y1 or Y-1 )

In 2.2, I believe emc would move directly to X1 Y0 and read the input.
If the resulting move on N300 creates a concave corner, then an error
occurs.

With chris's new method the N100 move is delayed until the N300 move is
known to be convex or concave, so that if necessary (the concave case)
the N100 move can be trimmed back to the necessary spot to avoid
gouging.

Jeff

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-08 Thread Leslie Newell
Fair enough for exact stop but what about CV? It would potentially try 
to look ahead past the read.

Les

Jeff Epler wrote:
 In 2.2, I believe emc would move directly to X1 Y0 and read the input.
 If the resulting move on N300 creates a concave corner, then an error
 occurs.

 With chris's new method the N100 move is delayed until the N300 move is
 known to be convex or concave, so that if necessary (the concave case)
 the N100 move can be trimmed back to the necessary spot to avoid
 gouging.

 Jeff
   


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-08 Thread Jeff Epler
On Thu, Jan 08, 2009 at 09:26:39PM +, Leslie Newell wrote:
 Fair enough for exact stop but what about CV? It would potentially try 
 to look ahead past the read.

No, I believe you'll find it exact-stops at that point.

Jeff

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-08 Thread Leslie Newell
I thought that would probably be what happens. Presumably it also exact 
stops to set an output?

Les

Jeff Epler wrote:
 No, I believe you'll find it exact-stops at that point.
 Jeff
   


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


[Emc-users] New cutter compensation algorithm in TRUNK

2009-01-07 Thread Chris Radek
Today I merged my cutter compensation work.  The new algorithm
handles concave corners and is not picky about entry moves.  The
old entry methods are still supported, as is any entry line longer
than the tool radius (as is customary).

I have tested many old working programs to make sure they run
exactly the same, and also crafted suitably perverse programs to
verify the newly-handled cases.

http://timeguy.com/cradek-files/emc/t3.png

This is a program that runs a subroutine three times: once without
compensation, and then with left and right comp.  You can see the
entry and exit moves are not special (they happen to make concave
corners in this program).

I believe it should also now be possible to use most/all
CAM-generated compensated code.  EMC2 can do the full
compensation, or the CAM can compensate for nominal tool size and
the user can specify a small diameter in the tool table (like
-0.010) to compensate for tool resharpening.  I understand (but
only from hearing in passing) that this is what Synergy wants and
I hope someone can test it (Hi Dave E!) I do not have any CAM
programs to test with so I'm relying on you folks.

Also I would especially appreciate if folks that are experts at
hand-writing code with cutter compensation would try it out and
perhaps come up with more perverse cases.  (Hi Ed N!  Hi John K!)

Some things that are probably currently under-tested:

lathes
inverse time mode
switching spindle and feed modes
helixes
switching absolute/relative
switching inch/mm
switching relative/absolute arc centers

A few things that I believe were previously allowed are currently
disallowed when compensation is on:

reading/writing motion's digital/analog ins/outs
switching coordinate systems
changing tools or tool length offset
enabling/disabling feed/speed override
enabling/disabling adaptive feed
running user-defined m-codes

I think some, but not all, of these could be allowed if someone
needs them.

Chris

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-07 Thread Stuart Stevenson
On Wed, Jan 7, 2009 at 8:07 PM, Chris Radek ch...@timeguy.com wrote:
 Today I merged my cutter compensation work.  The new algorithm
 handles concave corners and is not picky about entry moves.  The
 old entry methods are still supported, as is any entry line longer
 than the tool radius (as is customary).

 I have tested many old working programs to make sure they run
 exactly the same, and also crafted suitably perverse programs to
 verify the newly-handled cases.

 http://timeguy.com/cradek-files/emc/t3.png

 This is a program that runs a subroutine three times: once without
 compensation, and then with left and right comp.  You can see the
 entry and exit moves are not special (they happen to make concave
 corners in this program).

 I believe it should also now be possible to use most/all
 CAM-generated compensated code.  EMC2 can do the full
 compensation, or the CAM can compensate for nominal tool size and
 the user can specify a small diameter in the tool table (like
 -0.010) to compensate for tool resharpening.  I understand (but
 only from hearing in passing) that this is what Synergy wants and
 I hope someone can test it (Hi Dave E!) I do not have any CAM
 programs to test with so I'm relying on you folks.

 Also I would especially appreciate if folks that are experts at
 hand-writing code with cutter compensation would try it out and
 perhaps come up with more perverse cases.  (Hi Ed N!  Hi John K!)

 Some things that are probably currently under-tested:

lathes
inverse time mode
this is exciting - I can't wait to try the 5 axis cutter diameter comp
- I will do so as soon as I get the cinci going - thanks a lot :)

switching spindle and feed modes
helixes
switching absolute/relative
switching inch/mm
switching relative/absolute arc centers

 A few things that I believe were previously allowed are currently
 disallowed when compensation is on:

reading/writing motion's digital/analog ins/outs
switching coordinate systems
changing tools or tool length offset
enabling/disabling feed/speed override
enabling/disabling adaptive feed
running user-defined m-codes

 I think some, but not all, of these could be allowed if someone
 needs them.

 Chris

 --
 Check out the new SourceForge.net Marketplace.
 It is the best place to buy or sell services for
 just about anything Open Source.
 http://p.sf.net/sfu/Xq1LFB
 ___
 Emc-users mailing list
 Emc-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/emc-users



--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] New cutter compensation algorithm in TRUNK

2009-01-07 Thread Leslie Newell
Looks good. It would be nice if you could enable these:

reading/writing motion's digital/analog ins/outs
enabling/disabling feed/speed override
enabling/disabling adaptive feed
running user-defined m-codes

Thanks,
Les



Chris Radek wrote:
 Today I merged my cutter compensation work.  The new algorithm
 handles concave corners and is not picky about entry moves.  The
 old entry methods are still supported, as is any entry line longer
 than the tool radius (as is customary).

 I have tested many old working programs to make sure they run
 exactly the same, and also crafted suitably perverse programs to
 verify the newly-handled cases.

 http://timeguy.com/cradek-files/emc/t3.png

 This is a program that runs a subroutine three times: once without
 compensation, and then with left and right comp.  You can see the
 entry and exit moves are not special (they happen to make concave
 corners in this program).

 I believe it should also now be possible to use most/all
 CAM-generated compensated code.  EMC2 can do the full
 compensation, or the CAM can compensate for nominal tool size and
 the user can specify a small diameter in the tool table (like
 -0.010) to compensate for tool resharpening.  I understand (but
 only from hearing in passing) that this is what Synergy wants and
 I hope someone can test it (Hi Dave E!) I do not have any CAM
 programs to test with so I'm relying on you folks.

 Also I would especially appreciate if folks that are experts at
 hand-writing code with cutter compensation would try it out and
 perhaps come up with more perverse cases.  (Hi Ed N!  Hi John K!)

 Some things that are probably currently under-tested:

 lathes
 inverse time mode
 switching spindle and feed modes
 helixes
 switching absolute/relative
 switching inch/mm
 switching relative/absolute arc centers

 A few things that I believe were previously allowed are currently
 disallowed when compensation is on:

 reading/writing motion's digital/analog ins/outs
 switching coordinate systems
 changing tools or tool length offset
 enabling/disabling feed/speed override
 enabling/disabling adaptive feed
 running user-defined m-codes

 I think some, but not all, of these could be allowed if someone
 needs them.

 Chris

 --
 Check out the new SourceForge.net Marketplace.
 It is the best place to buy or sell services for
 just about anything Open Source.
 http://p.sf.net/sfu/Xq1LFB
 ___
 Emc-users mailing list
 Emc-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/emc-users
   


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users