Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On 08.10.14 09:06, John Dammeyer wrote: Windows 3.11 to Win95 orphaned the product two months after I bought it. ... I also own a 32 channel logic analyzer pod that runs off the parallel port. Last time I was using it was WIN-98 or maybe XP. I wrote custom DLL code for it to do CAN bus decoding from the bit stream back in 2001. I haven't tried it with WIN-7. Don't know if it will work. ... Just an observation that these little pocket scopes and logic analyzers have a very short lifetime. Yup, when the host is M$-based, that's particularly true. My linux-hosted oscilloscope/logic_analyser is ethernet connected, and the host software still runs on current linux versions, with new downloads a couple of mouse clicks away. On 08.10.14 16:55, Ralph Stirling wrote: It gets more complicated, though. We have a lab full of Tek logic analyzers (about 10yo if I recall). They had a retail value of about $11K each I think, although we got a discount. We discovered after we bought them that they ran on Windows 2000. Last year we persuaded Tek to give us the drivers that would work on XP, and upgraded the LA's to XP. Don't know how many more times we can make that happen. With linux-based stuff, the norm is to put the host software on a webpage, and let you upgrade at will. For the one I have, it's http://my.bitscope.com/download/ where you just select OS and host architecture, then snarf it for nix. Providing ongoing value in a product is probably an advantage in staying in business, I think. But if the supplier were to go west, I'd still remain on air for as long as the source code for a compatible linux version can compile on a piece of hardware I can buy. My suspicion is that I'll wear out before that happens. For just a logic analyser, an open source product, like the one mentioned upthread, provides complete vendor independence. Erik -- The use of Microsoft crippleware systems is a sin that carries with it its own punishment. -- Tom Christiansen in 6bo3fr$pj8$5...@csnews.cs.colorado.edu (No relation) -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On 9 October 2014 07:02, Erik Christiansen dva...@internode.on.net wrote: Just an observation that these little pocket scopes and logic analyzers have a very short lifetime. Yup, when the host is M$-based, that's particularly true. That seems a little unfair. How long did MS support XP for? It was released in 2001 and support ended in 2014. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On 08/10/14 23:05, John Dammeyer wrote: Sorry. 3GHz. Not MHz. Something that popped up on my in box ... https://www.coolcomponents.co.uk/rf-explorer-signal-generator-rfe6gen.html ... 24MHz to 6GHz controlled by the PC :) -- Lester Caine - G8HFL - Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On 09.10.14 10:51, andy pugh wrote: On 9 October 2014 07:02, Erik Christiansen dva...@internode.on.net wrote: Just an observation that these little pocket scopes and logic analyzers have a very short lifetime. Yup, when the host is M$-based, that's particularly true. That seems a little unfair. How long did MS support XP for? It was released in 2001 and support ended in 2014. And it ought to be possible to run the old OS on the old hardware until it succumbs to entropy. Buying one or two old hardware mobos, recently manufactured, should then add up to another decade, with a bit of luck. However, it's not as future proof as having the source code to the OS, and being able to do a backport yourself (or pay someone to), if necessary. With an ethernet connection, and a linux hosted app, the one I use is really only reliant on linux system calls, X11, and TCP/IP, I figure. Oh, and a DLL, I remember. In contrast to relying on both M$ and the gadget vendor continuing support, the exposure is halved when only the latter needs to continue, because linux distros abound, and loss of any one has no great effect. Erik -- I didn't marry him for his money, I divorced him for it. - Seen on a wall plaque in a gift shop. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Thoughts on a Python script to calculate estimated run time, for G code and my first hacked sub routine
If you need the exact time to run a file create a simulator with the same acceleration and velocity settings as your machine. Add the time component to the simulator then run your file. JT On 10/8/2014 10:01 AM, Schooner wrote: First Q From Axis File Properties Brings up the properties of the currently loaded gcode including estimated run time Always underestimates as it takes no account of time used in acceleration and deceleration to/from the required Feed speed regards -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] In/Out pin on Hostmot2 Encoder component
Seb - thank you HAL IO pins are strange and apparently very rare beasts which don't map easily in my mind to the wire -- signal analogy. If we review HAL (and its documentation) I wonder if IO pins should be deprecated. A two signal handshake would seem more transparent and allow general interconnection of components rather a special purpose connection such as is used between encoder and axis for resetting counts. Thoughts anyone - perhaps I have totally missed the point. John Prentice -Original Message- From: Sebastian Kuzminsky [mailto:s...@highlab.com] Sent: 08 October 2014 22:25 To: Enhanced Machine Controller (EMC) Subject: Re: [Emc-users] In/Out pin on Hostmot2 Encoder component On 10/8/14 3:18 PM, John Prentice (FS) wrote: Can anyone give an example snippet of HAL to explain how one might exploit this. I cannot wire a signal to set it True (not surprisingly as it is an output). I must be missing something obvious here and need guidance. Look at the hm2-servo sample config: http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=configs/by_interface/ mesa/hm2-servo/hm2-servo.hal;h=50a630a0ab84497fbef5c2927a20acfa3510fa56;hb=r efs/heads/master#l231 -- Sebastian Kuzminsky -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] In/Out pin on Hostmot2 Encoder component
On Thu, Oct 9, 2014, at 09:46 AM, John Prentice (FS) wrote: Seb - thank you HAL IO pins are strange and apparently very rare beasts which don't map easily in my mind to the wire -- signal analogy. To extend the wire-signal analogy, I think of I/O pins as tri-stateable signals. They have two possible uses: 1) as a one-wire handshake, where component A asserts the signal to request an action, and component B clears it when the action is done. 2) to allow multiple components to drive a signal signal. #1 is the index-enable case. It could be replaced by a two-wire handshake, but motion and all the encoder drivers would need to make the change at the same time, and it would require changing existing configurations. There is one caveat to that replacement. The existing one-wire handshake works even across thread boundaries. In other words, a component running in one thread (or even in user space) can request an index capture from an encoder driver running in a faster thread, and be assured that the encoder driver will capture the index position once and only once. That is because the very act of acknowleding the request also clears the request. If the handshake was split into two wires, a request and an acknowledge, then the requestor MUST see the acknowledge and remove the request before a second index pulse occurs, or the index position will be captured twice. In our normal configurations, the requestor is motion, and it is running in the same thread as the encoder driver, so this doesn't matter. But it is very handy to be able to test an encoder by manually setting the request and seeing that when an index pulse occurs the request is cleared. If doing things manually, there is a very good chance that two (or more) index pulses will arrive before you manually clear the request. #2 is not currently used by LinuxCNC to my knowledge. One example that I had in mind for it was a FAULT or ESTOP signal that could be driven by any of multiple components to force a shutdown, without having to OR together a bunch of individual signals, one from each module. This is more like an open-collector than a tri-state output. Each component that might detect a fault would drive its I/O pin to the faulted state when a fault condition exists, and would not drive it at all otherwise. One component would be responsible for driving the signal to the not faulted state only one time when the user attempts to reset the fault. If we review HAL (and its documentation) I wonder if IO pins should be deprecated. A two signal handshake would seem more transparent and allow general interconnection of components rather a special purpose connection such as is used between encoder and axis for resetting counts. Thoughts anyone - perhaps I have totally missed the point. John Prentice -Original Message- From: Sebastian Kuzminsky [mailto:s...@highlab.com] Sent: 08 October 2014 22:25 To: Enhanced Machine Controller (EMC) Subject: Re: [Emc-users] In/Out pin on Hostmot2 Encoder component On 10/8/14 3:18 PM, John Prentice (FS) wrote: Can anyone give an example snippet of HAL to explain how one might exploit this. I cannot wire a signal to set it True (not surprisingly as it is an output). I must be missing something obvious here and need guidance. Look at the hm2-servo sample config: http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=configs/by_interface/ mesa/hm2-servo/hm2-servo.hal;h=50a630a0ab84497fbef5c2927a20acfa3510fa56;hb=r efs/heads/master#l231 -- Sebastian Kuzminsky -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- John Kasunich jmkasun...@fastmail.fm -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0
Re: [Emc-users] In/Out pin on Hostmot2 Encoder component
On Thursday 09 October 2014 10:23:30 John Kasunich did opine And Gene did reply: On Thu, Oct 9, 2014, at 09:46 AM, John Prentice (FS) wrote: Seb - thank you HAL IO pins are strange and apparently very rare beasts which don't map easily in my mind to the wire -- signal analogy. To extend the wire-signal analogy, I think of I/O pins as tri-stateable signals. They have two possible uses: 1) as a one-wire handshake, where component A asserts the signal to request an action, and component B clears it when the action is done. 2) to allow multiple components to drive a signal signal. #1 is the index-enable case. It could be replaced by a two-wire handshake, but motion and all the encoder drivers would need to make the change at the same time, and it would require changing existing configurations. There is one caveat to that replacement. The existing one-wire handshake works even across thread boundaries. In other words, a component running in one thread (or even in user space) can request an index capture from an encoder driver running in a faster thread, and be assured that the encoder driver will capture the index position once and only once. That is because the very act of acknowleding the request also clears the request. If the handshake was split into two wires, a request and an acknowledge, then the requestor MUST see the acknowledge and remove the request before a second index pulse occurs, or the index position will be captured twice. In our normal configurations, the requestor is motion, and it is running in the same thread as the encoder driver, so this doesn't matter. But it is very handy to be able to test an encoder by manually setting the request and seeing that when an index pulse occurs the request is cleared. If doing things manually, there is a very good chance that two (or more) index pulses will arrive before you manually clear the request. #2 is not currently used by LinuxCNC to my knowledge. One example that I had in mind for it was a FAULT or ESTOP signal that could be driven by any of multiple components to force a shutdown, without having to OR together a bunch of individual signals, one from each module. This is more like an open-collector than a tri-state output. Each component that might detect a fault would drive its I/O pin to the faulted state when a fault condition exists, and would not drive it at all otherwise. One component would be responsible for driving the signal to the not faulted state only one time when the user attempts to reset the fault. Tongue firmly in cheek, there is something terribly wrong here, John. I understood this perfectly on the first read! The above text should be incorporated into the Integrators Manual pdf's as it is not explained as clearly as you have done above. If we review HAL (and its documentation) I wonder if IO pins should be deprecated. A two signal handshake would seem more transparent and allow general interconnection of components rather a special purpose connection such as is used between encoder and axis for resetting counts. Thoughts anyone - perhaps I have totally missed the point. John Prentice -Original Message- From: Sebastian Kuzminsky [mailto:s...@highlab.com] Sent: 08 October 2014 22:25 To: Enhanced Machine Controller (EMC) Subject: Re: [Emc-users] In/Out pin on Hostmot2 Encoder component On 10/8/14 3:18 PM, John Prentice (FS) wrote: Can anyone give an example snippet of HAL to explain how one might exploit this. I cannot wire a signal to set it True (not surprisingly as it is an output). I must be missing something obvious here and need guidance. Look at the hm2-servo sample config: http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=configs/by_int erface/ mesa/hm2-servo/hm2-servo.hal;h=50a630a0ab84497fbef5c2927a20acfa3510f a56;hb=r efs/heads/master#l231 -- Sebastian Kuzminsky 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) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
The Spectrum analyzer and SWR Bridge allow signal generation and as a tracking generator can also analyze cables. It's a sweet tool. http://www.rohde-schwarz.com/en/product/fsh3-6-18-options_63490-7578.html http://www.rohde-schwarz.com/en/product/fshz2-productstartpage_63493-7781.ht ml John -Original Message- From: Lester Caine [mailto:les...@lsces.co.uk] Sent: October-09-14 3:28 AM To: emc-users@lists.sourceforge.net Subject: Re: [Emc-users] Oscilloscope + logic analyzer (PC based) On 08/10/14 23:05, John Dammeyer wrote: Sorry. 3GHz. Not MHz. Something that popped up on my in box ... https://www.coolcomponents.co.uk/rf-explorer-signal-generator- rfe6gen.html ... 24MHz to 6GHz controlled by the PC :) -- Lester Caine - G8HFL - Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.cl ktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
I can still get parts for my Sears Drill Press purchased in 1983. I'm pretty sure I can fit new bearings and other pieces onto my 1935 Delta Band Saw. Granted my South Bend 10L is no longer made it's still repairable and it was originally sold to the Ordinance Officer Edmonton in 1942. The concept that a tool sold in 2001 and can no longer be repaired or perhaps safely used after 2014 is a modern concept that bothers me a lot. I read somewhere that this century will go down in history as the most 'undocumented' century in human history when historians look back 500 or 1000 years from now. If you think that's silly try and read an 8 floppy disk or even an quad density 3.5 disk that is 15 years old. The usual result, especially from Win7 is This floppy is not formatted. Would you like it formatted now? CD ROMs have a life. The information does degrade. When was the last time you pulled out that CD with pictures of your children's birth or 1st birthday and rewrote them to a new CD. The sheer volume of photographs makes organizing them tedious and therefore unlikely. When you die will your kids methodically go through them all and re-organize into their photo albums? Or will the CDs, and the plastic jewel cases be tossed into recycling. One of the advantages of Windows over the Apple is that with every revision change they maintained a certain amount of backwards compatibility. With Apple an new revision will often 'break' existing applications and if that software company is no longer in business too bad. And traditionally you cannot roll back a revision on Apple hardware. Linux is even worse. Just recompile the source code is the mantra. The moving target of Linux distributions is laughable for the longevity of any product. Were it different and not geek programmer oriented the IBM PC hardware and Apple hardware would both be running Linux distributions. Android may still win this battle but it's hard to say if it's linux underpants will be soiled by the runs at some point too. John Dammeyer -Original Message- From: andy pugh [mailto:bodge...@gmail.com] Sent: October-09-14 2:51 AM To: Enhanced Machine Controller (EMC) Subject: Re: [Emc-users] Oscilloscope + logic analyzer (PC based) On 9 October 2014 07:02, Erik Christiansen dva...@internode.on.net wrote: Just an observation that these little pocket scopes and logic analyzers have a very short lifetime. Yup, when the host is M$-based, that's particularly true. That seems a little unfair. How long did MS support XP for? It was released in 2001 and support ended in 2014. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.cl ktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
try a new cellular phone , top of the range model , 10 months in ...wont switch on so i sent back under warrenty ,, got it back in bits after 4 weeks ... their not able to repair it ... un economic to repair ! .. and they say although it's in warrenty they cant cover it .. i'd stick with your saw and other metallic objects , tech stuff if far to volatile to touch On 9 October 2014 17:33, John Dammeyer jo...@autoartisans.com wrote: I can still get parts for my Sears Drill Press purchased in 1983. I'm pretty sure I can fit new bearings and other pieces onto my 1935 Delta Band Saw. Granted my South Bend 10L is no longer made it's still repairable and it was originally sold to the Ordinance Officer Edmonton in 1942. The concept that a tool sold in 2001 and can no longer be repaired or perhaps safely used after 2014 is a modern concept that bothers me a lot. I read somewhere that this century will go down in history as the most 'undocumented' century in human history when historians look back 500 or 1000 years from now. If you think that's silly try and read an 8 floppy disk or even an quad density 3.5 disk that is 15 years old. The usual result, especially from Win7 is This floppy is not formatted. Would you like it formatted now? CD ROMs have a life. The information does degrade. When was the last time you pulled out that CD with pictures of your children's birth or 1st birthday and rewrote them to a new CD. The sheer volume of photographs makes organizing them tedious and therefore unlikely. When you die will your kids methodically go through them all and re-organize into their photo albums? Or will the CDs, and the plastic jewel cases be tossed into recycling. One of the advantages of Windows over the Apple is that with every revision change they maintained a certain amount of backwards compatibility. With Apple an new revision will often 'break' existing applications and if that software company is no longer in business too bad. And traditionally you cannot roll back a revision on Apple hardware. Linux is even worse. Just recompile the source code is the mantra. The moving target of Linux distributions is laughable for the longevity of any product. Were it different and not geek programmer oriented the IBM PC hardware and Apple hardware would both be running Linux distributions. Android may still win this battle but it's hard to say if it's linux underpants will be soiled by the runs at some point too. John Dammeyer -Original Message- From: andy pugh [mailto:bodge...@gmail.com] Sent: October-09-14 2:51 AM To: Enhanced Machine Controller (EMC) Subject: Re: [Emc-users] Oscilloscope + logic analyzer (PC based) On 9 October 2014 07:02, Erik Christiansen dva...@internode.on.net wrote: Just an observation that these little pocket scopes and logic analyzers have a very short lifetime. Yup, when the host is M$-based, that's particularly true. That seems a little unfair. How long did MS support XP for? It was released in 2001 and support ended in 2014. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.cl ktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On 9 October 2014 17:33, John Dammeyer jo...@autoartisans.com wrote: I can still get parts for my Sears Drill Press purchased in 1983. I'm pretty sure I can fit new bearings and other pieces onto my 1935 Delta Band Saw. Granted my South Bend 10L is no longer made it's still repairable and it was originally sold to the Ordinance Officer Edmonton in 1942. I was soldering the radiator of a 1916 Dennis back together last night (until 1am) and today I rode my 1921 Ner-a-Car. But in both cases I had to compile the parts from source. Often using LinuxCNC. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
CD ROMs have a life. The information does degrade. When was the last time you pulled out that CD with pictures of your children's birth or 1st birthday and rewrote them to a new CD. The sheer volume of photographs makes organizing them tedious and therefore unlikely. When you die will your kids methodically go through them all and re-organize into their photo albums? Or will the CDs, and the plastic jewel cases be tossed into recycling. And on top of that, the printed photos will themselves have faded or spontaneously combusted/composted due to some weird chemical action over time. Even the archival quality inks (and who uses them for family snaps?) only have a /simulated/ lifetime that hasn't been put to the test yet - its just hopeful extrapolation from accelerated heat UV exposure testing. I had occasion to re-burn some old discs a while ago, several were from the era of single speed CDRs, and I foolishly put them in a drive that can read at 52x. Second disc in literally exploded. Very loudly. I thought it was the PSU caps so leapt up and yanked the power lead. When I dismantled the drive it was full of metallic confetti and SMALL shards of polycarbonate, none bigger than a thumbnail. It totally banjaxed the drive, I was quite surprised at the amount of energy in a small spinning disc. The fragments left deep gouges in the CD tray. Luckily I had a later backup which I made sure to read at 2x. Now I mainly use a stack of obsolete HDDs and copy from one to the other every few years. I use a fair few 35GB Rev discs too, and give sets to family to stash. Hard copy is the only sure way, preferably chiselled 6 into a granite cliff face... -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] In/Out pin on Hostmot2 Encoder component
John, thank you for your elaboration. Two points interleaved below: snip To extend the wire-signal analogy, I think of I/O pins as tri-stateable signals. I don't really get this analogy as there is also a memory hiding somewhere for when everyone it tri-stated. It feels more like a wire with some sort of latch with weak pull-up (and perhaps pull-downs?) on its output. I.e. it remembers the state imposed on it by anything bussed onto it when the driver turns on a strong 3-state buffer They have two possible uses: 1) as a one-wire handshake, where component A asserts the signal to request an action, and component B clears it when the action is done. 2) to allow multiple components to drive a signal signal. #1 is the index-enable case. It could be replaced by a two-wire handshake, but motion and all the encoder drivers would need to make the change at the same time, and it would require changing existing configurations. There is one caveat to that replacement. The existing one-wire handshake works even across thread boundaries. In other words, a component running in one thread (or even in user space) can request an index capture from an encoder driver running in a faster thread, and be assured that the encoder driver will capture the index position once and only once. That is because the very act of acknowleding the request also clears the request. If the handshake was split into two wires, a request and an acknowledge, then the requestor MUST see the acknowledge and remove the request before a second index pulse occurs, or the index position will be captured twice. In our normal configurations, the requestor is motion, and it is running in the same thread as the encoder driver, so this doesn't matter. But it is very handy to be able to test an encoder by manually setting the request and seeing that when an index pulse occurs the request is cleared. If doing things manually, there is a very good chance that two (or more) index pulses will arrive before you manually clear the request. It was actually trying to do a manual test that got me into this trouble. I think one needs a special comp with an IO pin to connect to the index-enable to something like a pyVCP button. Is the fundamental concept we want for REQ not an edge-input? The receiver latches this and clears the latch when the action (e.g. count reset by the index) is performed. The requester then has to see an ACK signal, deal with the data, and eventually drop and re-raise the REQ. #2 is not currently used by LinuxCNC to my knowledge. One example that I had in mind for it was a FAULT or ESTOP signal that could be driven by any of multiple components to force a shutdown, without having to OR together a bunch of individual signals, one from each module. This is more like an open-collector than a tri-state output. Each component that might detect a fault would drive its I/O pin to the faulted state when a fault condition exists, and would not drive it at all otherwise. One component would be responsible for driving the signal to the not faulted state only one time when the user attempts to reset the fault. This wired OR would look neat in the HAL but unless faulting pins (e.g. limit switches) are to be forced to use the mechanism we need an understanding of what an IO pin connected to an input pin does (c.f. a tristated output connected to a TTL input without pull-ups/pull-downs would have an indeterminate value). The limit switch example seems to require making the GPIO pins of Hostmot2 be IO in case they are to be wire-ORed. This seems much more complicated that a multiple input OR - which is perhaps why it is not currently used. Anyhow I think I must code a one-shot, whose output is an IO, to exercise the encoder index-enable input. Thanks again John Prentice -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] In/Out pin on Hostmot2 Encoder component
On 9 October 2014 19:15, John Prentice (FS) j...@castlewd.freeserve.co.uk wrote: Anyhow I think I must code a one-shot, whose output is an IO, to exercise the encoder index-enable input. Is http://linuxcnc.org/docs/html/man/man9/tristate_bit.9.html any help? -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On Thursday 09 October 2014 12:33:17 John Dammeyer did opine And Gene did reply: The Spectrum analyzer and SWR Bridge allow signal generation and as a tracking generator can also analyze cables. It's a sweet tool. http://www.rohde-schwarz.com/en/product/fsh3-6-18-options_63490-7578.ht ml http://www.rohde-schwarz.com/en/product/fshz2-productstartpage_63493-77 81.ht ml John Dunno, I suppose if one wanted to test the quality of a new and unknown quality cable it could be useful. But in troubleshooting existing cables, I have yet to see anything work slicker than a good TDR. You can have a bullet burnout someplace in a 2100 foot run of high powered coax, take a look at it on the TDR and tell the tower crew within 5 feet of where to take it apart. The 5' error? Probably the operator, not knowing the exact propagation velocity of that particular line using a SWAG instead. From there of course, they may have to take several sections below it to clean up the burnt teflon soot, but it saves them time you money for the high steel people on site if they don't have to take the last 140 feet of it apart looking for the problem. I've even used a homemade one, using F family chips for pulse drivers and a 100+ Mhz scope some math. It worked well enough to hit the bad joint. And some local frogs who had never seen a TDR were telling me I was wasting my time. I told the crew to take the tower top jumper on the west side apart and if it was clean, start down, the line was slower than my data said it was. The jumper was 4 elbows arranged to form a U shape with the U laying horizontal. The vertical lines go up the face of the tower, and this jumper went from the vertical line to the line going up the antenna mast itself, a run of about 32 if the tower is Stainless G5. The line springs had gradually pulled the line up, slightly over stretched, and the U had about a gallon of water in it because the line had been pulled up about 4, creating a low spot for moisture to collect. Its a pressurized line, 2 to 3 psi of dry nitrogen in it, operator checked replenished if needed 2x daily, so the ONLY way that water got in was the last crew put it together wet. And they knew it because they had to wait for the rain to stop before work resumed the next day, after leaving it open when they quit the night before, not even a garbage bag tied over it. The tower crew that originally did that work for me has never been on site again, per my orders. We were probably out some north of $50,000 in lost air time, make goods and extra work because they were so sloppy. -Original Message- From: Lester Caine [mailto:les...@lsces.co.uk] Sent: October-09-14 3:28 AM To: emc-users@lists.sourceforge.net Subject: Re: [Emc-users] Oscilloscope + logic analyzer (PC based) On 08/10/14 23:05, John Dammeyer wrote: Sorry. 3GHz. Not MHz. Something that popped up on my in box ... https://www.coolcomponents.co.uk/rf-explorer-signal-generator- rfe6gen.html ... 24MHz to 6GHz controlled by the PC :) -- Lester Caine - G8HFL 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) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On Thursday 09 October 2014 12:57:43 David Armstrong did opine And Gene did reply: try a new cellular phone , top of the range model , 10 months in ...wont switch on so i sent back under warranty ,, got it back in bits after 4 weeks ... their not able to repair it ... un economic to repair ! .. and they say although it's in warranty they cant cover it .. i'd stick with your saw and other metallic objects , tech stuff if far to volatile to touch I'd lay 99.9% of that right in the laps of the BBLB fans used for cooling. Decent ball bearing fans will run 10 to 50x longer than a 47 cent sleeve bearing bought in thousand lots from a street vendor in Shanghai or even farther west. On 9 October 2014 17:33, John Dammeyer jo...@autoartisans.com wrote: I can still get parts for my Sears Drill Press purchased in 1983. I'm pretty sure I can fit new bearings and other pieces onto my 1935 Delta Band Saw. Granted my South Bend 10L is no longer made it's still repairable and it was originally sold to the Ordinance Officer Edmonton in 1942. The concept that a tool sold in 2001 and can no longer be repaired or perhaps safely used after 2014 is a modern concept that bothers me a lot. I read somewhere that this century will go down in history as the most 'undocumented' century in human history when historians look back 500 or 1000 years from now. If you think that's silly try and read an 8 floppy disk or even an quad density 3.5 disk that is 15 years old. The usual result, especially from Win7 is This floppy is not formatted. Would you like it formatted now? CD ROMs have a life. The information does degrade. When was the last time you pulled out that CD with pictures of your children's birth or 1st birthday and rewrote them to a new CD. The sheer volume of photographs makes organizing them tedious and therefore unlikely. When you die will your kids methodically go through them all and re-organize into their photo albums? Or will the CDs, and the plastic jewel cases be tossed into recycling. One of the advantages of Windows over the Apple is that with every revision change they maintained a certain amount of backwards compatibility. With Apple an new revision will often 'break' existing applications and if that software company is no longer in business too bad. And traditionally you cannot roll back a revision on Apple hardware. Linux is even worse. Just recompile the source code is the mantra. The moving target of Linux distributions is laughable for the longevity of any product. Were it different and not geek programmer oriented the IBM PC hardware and Apple hardware would both be running Linux distributions. Android may still win this battle but it's hard to say if it's linux underpants will be soiled by the runs at some point too. John Dammeyer -Original Message- From: andy pugh [mailto:bodge...@gmail.com] Sent: October-09-14 2:51 AM To: Enhanced Machine Controller (EMC) Subject: Re: [Emc-users] Oscilloscope + logic analyzer (PC based) On 9 October 2014 07:02, Erik Christiansen dva...@internode.on.net wrote: Just an observation that these little pocket scopes and logic analyzers have a very short lifetime. Yup, when the host is M$-based, that's particularly true. That seems a little unfair. How long did MS support XP for? It was released in 2001 and support ended in 2014. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto 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) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On Thursday 09 October 2014 13:05:48 andy pugh did opine And Gene did reply: On 9 October 2014 17:33, John Dammeyer jo...@autoartisans.com wrote: I can still get parts for my Sears Drill Press purchased in 1983. I'm pretty sure I can fit new bearings and other pieces onto my 1935 Delta Band Saw. Granted my South Bend 10L is no longer made it's still repairable and it was originally sold to the Ordinance Officer Edmonton in 1942. I was soldering the radiator of a 1916 Dennis back together last night (until 1am) and today I rode my 1921 Ner-a-Car. But in both cases I had to compile the parts from source. Often using LinuxCNC. Pix Andy, gotta have the evidence. :) 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) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] In/Out pin on Hostmot2 Encoder component
On Thu, Oct 9, 2014, at 02:15 PM, John Prentice (FS) wrote: John, thank you for your elaboration. Two points interleaved below: snip To extend the wire-signal analogy, I think of I/O pins as tri-stateable signals. I don't really get this analogy as there is also a memory hiding somewhere for when everyone it tri-stated. It feels more like a wire with some sort of latch with weak pull-up (and perhaps pull-downs?) on its output. I.e. it remembers the state imposed on it by anything bussed onto it when the driver turns on a strong 3-state buffer The analogy is getting stretched almost to the breaking point, but: Consider a tri-state signal with no pull-up or pull-down resistor. All pins connected to it are truly infinite impedance when off. All inputs likewise have infinite input impedance. The wire has some capacitance such that when not driven it retains its current value. It was actually trying to do a manual test that got me into this trouble. I think one needs a special comp with an IO pin to connect to the index-enable to something like a pyVCP button. Why not just type sets index-ena 1? That command writes to the signal one time, which is exactly what you want. Is the fundamental concept we want for REQ not an edge-input? The receiver latches this and clears the latch when the action (e.g. count reset by the index) is performed. The requester then has to see an ACK signal, deal with the data, and eventually drop and re-raise the REQ. Yes and no. As normally used by LinuxCNC, an edge-sensitive request would probably work. It is actually a mix of edge and level - the level still matters so that the ACK line works correctly. It works like this: in idle state, REQ and ACK both 0 master sets REQ slave sees REQ change from 0 to 1 slave does whatever it does and makes data available slave sets ACK master sees ACK go from 0 to 1 master reads data master clears REQ slave sees REQ go from 1 to 0 slave clears ACK master sees ACK go from 1 to 0 back in idle state, ready to start again Note that the master cannot clear REQ until it sees ACK go true, since it has no way of knowing if the slave saw the edge. Remember that the master and the slave might be in different threads, either one might run hundreds of times before the other runs once. For the same reason, the slave can't clear ACK until it sees REQ go false, because until then it doesn't know if the master saw the ACK edge. The old way works like this: in idle state, REQ is 0 master sets REQ slave sees that REQ is 1 (prior state doesn't matter) slave does whatever it does and makes data available slave clears REQ master sees REQ go from 1 to 0 master reads data back in idle state, ready to start again Simpler, fewer steps, but still robust, even in the case of master and slave in different threads. This wired OR would look neat in the HAL but unless faulting pins (e.g. limit switches) are to be forced to use the mechanism we need an understanding of what an IO pin connected to an input pin does (c.f. a tristated output connected to a TTL input without pull-ups/pull-downs would have an indeterminate value). If you consider the signal has capacitance model, then a signal driven by 10 tri-stated outputs and connected to any number of inputs will hold whatever value it has until one of those tri-stated outputs is enabled and drives it to a new level. The initial state of a brand new HAL signal is zero. If I was designing a machine, that would be the faulted state, and I would have a reset function (a button or whatever) that would write a 1 to the signal ONCE when the user presses the button. The limit switch example seems to require making the GPIO pins of Hostmot2 be IO in case they are to be wire-ORed. Nope. There is nothing special about GPIO pins. Any pin could be used in this way, by running it through the tri-state component. The pin signal would actually be used to drive the enable of the tri-state component. The input of the tri-state would be tied either high or low. When you hit the limit, the tri- state turns on and drives either a 1 or a 0 onto the output. Note: I believe there is also a floating point tri-state component, and it can be used to make an analog multiplexor in much the same way as the boolean tri-state can do an open-collector fault line. Just enable one of N tri-state components. This seems much more complicated that a multiple input OR - which is perhaps why it is not currently used. Perhaps. Anyhow I think I must code a one-shot, whose output is an IO, to exercise the encoder index-enable input. Nope. Just use sets. Or if you must have a GUI thing, connect a VCP button to the enable input of a tri-state, and setp the input to 1. Regards, John Kasunich jmkasun...@fastmail.fm -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0
Re: [Emc-users] In/Out pin on Hostmot2 Encoder component
Andy and John Thanks TRISTATE_BIT looks great for the job of kicking an encoder index-enable. John Prentice -Original Message- From: John Kasunich [mailto:jmkasun...@fastmail.fm] Sent: 09 October 2014 19:58 To: emc-users@lists.sourceforge.net Subject: Re: [Emc-users] In/Out pin on Hostmot2 Encoder component -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On 9 October 2014 19:45, Gene Heskett ghesk...@wdtv.com wrote: I was soldering the radiator of a 1916 Dennis back together last night (until 1am) and today I rode my 1921 Ner-a-Car. But in both cases I had to compile the parts from source. Often using LinuxCNC. Pix Andy, gotta have the evidence. :) https://union.ic.ac.uk/rcc/rcsmotor/gallery/index.php/2010s/2014-15/Fresher-s-Week-inc-Radiator-Rebuild?page=3 (Photos 24 onwards) -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On Thursday 09 October 2014 19:14:27 andy pugh did opine And Gene did reply: On 9 October 2014 19:45, Gene Heskett ghesk...@wdtv.com wrote: I was soldering the radiator of a 1916 Dennis back together last night (until 1am) and today I rode my 1921 Ner-a-Car. But in both cases I had to compile the parts from source. Often using LinuxCNC. Pix Andy, gotta have the evidence. :) https://union.ic.ac.uk/rcc/rcsmotor/gallery/index.php/2010s/2014-15/Fre sher-s-Week-inc-Radiator-Rebuild?page=3 (Photos 24 onwards) That, with all the old age corrosion, looks like fun, NOT. But, being an old biker with many sets of worn out Dunlaps on my resume, I was hoping to see the Ner-a-Car in action. 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) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On 10/09/2014 06:14 PM, Gene Heskett wrote: ... snip old biker with many sets of worn out Dunlaps on my resume, I was hoping to see the Ner-a-Car in action. Cheers, Gene Heskett https://www.youtube.com/watch?v=mpHFVzwwZWs -- Kirk Wallace http://www.wallacecompany.com/machine_shop/ http://www.wallacecompany.com/E45/ -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On Thursday 09 October 2014 21:30:40 Kirk Wallace did opine And Gene did reply: On 10/09/2014 06:14 PM, Gene Heskett wrote: ... snip old biker with many sets of worn out Dunlaps on my resume, I was hoping to see the Ner-a-Car in action. Cheers, Gene Heskett https://www.youtube.com/watch?v=mpHFVzwwZWs Great! Now, how hard will it be to put enough legal stuff on it to get a plate ride it legally on the street? 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) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
Good Day All Many thanks for the pictures and keeping the old skills alive. john From: bodge...@gmail.com Date: Fri, 10 Oct 2014 00:14:27 +0100 To: emc-users@lists.sourceforge.net Subject: Re: [Emc-users] Oscilloscope + logic analyzer (PC based) On 9 October 2014 19:45, Gene Heskett ghesk...@wdtv.com wrote: I was soldering the radiator of a 1916 Dennis back together last night (until 1am) and today I rode my 1921 Ner-a-Car. But in both cases I had to compile the parts from source. Often using LinuxCNC. Pix Andy, gotta have the evidence. :) https://union.ic.ac.uk/rcc/rcsmotor/gallery/index.php/2010s/2014-15/Fresher-s-Week-inc-Radiator-Rebuild?page=3 (Photos 24 onwards) -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Oscilloscope + logic analyzer (PC based)
On 10/9/2014 11:32 AM, JHC wrote: I had occasion to re-burn some old discs a while ago, several were from the era of single speed CDRs, and I foolishly put them in a drive that can read at 52x. Second disc in literally exploded. Very loudly. I still have the very first CD-R I ever burned. Used a 1x or 2x speed SCSI Sony burner and the disc used the dark green dye. It was even readable in an old 1x Mitsumi drive, the one where the whole mechanism slides out with the clamshell lid. Crazy thing is that original 1x Mitsumi drive was not supposed to be able to read any CD-R, no matter what. Still readable even after 17 years. The nearly invisible blue dye is nowhere near as reliable as the original dark green or dark blue dyes. It does have one error in one Windows 95 CAB file. Dunno what the problem was with that one file but whenever I'd build a PC I'd always have to burn two copies of Windows to the disc to go with the system because every time that same CAB file would develop an error in one copy, though both were read from the same source files. The extra crazy thing is both copies would verify 100% against the source then the one file would suddenly develop a read error - and it wasn't just with one burner. I've only had one CD-R go to pieces on me. It had a crack at the hub which extended just into the TOC zone. I tried using Unstoppable Copier to recover the data. It wasn't having any luck, the drive would spin up and down over and over then suddenly it revved up to max speed and BANG! Plastic confetti. I was looking at it so I saw the front of the tray pop out. Shut it down, took the drive out and apart. Shook out the debris, popped the front back on the tray and no problems with the drive. Something quite annoying about recordable optical discs is stores either will not stock dual layer DVDs or if they do they only have extremely overpriced 3 or 5 packs in jewel cases or at most 25 disc cake boxes. Staples only stocks 25 disc cake boxes of Maxell DVD+R DL - the absolute worst brand of DL media made. Out of six or more burners I have only ONE will work with them. HP 2.5x speed DL media was also rather horrid. Drive compatibility was decent but I had almost a 50% write failure rate. When it comes to rewriteable DVDs, most drives support up to 8x RW discs but just try and find any DVD-RW faster than 4x. And where are the Blu-Ray drives, burners and media? I've never seen any BR drives of any kind at Staples and for only a short time did they have any discs. Dual layer DVD, 8x DVD-RW and BD-R/RE are all turning out to be like the 2.88M floppy disc. Stores that sell computer supplies and parts should have had shelves full of all these for the past decade but have either failed to stock any at all or only made tiny token efforts at selling them. The old We don't have that because it doesn't sell well. BS! You can't sell what you refuse to put on the shelf! If Wal-Mart would order a billion *good quality* dual layer DVD blanks and make sure all their stores had 50 and 100 disc spindles of them, the media would sell very well - and Staples, Office Max and the rest would have to stock them too. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
