Short edges detection

hello,
i have LabVIEW 8.2 FPGA and i need to detect edges coming from a Hall effect probe build on a motor. i need it to initialize a counter when a rising edge appeer on the Hall effect probe to know how many states per turn my motor has. the time isnt constant between 2 rising edges, because the motor can rotate with several speeds. i tried it with the bloc boolean crossing, but its not good. i also tried to put a delay between to mesures of my probe, and then compare the two values to know if there is an edge, but sometimes this method doesnt detect anything...
the time of the edge is 24ns and i must do the same thing (another application) with an edgetime of 4us.
best regards
Portmann J.

i enter in a PCI interface with the hall effect probe signal (0-5V : digital input). the motor can run at max 12000 revolution / min, but the duration of the edges is not depending of the speed. the low to high edge is during 4us and the high to low edge is during 24ns. now i tried to filter the signal and i received good results.
thank you for your help
best regards
Portmann J.

Similar Messages

  • Unable to enable duplex printing through e-Print (Print on both sides - flip pages on short edges)

    I need to print on both sides on the HP Envy 100 - 410a.  How do I enable this feature.  Everytime I try this on ePrint, I have the email attachment printing out on two separate papers.  If I print direct from the document, then this does correctly print on the same paper on both sides, just the way I want it.
    I need to get ePrint to work on both sides of the paper (flip pages by short edges) by emailing the attachment.
    Any help would be greatly appreciated.

    Unfortunately, Duplex is not supported on ePrint at this moment.
    I work for HP.

  • Contact Sheet Photos

    Can you individually orient photos in a contact sheet

    The starting point here, is which way round the images appear in the Filmstrip and generally. If you want to use a button, that's set in Library, as SausalitoDog says.
    However the arrows may not appear for you. For grid view, there is an item "Rotation" that would need to be checked in the view options for how the image cells appear. For loupe view, the Toolbar has to be showing - it toggles on and off with the T key shortcut. Next, the user can select what controls appear on the Toolbar - there's a little triangular arrow at the right hand side, accessing a menu. Rotate needs to be checked there, for the arrows to show.
    Or you can use the Ctrl + [ or ] (square bracket) key shortcut after highlighting an image in the filmstrip, even while in the Print module.
    The specific orientation controls you have in Print, are firstly the shape of the containing image cell (whether it is itself portrait, landscape or square), and secondly whether Auto Rotate is checked or not (this is found in "image settings", along with Zoom to Fill).
    Often contact sheet layouts use an exactly square image cell, in which case checking Auto Rotate makes no difference, and the image always appears as seen in the Filmstrip.
    Say you wanted to force all the images on a contact sheet to appear portrait for printing, then you would need to achieve a portrait rather than square cell size, and to check Auto Rotate.
    LR always makes the image as big as it can within the constraints that you set. So:
    If Zoom to Fill is not checked, and Auto Rotate off, you see all of each image, centred and sized to fit for both width and height. With Auto Rotate on, it's the same, except an individual image will turn 90 degrees where the longer edges of the image and the cell, allow it to scale bigger that way.
    If Zoom to Fill is checked, and Auto Rotate off, you see every image enlarged so as to show no white space in the cell, cropping off the surplus on-the-fly. With Auto Rotate on, it's the same, except an individual image will turn 90 degrees where the shorter edges of the image and the cell, allow it to scale bigger that way.
    RP

  • Import images into Visual Edge Detector

    I am new to this tool, infact very new. I am working on the image analysis of cancer CT images. I would like to know if it is possible to import the DICOM (or any other image format) images into this tool and get the edges detected?
    If not what other tool of NI can I to apply alogrithms to edge detect?
    Thanks in advance.

    Hi, Elaine. Thanks for your inquiry. Here's my basic workflow:
    Output JPG from Photoshop at intended size, say 300 x 400 px @ 72ppi.
    Import to stage in Edge Animate - no options here. Image seems considerably less sharp, right on the stage - I have multiple identical monitors, so I can compare.
    Use Edge Animate's Preview in Browser (in this case, Firefox for general testing purposes...) the images are not sharp.
    If I DOUBLE the resolution when outputting from PS (600 x 800px @72 ppi), saving with the identical filename, as resdesign suggested, and change nothing in Edge, the outputted images look great. I have tested with many bitmaps and they all exhibit the SAME behavior.
    Extremely inconvenient to have to manually re-calculate image output sizes to accommodate this problem in Edge.

  • Graduated filter substitute?

    Hi,
    I'm far away from being a professional photographer but I do enjoy landscape photography. I've been playing around with Lightroom 3 and I love what I can do with my pictures in there. My big problem is that I also love Apple products and all the syncing that comes with it. I really want to move over to Aperture but I can't find a decent substitute for the graduated filter that Lightroom 3 has. I've tried the Brushes (dodge and burn) but they leave me with edges. It ends up looking bad. I've tried experimenting with the exposure but that changes the whole picture, not the sky or the ground (which is mostly what I want to adjust in my pictures). I've also played around a bit with highlights and shadows but, as with exposure, it's the whole picture that is being altered.
    Any suggestions?
    Thanks so much
    Sophie

    Also useful:
    Put down brushstrokes at different strengths.  Use "color overlay" to see.  Feather between strokes as well as between stroke and non-stroke.  Note that Feather is also strength-settable (afaict).
    Brushes are stupendously variable.  I find them the least well-used and understood aspect of Aperture.
    For the quick'n'dirty GND filter, use the Polarize Quick Brush, turn off "Detect Edges", set size to whatever is one-fourth the distance from horizon to top of Image, set softness to c. 0.3 and Strength to 1.0 and draw a swath across the top of the Image.  Change strength to 0.9 and come back the other way with swath #2 just below the first.  Repeat at 0.8 and 0.7.  Set Strength back to 1.0 and Feather the three in-between edges, and the fourth (lowest) edge as needed.
    Note that "Detect Edges" works as an Eraser as well.  It is often easier (IME) to erase to the edge of a form as it is to fill outside the form to the edge (the rule of thumb is simple: detect edges from the side of the edge with the least tonal variation).  I almost always lightly feather all edges detected w. "Detect Edges".
    Try to avoid relying on "Detect Edges".  It is needed much less than commonly thought, imho.  (Any draftsman could tell you this.  We perceive with our brains, and our brains are massively motivated completion machines.  You are generally better off under-specifying an edge and letting the viewer "find it", than over-specifying it and bringing attention to it.)
    OP:  Note that almost every Adjustment except "Exposure" can be brushed on/brushed off, and that there are separate Quick Brushes for each of the four slider-controls in the Enhance Brick.
    Message was edited by: Kirby Krieger

  • Cropping made difficult

    When I want to crop an image, iPhoto '08 zooms out, displaying the image on a black background. When the objects on the photo are dark, this actually makes it difficult to see where the image stops and the application background begins. (We want to crop before enhancing, right.) Also, the proportion numbers and two buttons (cancel and that other one) are placed on the image itself, blocking the view to the bottom part of the image.
    I suppose there is no way to crop an image while actually seeing the image (and not just "most of the image")?
    And another silly thing: My photos are 4:3, and the closest format the photo lab uses is 13 x 10 cm, which is slightly shorter. The lab automatically cuts off the edges, so sometimes I want to crop the images to 13 x 10 to decide which edge of the image should survive its visit to the photo lab.
    In iPhoto '06, when I typed 13 x 10 (because it isn't in the list, you know), the crop area was always at its maximum size, so I only needed to move the area towards one of the edges. If I wanted to zoom and crop (leaving out more of the image), this of course had to be done manually.
    Now I have to manually grow the crop area to its maximum (dragging the crop edges at least twice, once I needed to drag the edges and move the crop area five times to reach the maximum size). I mean -- most of the time there is no reason to "zoom and crop", and certainly very seldom to the exact area that iPhoto proposes. So whoever wants to zoom in/crop to a particular area will always have to do some manual adjustments to the size of that area. Now one also has to manually zoom out.
    In iPhoto '06 the crop area was even centered, so I could see exactly what the photo lab would leave out. Now I can only hope to place the crop lines more or less in the center. But it's difficult to see because of the black background and all the writing.
    What happened? Did Microsoft buy Apple?
    Oops. I just uttered a couple of Norwegian swear words here in my sofa. I accidentally discovered one more annoying thing.
    In iPhoto '06, when the crop area was shown, one had to press Enter or click some button to actualy perform the cropping. One could see the crop area and decide that this image doesn't need to be cropped, and then click the right arrow, move on to the next image, and right away evaluate it for cropping, etc.
    If I click the arrow in iPhoto '08 while the crop function is active, a cropping is actually performed. So now I have to activate the crop function, manually enlarge the crop area using multiple clicks and drags, hope to be able to center it despite the black background and the writing at the bottom, then decide that the image doesn't need cropping, deactivate the crop function, click the right arrow and activate the crop function again.
    I want my money back.

    Thanks for all the advice, but it seems I am not good at explaining what I don't like and why. I'll try to explain in detail. There's nothing new here, so don't read it unless you really want to.
    Here in Europe 13 x 10 cm is one of the standard sizes of a photo print. Many digital cameras (e.g. Ixus 750) use the ratio 4:3. The print size 13 x 10 cm equals 3.9:3.
    (The adviced 5:7 equals to 13 x 18 cm, which again is equal to 4.15:3. This is of course also pretty close to 4:3, but then we need other albums for the prints.)
    When the photo labs receives an uncropped 4:3 image, it will make 3.9:3 prints (13 x 10 cm) where the edges of the original 4:3 image have been cut off. Often this is not a problem. But not too seldom it is wise to perform the cropping to 3.9:3 at home before uploading to the photo lab. In most of those cases we do not want to select some small area of the image, we want to conserve the whole hight but remove one of the short edges in order to preserve the other one.
    Of course, 10 x 13 is not in the list of predetermined sizes. The closest predetermined size is 4:3, which is exactly the size we want to avoid when cropping. I can live with that. It's easy to type the numbers "13" and "10" manually.
    In iPhoto '06, when the size had been chosen, the crop area popped up and was so big that it couldn't be expanded any more. It was also centered on the photo, and we could see very easily what parts of the picture the photo lab would leave out on the prints if we didn't crop anything at home. And we could drag the crop area to one of the short edges and then crop if we wanted that partucular edge to be preserved on the print. Of course, we could also make the crop area smaller if we wanted to leave out even more of the picture.
    If the picture was already cropped to 13 x 10, the crop area that popped up would be smaller than the cropped photo itself, and so we could see fairly easily if the image had already been cropped or not. A nice feature, but not crucial.
    Having looked at one picture (and perhaps cropped it, perhaps not) we moved on the the next picture, looked at the cropping area, and decided if we needed to crop the photo for the photo lab's sake or not.
    In iPhoto '08, when the crop tool and ratio have been chosen, the crop area pops into position, but it is not expanded to its maximum. We have to perform at least two clicks-and-drags to achieve this. (I have discovered that if I "reset crop", then that will expand the crop area to the desired maximum that wasnt' there in the first place. Still, this is of course counterintuitive.)
    Also, there is now a black border around the picture when the crop tool is activated, and it's more difficult to see where the actual edges of the uncropped picture are. I have found no way to change that colour. And we don't even need that border, as the only reason to have it when editing in the main window or in a separate window, would be to make place for the crop info bar, which is really a floating window that can be moved.
    Anyway, all this means that it has become more tedious/complicated to crop pictures, and especialy the kind of cropping that we need to do to make a 4:3 image fit onto a 13 x 10 cm print.
    One of the complicating factors is also the fact that in iPhoto '08 we can't just move on to the next picture anymore. If we do, the present picture will be cropped automatically, unless we first deactivate the crop tool, and then move on before we activate it again. So... more difficult to crop what we want to crop, but easier to crop what we don't want to crop. To achieve the latter disaster, we just need to forget to turn the crop tool off and then on.

  • MiniDV Tape Storage

    I'm trying to determine the best way to store MiniDv tape. I have heard and seen different methods, Some sites say upward standing on its short end with its spine showing outward as a book on a shelf and the way VHS tapes are kept, Others say flat (like the audio tape format) as in a storage rack that are sold online.
    What is the correct way for long term storage?
    Thanks. Rich

    Don't lay them flat. Over a while, the tape can "creep" down the spindle, like Sellotape (3M tape) sometimes does, and thus kink its edges, thus giving corrupt replay.
    Stand the tapes vertically, though it doesn't matter whether you stand them on their short edges or longer edges. If in their original boxes - they should be - when you stand them on a short edge you can more easily read the writing you'll put on their spines to identify each tape ..like, as you say "..a book on a shelf and the way VHS tapes are kept".
    DON'T store them near a loudspeaker or electric motor or anything else which generates a magnetic field, and keep them away from mains wiring ..ditto.
    DO keep them where they won't get too moist (NOT near a bathroom!) nor too cold (in a damp cellar) nor too hot (in a conservatory or hothouse).
    DO keep them at cool-ish room temperature and normal humidity ..like, say, in a cupboard in a spare bedroom.
    DON'T let them get dusty, nor keep them where volatile chemicals can get to them - so not in a tool shed where you store paint.
    ONCE A YEAR rewind them ..wind them fast forwards and then fast rewind. That's to make sure that the layers of tape don't stick together, so that pressure between layers is eased, and so that you don't get "print-through" of the magnetism from one layer onto the next.
    You might also get some fun from playing them back each year!

  • The detection of short dump in the Solution Manager

    Hi,
    In my project, Batch are processing  every night  In the CRM system.
    IF any error was occurred, alert email will be sent by the system,  however,
    when the "short dump" was occurred  unexpectedly,the system can't detect it and email was not able to be sent.
    Therefore I want to detect the "short dump"  in the "Solution Manager".
    Who can tell me that Is there any standard service/function which can handle this in the "Solution Manager" ?
    regards
    Takahiro

    Hi,
    Please check below URL and notes, hope it helps.
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/content.htm
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/05c80724d63836e10000000a42189b/frameset.htm
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e3eeb4a8-0b01-0010-bd99-f4a700a49d32?quicklink=index&overridelayout=true
    note 553953
    note 784752
    Regards,
    Deepanshu

  • [AS CS2] Create a list of all items whose clipping type = detect edges

    I am creating myself a light preflight script for Indesign CS2 documents where a part of it creates a list of all the images that have had the clipping path "detect edges" applied. But I am struggling to work out how to address the clipping path settings. This is basically what I have tried:
    set BadClipping to the name of every link whose clipping type is detect edges
    display dialog "The following images have detect edges on: " & (BadClipping as string)
    Any help is greatly appreciated.

    On 8/7/08 10:43 AM, "Dylan" <[email protected]> wrote:<br /><br />> set BadClipping to the name of every link whose clipping type is detect edges<br /><br />'clipping type' isn't a property of links, so you're sunk there. You need to<br />go via graphics and the 'clipping path' property (the dictionary doesn't<br />list it for graphics for some odd reason, but all subclasses of graphic<br />support it so that's got to be a bug). 'clipping path' returns a reference<br />to the 'clipping path settings', one property of which is 'clipping type.<br /><br />So you need something like this:<br /><br />tell application "Adobe InDesign CS3"<br />    tell document 1<br />        try<br />            set BadClipping to every item of all graphics whose clipping<br />type of clipping path is detect edges<br />        on error<br />            -- none found<br />        end try<br />    end tell<br />end tell<br /><br />-- <br />Shane Stanley <[email protected]>

  • How can you detect irregular edges using the IMAQ add on?

    Im currently trying to use the IMAQ add-on for LabView to detect the edges of an irregular image. I have attached the image I am trying to detect the edges of. I have tried using everything in the "locate edges" sub-pannel (i.e.. imaq find edge, imaq find circular edge etc.) but none of them have yielded any favorable results. I think the "IMAQ edge tool 3 IV" might be what im trying to find however I don't understand how to get any usable data out of it.
    Thank you, all comments and help are greatly appreciated. 
    Attachments:
    waveguide.png ‏516 KB

    Hi Dander, 
    I am not sure exactly what types of edges you are trying to acquire, but I used one of the examples from our Example Finder and was able to detect edges on your image.  I will say that with the image that you are using, the edges are not very well defined, so you may not get a 100% accurate measurement.  The example that I was using uses the IMAQ Edge Tool 3 VI and the example can be found by going in LabVIEW to Help>>Find Examples...  From there, you will go to Toolkits and Modules>>Vision>>Functions>>Edge Detection Example.vi.  After that, you will remove the build path function and input a path to the image.  I hope this helps!
    Kim W.
    Applications Engineer
    National Instruments

  • Need to find if Images applied clipping path(detect Edges)

    Hi Scripters,
    How to find Images applied with clipping path(detect Edges) in Indesign document.
    Could anybody please share a code/script with me.
    Yours,
    Jerome

    No problem -- a document's "allGraphics" property lists all of the imported graphics in the document. Just check each of them one by one. This little script alerts you with the name:
    for (img=0; img<app.activeDocument.allGraphics.length; img++)
    if (app.activeDocument.allGraphics[img].clippingPath.clippingType == ClippingPathType.DETECT_EDGES)
      alert (app.activeDocument.allGraphics[img].itemLink.name);

  • Detect edges script

    is there a script to remove all instances of detect edges in an open doc?

    Please repost in the forum that corresponds to the software you are using.

  • Detect edges problem with brushes since 3.2 update

    When using any of the brushes with the detect edges on with a raw image, they start to apply the change with a small area of the image effected but then stop applying the effect. If the colour overlay is turned on a straight line is seen were the affect has stopped being applied. turning of detect edges returns the brush to its normal function. This problem is making the detect edges function unusable and very anoying as I do use this a bit. This has only happened since upgrading to version 3.2.

    That's a good news! Seems, that the massive protest of the users has been heard!
    Could you please check the behavior of the crop tool? In Ap. 3.1.3 when I grabbed the crop-frame on one of the middle handles only that side of the frame was moved. In Ap. 3.2 the opposite side moved too.
    An example: grab the middle handle on the right side of the frame and move it to the right.
    Aperture 3.1.3: the right border follows the mouse, the upper and the lower frame border goes up resp. down by resizing the crop-frame.
    Aperture 3.2: the right border follows the mouse to the right side and the left border goes to the left side, the same amount you move the right frame border to the right side.
    What about Aperture 3.2.1???

  • InDesign CS3 - Detect Edges does not work with transparency

    I have three machines running at home. One is a PowerMac G5 running OS X Tiger and Adobe CS3 Master Collection. The other two are new Intel iMacs running OS X Leopard, also with the CS3 Master Collection.
    My problem is this: On the PowerMac G5, I can create an image in Photoshop that has a transparent background with a cut out object. When I place this object on a page in InDesign, I can use the Detect Edges feature in the Text Wrap panel to automatically detect the edges of my object with its transparent background.
    However, when I do this same procedure on the new iMac, InDesign fails to detect the edges of the object. This does not seem to be dependent on whether the image was created on the iMac or the PowerMac.
    What I have discovered, is that the Detect Edges feature works on the iMac if the image has a solid white background, whether on the same layer as the object (i.e. 1 layer) or as a separate layer behind the object.
    So, if anyone out there, or particularly one of the developers over at Adobe, could check on this issue and find out if my case is an anomaly or a real bug, that would be terrific.
    Thanks!

    F,
    No need to need to get into a tif. I was merely pointing out that your response wasn't directed to the OPs request.
    Jared isn't asking how things work, he's asking if they work the same for other users as they do for him with the little complication that they work for him in two different ways.
    >So, if anyone out there, could check on this issue and find out if my case is an anomaly or a real bug, that would be terrific.
    Jared,
    I can't talk for Tiger. I have an iMac running 10.5 and detect edges does not work for me with transparency. But there is a difference in the text wrap options between a transparent background and a white one. When an image with a white background is selected, the Alpha channel is greyed out. With a transparent background the Alpha channel becomes available, and when selected another field is generated. [Alpha: Transparency]
    Are those options not available on your G5?

  • How do you detect all edges with IMAQ extract contour IV?

    I am trying to use the vision development module to detect all of the edges in a pictue and not just one. The idea is by the end I will be able to detect all of the red in the attached image. However the extract contour with only give me one brighter section of the image.
    All help greatly apreciated
    Attachments:
    waveguide.png ‏516 KB

    Hello Dander
    I wanted to apologize to you.  I saw that an identical issue was being handled by a different engineer and we consolodated that this other individual would handle it.  Have you been able to come to a resolution to this problem?
    I have this notion that you may be able to find the outer most edge, take note of it's location and cut out the image bounded by that edge and then run the edge detection system again to find the next outer most edge and repeat.  Have you made any progress on this issue?  I'm happy to provide any further insight into the situation.
    Sincerely,
    Greg S.

Maybe you are looking for

  • Some Solutions, 1 remaining prob with MBP, Windows 7 64-bit, Bootcamp

    It has taken me about 3 months to get Windows 7 64-bit (OEM disk purchased from TigerDirect) to work on my MacBook PRO 17" 2.4GHz, and it is still not quite there. FIRST: It seemed impossible to load. I put the disk in the drive, held Option key down

  • How do I build a user update page

    I am trying to build a user update page that only the user can update if they have the correct username and password. I have tried a number of ways, but haven't come anywhere near to acheiving it. I am guessing I need to correctly construct the log i

  • "Cant fit into specified packet size" error when adding new metadata

    I get a  "Cant fit into specified packet size" when I add my own custom field in a different name space and use "myFile.PutXMP(meta);". The Schema example in SDK dumps RDF in separate files but I want to add a new field in the metadata of an existing

  • CTI Tool Bar Hangs in Siebel CRM

    Hi Experts, CRM Application Version:        8.1.1.4 SIA [21225] Database Version:                    11.1.0.7.0 CTI Siebel driver dll                  9.0.347.1 We have recently upgraded our CISCO CTI Client from 7.5 to 9.0. And we have been facing i

  • My iPod won't turn on and I tried everything someone help!!!

    iPod 4g It was reset because it wouldn't go on past the apple icon My sister reset the iPod I hav tried everything I can think of to turn it on I've let it run dead for over a month I charged it for over 10 hours yesterday to today I hav hooked it to