Re: [Emc-users] Halscope Log Files

2020-10-22 Thread Thomas J Powderly

Hello

Comparing 2 scope traces could be handy.


I had a few techs working for me in a cnc repair situation.

We all used tek scopes and had 'screen savers' that actually saved the 
source code to recreate screen


These 'screenshots' could be reloaded  on a 'channel' and compared to a 
real live channel.


( there are many related ideas on web like

http://techforcurious.website/how-to-save-data-from-oscilloscope-using-python-in-linux/ 
)



So I would give the techs some 'screenshots' as :

    This is what it should look like"

and they would attach

    This is what I got"

to thier reports.


This is very basic trouble shooting...

    the difference between WhatYouWant and WhatYouGot.


Tweaking a pot or param untill the 2 pictures agree is intuitive.


HalScope reloading as an overlay/onion-skin could be handy


my 2c

TomP

On 10/22/20 11:39 PM, andy pugh wrote:

On Thu, 22 Oct 2020 at 16:50, Nicklas SB Karlsson  wrote:

Did not read very carefully, if you need maybe I could spend a few other
try to get the halscope log file into Octave.

I would be much more interested in getting a halcope log back in to halscope.




___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Halscope Log Files

2020-10-22 Thread Robert Ellenberg
Andy,

Try this branch here:


https://github.com/LinuxCNC/linuxcnc/tree/rellenberg/halscope

It adds native CSV-saving capability to halscope (if you specify a .csv
file in the save dialog). It's much easier to parse in something like
octave (and also much faster). It won't do much for the reading-back-in
part, unfortunately.

-Rob

On Thu, Oct 22, 2020 at 12:44 PM andy pugh  wrote:

> On Thu, 22 Oct 2020 at 16:50, Nicklas SB Karlsson  wrote:
> >
> > Did not read very carefully, if you need maybe I could spend a few other
> > try to get the halscope log file into Octave.
>
> I would be much more interested in getting a halcope log back in to
> halscope.
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1912
>
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] spindle syncing arbitrary shapes.. Yes please...

2020-10-22 Thread Gregg Eshelman via Emc-users
I wonder if any company is making such pressed together camshafts for old 
engines like 350 Chevy and 302 Ford? Lighter weight = less rotational inertia. 
Should result in less stress on the timing chain and sprocket.

On Thursday, October 22, 2020, 6:45:03 AM MDT, Leonardo Marsaglia 
 wrote:  
 I must add, that lately we're considering making the camshafts this way:

https://www.youtube.com/watch?v=kkHgf5SSsAQ

This would eliminate the roughing process at all.

El jue., 22 oct. 2020 a las 9:35, Leonardo Marsaglia ()
escribió:

> Looks like this would be perfect for roughing camshafts prior to heat
>> treating and grinding. I bet the guy with the camshaft factory who adapted
>> LCNC to control induction heat treaters would be interested in this.
>
>
> This is what I achieved so far Gregg
>
> https://www.youtube.com/watch?v=xjBXa6RHSPQ
>
> The thing is, we have an old landis grinder that can rough those cams in
> about 25 seconds (1.5 mm of material to remove in the radius) per lobe
> (using 60 grit grinding wheel and dessing it with a high feed). So, we are
> waiting until we have a little more time to make a live tooling gig to
> rough them (I already have that on paper but didn't have the time to
> implement it yet).
>
> Without live tooling it's not that practical to rough the lobes/cams for
> production.
  
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Emc-users Digest, Vol 174, Issue 64

2020-10-22 Thread Alan Condit
Andy,

Thank you very much. Because of the error message I was looking in the
wrong place. That fix got it to load successfully, and allowed me to debug
the problem and fix it.

Thanks again,
Alan


> From: andy pugh 
> To: "Enhanced Machine Controller (EMC)" 
> Cc:
> Bcc:
> Date: Thu, 22 Oct 2020 19:03:25 +0100
> Subject: Re: [Emc-users] Apparent changes in gcode in Linuxcnc 2.8.0
> On Wed, 21 Oct 2020 at 14:52, Alan Condit  wrote:
>
> > I have a bunch of wizards that I have written under 2.7 and under 2.8
> they won’t work. The biggest change is that you used to be able to write
> the subroutine declaration as O< CutBevel > SUB [1] [2] [3]  like a formal
> declaration of parameters. Now I have to go through and make all of them
> just comments like O SUB ([1] [2] [3]).
>
> Subroutines get parameters strictly by position, they just appear as #1,
> #2 etc. You can have a comment to document what they do, but I don't think
> anything has changed there
>
> The problem is actually line 76:
>
> G00 X0.0 Z[#Zcut]
>
> Should be
>
> G00 X0.0 Z[#]
>
> --
> atp
>
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Now do I have a bad card?

2020-10-22 Thread Mark Wendt
>
> My next attempt seems to have arrived at a usable config although neither
> the spindle nor axisA is wired up ATM.  But I am getting the desired
> signals to make it work from the stepgen 3 terminals on tb2, getting the
> complements pairs out on the 4 terminals labeled as stepgen 3.
>
> I will need to go thru the hal file, removing whats no longer used, but I
> need to make up an interface for the olimex card next, which needs 8
> signals, 3 from liuxcnc, pdm and dir+, dir-, which I now have and can
> actually see with a halmeter.  The spindles pdm is on the 2nd pwmgen
> with the pwd from the bob. And I need to hook the spindle dir back up
> on stepgen#3 and the A dirs to the olimex stamp on the other stepgen#3
> pins on the 7i76D.
>
> I think that might be Progress!  Spose?  Time to rest my back.  Getting
> old is unavoidable unless you die Junge. Considering the alternative, I
> rather like it. ;p)
>
> This olimex card has so low an R for the on gates that it doesn't even
> come with a heat sink for a 30 amp rated load, the whole card is about
> the size of an airmail stamp. If I think it needs cooling, I'll mount it
> in the psu's exhaust port air stream.  Or I've some bigger heat sink
> stock.
>
> Thank you Peter.
>
> Cheers, Gene Heskett
>

Any chance we could trim these posts?  This one had a comet tail about a
mile and a half long.  Makes for really difficult reading when it takes a
while to either find where the comments are or scroll only to the bottom to
find a paragraph or two.

Thanks,
Mark

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Now do I have a bad card?

2020-10-22 Thread Gene Heskett
On Thursday 22 October 2020 11:07:19 Gene Heskett wrote:

> On Thursday 22 October 2020 09:39:35 Peter C. Wallace wrote:
> > On Thu, 22 Oct 2020, Gene Heskett wrote:
> > > Date: Thu, 22 Oct 2020 04:41:19 -0400
> > > From: Gene Heskett 
> > > Reply-To: "Enhanced Machine Controller (EMC)"
> > > 
> > > To: emc-users@lists.sourceforge.net
> > > Subject: Re: [Emc-users] Now do I have a bad card?
> > >
> > > On Wednesday 21 October 2020 23:05:16 Peter C. Wallace wrote:
> > >> On Wed, 21 Oct 2020, Gene Heskett wrote:
> > >>> Date: Wed, 21 Oct 2020 21:06:06 -0400
> > >>> From: Gene Heskett 
> > >>> Reply-To: "Enhanced Machine Controller (EMC)"
> > >>> 
> > >>> To: emc-users@lists.sourceforge.net
> > >>> Subject: Re: [Emc-users] Now do I have a bad card?
> > >>>
> > >>> On Wednesday 21 October 2020 20:21:30 Peter C. Wallace wrote:
> > >>> [...]
> > >>>
> > >> sudo mesaflash --device 5i25 --readhmid
> > >
> > > gene@GO704:~/linuxcnc$ sudo mesaflash --device 5i25
> > > --readhmid [sudo] password for gene:
> > > Configuration Name: HOSTMOT2
> > >
> > > General configuration information:
> > >
> > >  BoardName : MESA5I25
> > >  FPGA Size: 9 KGates
> > >  FPGA Pins: 144
> > >  Number of IO Ports: 2
> > >  Width of one I/O port: 17
> > >  Clock Low frequency: 33. MHz
> > >  Clock High frequency: 200. MHz
> > >  IDROM Type: 3
> > >  Instance Stride 0: 4
> > >  Instance Stride 1: 64
> > >  Register Stride 0: 256
> > >  Register Stride 1: 256
> > >
> > > Modules in configuration:
> > >
> > >  Module: WatchDog
> > >  There are 1 of WatchDog in configuration
> > >  Version: 0
> > >  Registers: 3
> > >  BaseAddress: 0C00
> > >  ClockFrequency: 33.333 MHz
> > >  Register Stride: 256 bytes
> > >  Instance Stride: 4 bytes
> > >
> > >  Module: IOPort
> > >  There are 2 of IOPort in configuration
> > >  Version: 0
> > >  Registers: 5
> > >  BaseAddress: 1000
> > >  ClockFrequency: 33.333 MHz
> > >  Register Stride: 256 bytes
> > >  Instance Stride: 4 bytes
> > >
> > >  Module: QCount
> > >  There are 2 of QCount in configuration
> > >  Version: 2
> > >  Registers: 5
> > >  BaseAddress: 3000
> > >  ClockFrequency: 33.333 MHz
> > >  Register Stride: 256 bytes
> > >  Instance Stride: 4 bytes
> > >
> > >  Module: SSerial
> > >  There are 1 of SSerial in configuration
> > >  Version: 0
> > >  Registers: 6
> > >  BaseAddress: 5B00
> > >  ClockFrequency: 33.333 MHz
> > >  Register Stride: 256 bytes
> > >  Instance Stride: 64 bytes
> > >
> > >  Module: PWM
> > >  There are 2 of PWM in configuration
> > >  Version: 0
> > >  Registers: 5
> > >  BaseAddress: 4100
> > >  ClockFrequency: 200.000 MHz
> > >  Register Stride: 256 bytes
> > >  Instance Stride: 4 bytes
> > >
> > >  Module: StepGen
> > >  There are 9 of StepGen in configuration
> > >  Version: 2
> > >  Registers: 10
> > >  BaseAddress: 2000
> > >  ClockFrequency: 33.333 MHz
> > >  Register Stride: 256 bytes
> > >  Instance Stride: 4 bytes
> > >
> > >  Module: LED
> > >  There are 1 of LED in configuration
> > >  Version: 0
> > >  Registers: 1
> > >  BaseAddress: 0200
> > >  ClockFrequency: 33.333 MHz
> > >  Register Stride: 256 bytes
> > >  Instance Stride: 4 bytes
> > >
> > > Configuration pin-out:
> > >
> > > IO Connections for P3
> > > Pin#  I/O   Pri. funcSec. func   Chan  Pin
> > > func Pin Dir
> > >
> > > 1  0   IOPort   StepGen  0   
> > > Dir/Table2 (Out) 14  1   IOPort   StepGen 
> > > 0 Step/Table1 (Out) 2  2   IOPort   StepGen   
> > >   1 Dir/Table2  (Out) 15  3   IOPort   StepGen
> > > 1 Step/Table1 (Out) 3  4   IOPort   StepGen 2
> > > Dir/Table2  (Out) 16  5   IOPort   StepGen 2
> > > Step/Table1 (Out) 4  6   IOPort   StepGen 3
> > > Dir/Table2  (Out) 17  7   IOPort   StepGen 3
> > > Step/Table1 (Out) 5  8   IOPort StepGen  4
> > > Dir/Table2  (Out) 6  9   IOPort StepGen  4
> > > Step/Table1 (Out) 7 10   IOPort SSerial  0
> > > TXData1 (Out) 8 11 IOPort   SSerial 0
> > > RXData1 (In) 9 12 IOPort   SSerial 0
> > > TXData2 

Re: [Emc-users] Cutting fluid

2020-10-22 Thread Nicklas SB Karlsson
In some oils there are PAHs polyaromatic hydrocarbons and these have 
been linked to some forms of cancer 
https://en.wikipedia.org/wiki/Polycyclic_aromatic_hydrocarbon Then 
reading about Creosot https://en.wikipedia.org/wiki/Creosote I found 
there is difference in chemical properties between coal-tar and wood-tar 
Creosot and I also expect difference in chemical properties between 
mineral oil and vegetable oil.


Expect food oil to be relatively harmless also then used as a cutting 
fluid, no rust and does not freeze during winter. Maybe bacterial growth 
might be a problem but in such case I could kill them by heating 
regularly. Do not freeze during winter is an important future for me as 
is now.



Den 2020-10-21 kl. 21:44, skrev marcus.bow...@visible.eclipse.co.uk:

On 2020-10-21 20:10, Nicklas SB Karlsson wrote:
I learned cutting fluid could be unhealthy. Anyone here have any 
experience?


I understand the problem has been that soluble cutting oil tends to 
drench the operator at waist level (on older machines which do not 
have total enclosures). That led to a noted connection between cancer 
and soluble oil.
I don't know of any link between neat cutting oil and medical 
conditions, but it is an oil, so the usual hazards apply.


I have serious reservations about the current fashion for atomised 
mist spray coolant, which I believe to be a real danger to the lungs 
and possibly the eyes, nose and mouth. I have not seen any medical 
studies on this, but atomised fluids of all sorts are generally a bad 
idea.

Just my opinion.

Marcus


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Apparent changes in gcode in Linuxcnc 2.8.0

2020-10-22 Thread andy pugh
On Wed, 21 Oct 2020 at 14:52, Alan Condit  wrote:

> I have a bunch of wizards that I have written under 2.7 and under 2.8 they 
> won’t work. The biggest change is that you used to be able to write the 
> subroutine declaration as O< CutBevel > SUB [1] [2] [3]  like a formal 
> declaration of parameters. Now I have to go through and make all of them just 
> comments like O SUB ([1] [2] [3]).

Subroutines get parameters strictly by position, they just appear as
#1, #2 etc. You can have a comment to document what they do, but I
don't think anything has changed there

The problem is actually line 76:

G00 X0.0 Z[#Zcut]

Should be

G00 X0.0 Z[#]

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Halscope Log Files

2020-10-22 Thread andy pugh
On Thu, 22 Oct 2020 at 16:50, Nicklas SB Karlsson  wrote:
>
> Did not read very carefully, if you need maybe I could spend a few other
> try to get the halscope log file into Octave.

I would be much more interested in getting a halcope log back in to halscope.

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Apparent changes in gcode in Linuxcnc 2.8.0

2020-10-22 Thread Alan Condit
Andy,

I was looking more closely at the wizards. They date from around 2014. I have 
been using them up until about 2 years ago. I went through a bunch of them 
yesterday. The only change that I had to make to get them to work was get rid 
of the “formal declarations” and comments on the same line as the o. I 
don’t know strictly speaking if I had to change the comment. Then I took one of 
the working wizards and replaced the body of the subroutine with the code from 
my “bevel” wizard (plus a little editing to match variable names. I commented 
out the call to the subroutine and it would load. But when I uncommented the 
call to my subroutine it gave me the same error as before.

So the working wizard is LTurnEXT.ngc 
The one that still won’t work is LBevelEXT.ngc 
I am baffled as to what is wrong.

Alan

>> On Wed, 21 Oct 2020 at 14:52, Alan Condit  wrote:
>> 
>> I have a bunch of wizards that I have written under 2.7 and under 2.8 they 
>> won't work. The biggest change is that you used to be able to write the 
>> subroutine declaration as O SUB [1] [2] [3]
>> like a formal declaration of parameters. Now I have to go through and make 
>> all of them
>>  just comments like O SUB ([1] [2] [3]).
> 
> This doesn't sound right. As far as I know there has not been any
> change made in this regard.
> There hasn't been any change in the docs that describe how to call a sub.
> http://linuxcnc.org/docs/2.8/html/gcode/o-code.html#ocode:subroutines
> 
> atp


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Halscope Log Files

2020-10-22 Thread Nicklas SB Karlsson
Did not read very carefully, if you need maybe I could spend a few other 
try to get the halscope log file into Octave.



Den 2020-10-21 kl. 20:36, skrev andy pugh:

Does anyone have any investment in a tool to read the halscope log file format?

I am thinking that it is a bit unhelpful at the moment and a plain CSV
or similar would be much easier to work with in external tools. But it
would be unfortunate if doing that broke existing tools.

(And it would be better still if Halscope could read its own files back in)




___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Now do I have a bad card?

2020-10-22 Thread Gene Heskett
On Thursday 22 October 2020 09:39:35 Peter C. Wallace wrote:

> On Thu, 22 Oct 2020, Gene Heskett wrote:
> > Date: Thu, 22 Oct 2020 04:41:19 -0400
> > From: Gene Heskett 
> > Reply-To: "Enhanced Machine Controller (EMC)"
> > 
> > To: emc-users@lists.sourceforge.net
> > Subject: Re: [Emc-users] Now do I have a bad card?
> >
> > On Wednesday 21 October 2020 23:05:16 Peter C. Wallace wrote:
> >> On Wed, 21 Oct 2020, Gene Heskett wrote:
> >>> Date: Wed, 21 Oct 2020 21:06:06 -0400
> >>> From: Gene Heskett 
> >>> Reply-To: "Enhanced Machine Controller (EMC)"
> >>> 
> >>> To: emc-users@lists.sourceforge.net
> >>> Subject: Re: [Emc-users] Now do I have a bad card?
> >>>
> >>> On Wednesday 21 October 2020 20:21:30 Peter C. Wallace wrote:
> >>> [...]
> >>>
> >> sudo mesaflash --device 5i25 --readhmid
> >
> > gene@GO704:~/linuxcnc$ sudo mesaflash --device 5i25
> > --readhmid [sudo] password for gene:
> > Configuration Name: HOSTMOT2
> >
> > General configuration information:
> >
> >  BoardName : MESA5I25
> >  FPGA Size: 9 KGates
> >  FPGA Pins: 144
> >  Number of IO Ports: 2
> >  Width of one I/O port: 17
> >  Clock Low frequency: 33. MHz
> >  Clock High frequency: 200. MHz
> >  IDROM Type: 3
> >  Instance Stride 0: 4
> >  Instance Stride 1: 64
> >  Register Stride 0: 256
> >  Register Stride 1: 256
> >
> > Modules in configuration:
> >
> >  Module: WatchDog
> >  There are 1 of WatchDog in configuration
> >  Version: 0
> >  Registers: 3
> >  BaseAddress: 0C00
> >  ClockFrequency: 33.333 MHz
> >  Register Stride: 256 bytes
> >  Instance Stride: 4 bytes
> >
> >  Module: IOPort
> >  There are 2 of IOPort in configuration
> >  Version: 0
> >  Registers: 5
> >  BaseAddress: 1000
> >  ClockFrequency: 33.333 MHz
> >  Register Stride: 256 bytes
> >  Instance Stride: 4 bytes
> >
> >  Module: QCount
> >  There are 2 of QCount in configuration
> >  Version: 2
> >  Registers: 5
> >  BaseAddress: 3000
> >  ClockFrequency: 33.333 MHz
> >  Register Stride: 256 bytes
> >  Instance Stride: 4 bytes
> >
> >  Module: SSerial
> >  There are 1 of SSerial in configuration
> >  Version: 0
> >  Registers: 6
> >  BaseAddress: 5B00
> >  ClockFrequency: 33.333 MHz
> >  Register Stride: 256 bytes
> >  Instance Stride: 64 bytes
> >
> >  Module: PWM
> >  There are 2 of PWM in configuration
> >  Version: 0
> >  Registers: 5
> >  BaseAddress: 4100
> >  ClockFrequency: 200.000 MHz
> >  Register Stride: 256 bytes
> >  Instance Stride: 4 bytes
> >
> >  Module: StepGen
> >  There are 9 of StepGen in configuration
> >  Version: 2
> >  Registers: 10
> >  BaseAddress: 2000
> >  ClockFrequency: 33.333 MHz
> >  Register Stride: 256 bytes
> >  Instance Stride: 4 bytes
> >
> >  Module: LED
> >  There are 1 of LED in configuration
> >  Version: 0
> >  Registers: 1
> >  BaseAddress: 0200
> >  ClockFrequency: 33.333 MHz
> >  Register Stride: 256 bytes
> >  Instance Stride: 4 bytes
> >
> > Configuration pin-out:
> >
> > IO Connections for P3
> > Pin#  I/O   Pri. funcSec. func   Chan  Pin func
> > Pin Dir
> >
> > 1  0   IOPort   StepGen  0Dir/Table2
> > (Out) 14  1   IOPort   StepGen  0
> > Step/Table1 (Out) 2  2   IOPort   StepGen  1
> > Dir/Table2  (Out) 15  3   IOPort   StepGen
> > 1 Step/Table1 (Out) 3  4   IOPort   StepGen 2
> > Dir/Table2  (Out) 16  5   IOPort   StepGen 2
> > Step/Table1 (Out) 4  6   IOPort   StepGen 3
> > Dir/Table2  (Out) 17  7   IOPort   StepGen 3
> > Step/Table1 (Out) 5  8   IOPort StepGen  4
> > Dir/Table2  (Out) 6  9   IOPort StepGen  4
> > Step/Table1 (Out) 7 10   IOPort SSerial  0
> > TXData1 (Out) 8 11 IOPort   SSerial 
> > 0 RXData1 (In) 9 12 IOPort   SSerial
> >  0 TXData2 (Out) 10 13   IOPort   SSerial   
> >   0 RXData2 (In) 11 14   IOPort   QCount 0
> > Quad-IDX(In) 12 15   IOPort   QCount 0
> > Quad-B (In) 13 16   IOPort   QCount 0Quad-A
> > (In)
> >
> > 

Re: [Emc-users] mesaflash problem, Peter plz comment

2020-10-22 Thread Gene Heskett
On Thursday 22 October 2020 07:55:04 andy pugh wrote:

> On Thu, 22 Oct 2020 at 02:00, Gene Heskett  
wrote:
> > No, that steers the pwm which modulates the bottom half of the
> > bridge, and not externally separated, both sides on these full H
> > bridge cards.
>
> The step outputs are a differential pair, not PWM and /PWM. I am not
> sure if that is a real distinction.
> But you might need to be careful of the common-mode voltage limits of
> the differential pair driver on the 7i76.

The output swing of the stepgen outputs, both step and dir, is rail to 
rail, with the rail at around 5.1 volts. I've no reason to believe the 
corresponding inputs are any different. For the spindle encoder, which I 
inadvertantly bought with differential outputs, has a pair of rs485 
teeny boards, rigged as rx only, making rail to rail out of that diff 
pair.  Works flawlessly at speeds that cannot even begin to get thru the 
input opto's on the average bob. Clue?  The spindle tach dies, and the 
pid drives the spindle wide open at speeds above 400 revs.  The 7i76 
encoder inputs have no speed killing opto's. So it Just Works. This 
motor I'll use on the BS-1, has a maximum of 5.4 Kilohertz, pushing the 
opto's speed limits a bit but should work.  If needed, I can bypass the 
opto's on the bob, the need yet to be determined. NBD IOW.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] spindle syncing arbitrary shapes.. Yes please...

2020-10-22 Thread Sam Sokolik
Oh - this certainly isn't a production way of creating shapes (internally
and externally)..  (although some shapes it might be)

sam

On Thu, Oct 22, 2020 at 7:44 AM Leonardo Marsaglia 
wrote:

> I must add, that lately we're considering making the camshafts this way:
>
> https://www.youtube.com/watch?v=kkHgf5SSsAQ
>
> This would eliminate the roughing process at all.
>
> El jue., 22 oct. 2020 a las 9:35, Leonardo Marsaglia (<
> ldmarsag...@gmail.com>)
> escribió:
>
> > Looks like this would be perfect for roughing camshafts prior to heat
> >> treating and grinding. I bet the guy with the camshaft factory who
> adapted
> >> LCNC to control induction heat treaters would be interested in this.
> >
> >
> > This is what I achieved so far Gregg
> >
> > https://www.youtube.com/watch?v=xjBXa6RHSPQ
> >
> > The thing is, we have an old landis grinder that can rough those cams in
> > about 25 seconds (1.5 mm of material to remove in the radius) per lobe
> > (using 60 grit grinding wheel and dessing it with a high feed). So, we
> are
> > waiting until we have a little more time to make a live tooling gig to
> > rough them (I already have that on paper but didn't have the time to
> > implement it yet).
> >
> > Without live tooling it's not that practical to rough the lobes/cams for
> > production.
> >
> > El jue., 22 oct. 2020 a las 9:27, Leonardo Marsaglia (<
> > ldmarsag...@gmail.com>) escribió:
> >
> >> Yep he is in Chile.
> >>
> >>
> >> Argentina actually. It's similar, but out shores face the atlantic
> >> instead of the pacific. Also we're closer of being an eleventh world
> >> country than they are...
> >>
> >> El jue., 22 oct. 2020 a las 3:08, andrew beck (<
> andrewbeck0...@gmail.com>)
> >> escribió:
> >>
> >>> Yep he is in Chile.
> >>>
> >>>
> >>>
> >>> On Thu, Oct 22, 2020, 6:47 PM Gregg Eshelman via Emc-users <
> >>> emc-users@lists.sourceforge.net> wrote:
> >>>
> >>> > Looks like this would be perfect for roughing camshafts prior to heat
> >>> > treating and grinding. I bet the guy with the camshaft factory who
> >>> adapted
> >>> > LCNC to control induction heat treaters would be interested in this.
> >>> >
> >>> > On Wednesday, October 21, 2020, 9:35:26 PM MDT, Sam Sokolik <
> >>> > samco...@gmail.com> wrote:
> >>> >  https://www.youtube.com/watch?v=-4sKHBh6rDk
> >>> > ___
> >>> > Emc-users mailing list
> >>> > Emc-users@lists.sourceforge.net
> >>> > https://lists.sourceforge.net/lists/listinfo/emc-users
> >>> >
> >>>
> >>> ___
> >>> Emc-users mailing list
> >>> Emc-users@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/emc-users
> >>>
> >>
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Now do I have a bad card?

2020-10-22 Thread Peter C. Wallace

On Thu, 22 Oct 2020, Gene Heskett wrote:


Date: Thu, 22 Oct 2020 04:41:19 -0400
From: Gene Heskett 
Reply-To: "Enhanced Machine Controller (EMC)"

To: emc-users@lists.sourceforge.net
Subject: Re: [Emc-users] Now do I have a bad card?

On Wednesday 21 October 2020 23:05:16 Peter C. Wallace wrote:


On Wed, 21 Oct 2020, Gene Heskett wrote:

Date: Wed, 21 Oct 2020 21:06:06 -0400
From: Gene Heskett 
Reply-To: "Enhanced Machine Controller (EMC)"

To: emc-users@lists.sourceforge.net
Subject: Re: [Emc-users] Now do I have a bad card?

On Wednesday 21 October 2020 20:21:30 Peter C. Wallace wrote:
[...]


sudo mesaflash --device 5i25 --readhmid


gene@GO704:~/linuxcnc$ sudo mesaflash --device 5i25 --readhmid
[sudo] password for gene:
Configuration Name: HOSTMOT2

General configuration information:

 BoardName : MESA5I25
 FPGA Size: 9 KGates
 FPGA Pins: 144
 Number of IO Ports: 2
 Width of one I/O port: 17
 Clock Low frequency: 33. MHz
 Clock High frequency: 200. MHz
 IDROM Type: 3
 Instance Stride 0: 4
 Instance Stride 1: 64
 Register Stride 0: 256
 Register Stride 1: 256

Modules in configuration:

 Module: WatchDog
 There are 1 of WatchDog in configuration
 Version: 0
 Registers: 3
 BaseAddress: 0C00
 ClockFrequency: 33.333 MHz
 Register Stride: 256 bytes
 Instance Stride: 4 bytes

 Module: IOPort
 There are 2 of IOPort in configuration
 Version: 0
 Registers: 5
 BaseAddress: 1000
 ClockFrequency: 33.333 MHz
 Register Stride: 256 bytes
 Instance Stride: 4 bytes

 Module: QCount
 There are 2 of QCount in configuration
 Version: 2
 Registers: 5
 BaseAddress: 3000
 ClockFrequency: 33.333 MHz
 Register Stride: 256 bytes
 Instance Stride: 4 bytes

 Module: SSerial
 There are 1 of SSerial in configuration
 Version: 0
 Registers: 6
 BaseAddress: 5B00
 ClockFrequency: 33.333 MHz
 Register Stride: 256 bytes
 Instance Stride: 64 bytes

 Module: PWM
 There are 2 of PWM in configuration
 Version: 0
 Registers: 5
 BaseAddress: 4100
 ClockFrequency: 200.000 MHz
 Register Stride: 256 bytes
 Instance Stride: 4 bytes

 Module: StepGen
 There are 9 of StepGen in configuration
 Version: 2
 Registers: 10
 BaseAddress: 2000
 ClockFrequency: 33.333 MHz
 Register Stride: 256 bytes
 Instance Stride: 4 bytes

 Module: LED
 There are 1 of LED in configuration
 Version: 0
 Registers: 1
 BaseAddress: 0200
 ClockFrequency: 33.333 MHz
 Register Stride: 256 bytes
 Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P3
Pin#  I/O   Pri. funcSec. func   Chan  Pin func
Pin Dir

1  0   IOPort   StepGen  0Dir/Table2
(Out) 14  1   IOPort   StepGen  0
Step/Table1 (Out) 2  2   IOPort   StepGen  1
Dir/Table2  (Out) 15  3   IOPort   StepGen
1 Step/Table1 (Out) 3  4   IOPort   StepGen 2
Dir/Table2  (Out) 16  5   IOPort   StepGen 2
Step/Table1 (Out) 4  6   IOPort   StepGen 3
Dir/Table2  (Out) 17  7   IOPort   StepGen 3
Step/Table1 (Out) 5  8   IOPort StepGen  4
Dir/Table2  (Out) 6  9   IOPort StepGen  4
Step/Table1 (Out) 7 10   IOPort SSerial  0
TXData1 (Out) 8 11 IOPort   SSerial  0
RXData1 (In) 9 12 IOPort   SSerial  0
TXData2 (Out) 10 13   IOPort   SSerial  0
RXData2 (In) 11 14   IOPort   QCount 0
Quad-IDX(In) 12 15   IOPort   QCount 0
Quad-B (In) 13 16   IOPort   QCount 0Quad-A
(In)

IO Connections for P2
Pin#  I/O   Pri. funcSec. func   Chan  Pin func
Pin Dir

1 17   IOPort   StepGen  5Dir/Table2
(Out) 14 18   IOPort   StepGen  5
Step/Table1 (Out) 2 19   IOPort   StepGen  6
Dir/Table2  (Out) 15 20   IOPort   StepGen
6 Step/Table1 (Out) 3 21   IOPort   StepGen 7
Dir/Table2  (Out) 16 22   IOPort   StepGen 7
Step/Table1 (Out) 4 23   IOPort   StepGen 8
Dir/Table2  (Out) 17 24   IOPort   StepGen 8
Step/Table1 (Out) 5 25   IOPort   PWM 0PWM
(Out) 6 26   IOPort PWM  0/Enable
(Out) 7 27   IOPort PWM  0Dir (Out) 8
   28 IOPort SSerial  0TXData3 (Out) 9 29
IOPort SSerial  0TXEn3 (Out) 10 30   IOPort
SSerial  0
RXData3 (In) 11 31   IOPort   QCount   1
 Quad-IDX(In) 12 32   IOPort   QCount
1 Quad-B (In) 13 33   IOPort   QCount   1
Quad-A (In)

gene@GO704:~/linuxcnc$


Yep that looks like a 7I76+7I78 configuration
with just one PWMGen for the 7I78 on P2


but this is the load line that generated that dmesg:
loadrt hm2_pci  config="num_encoders=2 num_pwmgens=2
num_stepgens=3"


Thats a pinout file not a dmesg log


Its the output of the --readhmid command you asked for. I just
copy pasted it all, including the mesaflash command you can see at
the top of 

Re: [Emc-users] spindle syncing arbitrary shapes.. Yes please...

2020-10-22 Thread Leonardo Marsaglia
I must add, that lately we're considering making the camshafts this way:

https://www.youtube.com/watch?v=kkHgf5SSsAQ

This would eliminate the roughing process at all.

El jue., 22 oct. 2020 a las 9:35, Leonardo Marsaglia ()
escribió:

> Looks like this would be perfect for roughing camshafts prior to heat
>> treating and grinding. I bet the guy with the camshaft factory who adapted
>> LCNC to control induction heat treaters would be interested in this.
>
>
> This is what I achieved so far Gregg
>
> https://www.youtube.com/watch?v=xjBXa6RHSPQ
>
> The thing is, we have an old landis grinder that can rough those cams in
> about 25 seconds (1.5 mm of material to remove in the radius) per lobe
> (using 60 grit grinding wheel and dessing it with a high feed). So, we are
> waiting until we have a little more time to make a live tooling gig to
> rough them (I already have that on paper but didn't have the time to
> implement it yet).
>
> Without live tooling it's not that practical to rough the lobes/cams for
> production.
>
> El jue., 22 oct. 2020 a las 9:27, Leonardo Marsaglia (<
> ldmarsag...@gmail.com>) escribió:
>
>> Yep he is in Chile.
>>
>>
>> Argentina actually. It's similar, but out shores face the atlantic
>> instead of the pacific. Also we're closer of being an eleventh world
>> country than they are...
>>
>> El jue., 22 oct. 2020 a las 3:08, andrew beck ()
>> escribió:
>>
>>> Yep he is in Chile.
>>>
>>>
>>>
>>> On Thu, Oct 22, 2020, 6:47 PM Gregg Eshelman via Emc-users <
>>> emc-users@lists.sourceforge.net> wrote:
>>>
>>> > Looks like this would be perfect for roughing camshafts prior to heat
>>> > treating and grinding. I bet the guy with the camshaft factory who
>>> adapted
>>> > LCNC to control induction heat treaters would be interested in this.
>>> >
>>> > On Wednesday, October 21, 2020, 9:35:26 PM MDT, Sam Sokolik <
>>> > samco...@gmail.com> wrote:
>>> >  https://www.youtube.com/watch?v=-4sKHBh6rDk
>>> > ___
>>> > Emc-users mailing list
>>> > Emc-users@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/emc-users
>>> >
>>>
>>> ___
>>> Emc-users mailing list
>>> Emc-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-users
>>>
>>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] spindle syncing arbitrary shapes.. Yes please...

2020-10-22 Thread Leonardo Marsaglia
>
> Looks like this would be perfect for roughing camshafts prior to heat
> treating and grinding. I bet the guy with the camshaft factory who adapted
> LCNC to control induction heat treaters would be interested in this.


This is what I achieved so far Gregg

https://www.youtube.com/watch?v=xjBXa6RHSPQ

The thing is, we have an old landis grinder that can rough those cams in
about 25 seconds (1.5 mm of material to remove in the radius) per lobe
(using 60 grit grinding wheel and dessing it with a high feed). So, we are
waiting until we have a little more time to make a live tooling gig to
rough them (I already have that on paper but didn't have the time to
implement it yet).

Without live tooling it's not that practical to rough the lobes/cams for
production.

El jue., 22 oct. 2020 a las 9:27, Leonardo Marsaglia ()
escribió:

> Yep he is in Chile.
>
>
> Argentina actually. It's similar, but out shores face the atlantic instead
> of the pacific. Also we're closer of being an eleventh world country than
> they are...
>
> El jue., 22 oct. 2020 a las 3:08, andrew beck ()
> escribió:
>
>> Yep he is in Chile.
>>
>>
>>
>> On Thu, Oct 22, 2020, 6:47 PM Gregg Eshelman via Emc-users <
>> emc-users@lists.sourceforge.net> wrote:
>>
>> > Looks like this would be perfect for roughing camshafts prior to heat
>> > treating and grinding. I bet the guy with the camshaft factory who
>> adapted
>> > LCNC to control induction heat treaters would be interested in this.
>> >
>> > On Wednesday, October 21, 2020, 9:35:26 PM MDT, Sam Sokolik <
>> > samco...@gmail.com> wrote:
>> >  https://www.youtube.com/watch?v=-4sKHBh6rDk
>> > ___
>> > Emc-users mailing list
>> > Emc-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/emc-users
>> >
>>
>> ___
>> Emc-users mailing list
>> Emc-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-users
>>
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] spindle syncing arbitrary shapes.. Yes please...

2020-10-22 Thread Leonardo Marsaglia
>
> Yep he is in Chile.


Argentina actually. It's similar, but out shores face the atlantic instead
of the pacific. Also we're closer of being an eleventh world country than
they are...

El jue., 22 oct. 2020 a las 3:08, andrew beck ()
escribió:

> Yep he is in Chile.
>
>
>
> On Thu, Oct 22, 2020, 6:47 PM Gregg Eshelman via Emc-users <
> emc-users@lists.sourceforge.net> wrote:
>
> > Looks like this would be perfect for roughing camshafts prior to heat
> > treating and grinding. I bet the guy with the camshaft factory who
> adapted
> > LCNC to control induction heat treaters would be interested in this.
> >
> > On Wednesday, October 21, 2020, 9:35:26 PM MDT, Sam Sokolik <
> > samco...@gmail.com> wrote:
> >  https://www.youtube.com/watch?v=-4sKHBh6rDk
> > ___
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-users
> >
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] mesaflash problem, Peter plz comment

2020-10-22 Thread andy pugh
On Thu, 22 Oct 2020 at 02:00, Gene Heskett  wrote:

> No, that steers the pwm which modulates the bottom half of the bridge,
> and not externally separated, both sides on these full H bridge cards.

The step outputs are a differential pair, not PWM and /PWM. I am not
sure if that is a real distinction.
But you might need to be careful of the common-mode voltage limits of
the differential pair driver on the 7i76.

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] spindle syncing arbitrary shapes.. Yes please...

2020-10-22 Thread Gene Heskett
On Wednesday 21 October 2020 23:32:17 Sam Sokolik wrote:

> https://www.youtube.com/watch?v=-4sKHBh6rDk
>
Sam is haveing way too much fun again.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


Re: [Emc-users] Now do I have a bad card?

2020-10-22 Thread Gene Heskett
On Wednesday 21 October 2020 23:05:16 Peter C. Wallace wrote:

> On Wed, 21 Oct 2020, Gene Heskett wrote:
> > Date: Wed, 21 Oct 2020 21:06:06 -0400
> > From: Gene Heskett 
> > Reply-To: "Enhanced Machine Controller (EMC)"
> > 
> > To: emc-users@lists.sourceforge.net
> > Subject: Re: [Emc-users] Now do I have a bad card?
> >
> > On Wednesday 21 October 2020 20:21:30 Peter C. Wallace wrote:
> > [...]
> >
>  sudo mesaflash --device 5i25 --readhmid
> >>>
> >>> gene@GO704:~/linuxcnc$ sudo mesaflash --device 5i25 --readhmid
> >>> [sudo] password for gene:
> >>> Configuration Name: HOSTMOT2
> >>>
> >>> General configuration information:
> >>>
> >>>  BoardName : MESA5I25
> >>>  FPGA Size: 9 KGates
> >>>  FPGA Pins: 144
> >>>  Number of IO Ports: 2
> >>>  Width of one I/O port: 17
> >>>  Clock Low frequency: 33. MHz
> >>>  Clock High frequency: 200. MHz
> >>>  IDROM Type: 3
> >>>  Instance Stride 0: 4
> >>>  Instance Stride 1: 64
> >>>  Register Stride 0: 256
> >>>  Register Stride 1: 256
> >>>
> >>> Modules in configuration:
> >>>
> >>>  Module: WatchDog
> >>>  There are 1 of WatchDog in configuration
> >>>  Version: 0
> >>>  Registers: 3
> >>>  BaseAddress: 0C00
> >>>  ClockFrequency: 33.333 MHz
> >>>  Register Stride: 256 bytes
> >>>  Instance Stride: 4 bytes
> >>>
> >>>  Module: IOPort
> >>>  There are 2 of IOPort in configuration
> >>>  Version: 0
> >>>  Registers: 5
> >>>  BaseAddress: 1000
> >>>  ClockFrequency: 33.333 MHz
> >>>  Register Stride: 256 bytes
> >>>  Instance Stride: 4 bytes
> >>>
> >>>  Module: QCount
> >>>  There are 2 of QCount in configuration
> >>>  Version: 2
> >>>  Registers: 5
> >>>  BaseAddress: 3000
> >>>  ClockFrequency: 33.333 MHz
> >>>  Register Stride: 256 bytes
> >>>  Instance Stride: 4 bytes
> >>>
> >>>  Module: SSerial
> >>>  There are 1 of SSerial in configuration
> >>>  Version: 0
> >>>  Registers: 6
> >>>  BaseAddress: 5B00
> >>>  ClockFrequency: 33.333 MHz
> >>>  Register Stride: 256 bytes
> >>>  Instance Stride: 64 bytes
> >>>
> >>>  Module: PWM
> >>>  There are 2 of PWM in configuration
> >>>  Version: 0
> >>>  Registers: 5
> >>>  BaseAddress: 4100
> >>>  ClockFrequency: 200.000 MHz
> >>>  Register Stride: 256 bytes
> >>>  Instance Stride: 4 bytes
> >>>
> >>>  Module: StepGen
> >>>  There are 9 of StepGen in configuration
> >>>  Version: 2
> >>>  Registers: 10
> >>>  BaseAddress: 2000
> >>>  ClockFrequency: 33.333 MHz
> >>>  Register Stride: 256 bytes
> >>>  Instance Stride: 4 bytes
> >>>
> >>>  Module: LED
> >>>  There are 1 of LED in configuration
> >>>  Version: 0
> >>>  Registers: 1
> >>>  BaseAddress: 0200
> >>>  ClockFrequency: 33.333 MHz
> >>>  Register Stride: 256 bytes
> >>>  Instance Stride: 4 bytes
> >>>
> >>> Configuration pin-out:
> >>>
> >>> IO Connections for P3
> >>> Pin#  I/O   Pri. funcSec. func   Chan  Pin func
> >>> Pin Dir
> >>>
> >>> 1  0   IOPort   StepGen  0Dir/Table2
> >>> (Out) 14  1   IOPort   StepGen  0
> >>> Step/Table1 (Out) 2  2   IOPort   StepGen  1
> >>> Dir/Table2  (Out) 15  3   IOPort   StepGen
> >>> 1 Step/Table1 (Out) 3  4   IOPort   StepGen 2
> >>> Dir/Table2  (Out) 16  5   IOPort   StepGen 2
> >>> Step/Table1 (Out) 4  6   IOPort   StepGen 3
> >>> Dir/Table2  (Out) 17  7   IOPort   StepGen 3
> >>> Step/Table1 (Out) 5  8   IOPort StepGen  4
> >>> Dir/Table2  (Out) 6  9   IOPort StepGen  4
> >>> Step/Table1 (Out) 7 10   IOPort SSerial  0
> >>> TXData1 (Out) 8 11 IOPort   SSerial  0
> >>> RXData1 (In) 9 12 IOPort   SSerial  0
> >>> TXData2 (Out) 10 13   IOPort   SSerial  0
> >>> RXData2 (In) 11 14   IOPort   QCount 0
> >>> Quad-IDX(In) 12 15   IOPort   QCount 0
> >>> Quad-B (In) 13 16   IOPort   QCount 0Quad-A
> >>> (In)
> >>>
> >>> IO Connections for P2
> >>> Pin#  I/O   Pri. funcSec. func   Chan  Pin func
> >>> Pin Dir
> >>>
> >>> 1 17   IOPort   StepGen  5Dir/Table2
> >>> (Out) 14 18   IOPort   StepGen  5
> >>> Step/Table1 (Out) 2 19   IOPort   StepGen  6
> >>> Dir/Table2  (Out) 15 20   IOPort   StepGen
> >>> 6 Step/Table1 (Out) 3 21   IOPort   StepGen 7
> >>> Dir/Table2  (Out) 16 22   IOPort   StepGen 7
> >>> Step/Table1 (Out) 4 23   IOPort   

Re: [Emc-users] spindle syncing arbitrary shapes.. Yes please...

2020-10-22 Thread andrew beck
Yep he is in Chile.



On Thu, Oct 22, 2020, 6:47 PM Gregg Eshelman via Emc-users <
emc-users@lists.sourceforge.net> wrote:

> Looks like this would be perfect for roughing camshafts prior to heat
> treating and grinding. I bet the guy with the camshaft factory who adapted
> LCNC to control induction heat treaters would be interested in this.
>
> On Wednesday, October 21, 2020, 9:35:26 PM MDT, Sam Sokolik <
> samco...@gmail.com> wrote:
>  https://www.youtube.com/watch?v=-4sKHBh6rDk
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users