Frequently Asked Questions



Lost license keys cannot be replaced; WipWare recommends that the license key is insured for the replacement value of the software product to protect against loss or theft. Damaged license keys can be exchanged for a nominal cost; Keys that have been damaged due to tampering may be replaced at the discretion of WipWare.
The most important thing about photoanalysis software is the quality of images that are used for the analysis. Image Acquisition – The better the images, the better the results. Develop a sampling strategy. Taking images is like taking samples for sieving or other tests. The results must statistically represent the product as a whole. To adequately compensate for rockpile segregation and heterogeneity, each image must contain a sufficient number of fragments, and the results from dozens of images per blast must be merged and averaged. Accurate estimation of larger blocks in particular requires merged data because of the scarcity of such blocks. High-fidelity, high-speed automatic edge detection is essential – methods that rely on tracing or manual editing are incapable of processing sufficient data and so are prone to large sampling errors.

Fill the field of view with fragmented rock, preferably at least 200 particles.

Include all sizes. No single block should occupy more than 20% of the width of image. For improved resolution of fines, use WipFrag's zoom-merge capability to combine images at different scales of magnification.

Beware of rockpile segregation. Large blocks tend to roll to the outer edges and fines may cover the surface or become hidden as a result of gravity or rainfall. The effects can be minimized by increasing the number of images per sample but only with careful selection of image locations.

Don’t waste an image. Get images of the particles in question, not the sky and area around it.

WipFrag measures what it can see. If your pictures are far away, fines will not be resolved. If the image is taken too close, oversize may be missed. Get a good mix of images of the sample in question.
When acquiring image samples each image should:

Contain an easy to read scale. (two for tilt correction).

Be high definiton – Not necessarily high resolution.

Never be taken with a wide angle lens.

Contain clearly visible particles. (if you can outline each individual particle, the software can too)

Have even lighting. (avoid hot spot/shadow areas if possible).
Updated Windows License Key Drivers among other useful tools and updates are available to registered users in the WipWare Customer Download Area; This driver can also be download directly from SafeNet using this link. (8.07Mb) The latest License Key Driver is universal allowing Parallel or USB type keys to work as well as adding new functions such as network connectivity. This means that if System A has a valid Hardware License Key and System B does not have a License Key however both systems are a part of the same network, have the License Key Driver and the WipWare software installed; Then System B can run the WipWare Software using the License Key on System A, assuming that the License from System A is not currently in use. This is just another way that WipWare keeps licensing simple and flexible to you…
The zipped attachment sent by WipFrag Technical Services contains a file named KeyEnable.exe. To initialize your key for the WipFrag software simply extract and run KeyEnable.exe with the security key attached to the computer. If it works properly, a prompt will appear stating that your key has been activated. You'll now be ready to run the software.
Large and small images each have their pros and cons. Fines can be delineated easier with larger images and tend to get fused together with smaller images. Oversize is usually analyzed properly with smaller images, but tends to get slightly disintegrated in larger images. Smaller images analyze and are edited much faster than large images. Editing the net will take longer if the image size is larger than your screen size as there is no fractional zooming capability in the software. WipWare always recommends taking the original images at a high resolution. It is always possible to downsize the image without distortion, but nearly impossible to make an image larger while keeping clarity and definition. As a rule of thumb, if you cannot delineate the particle with your eye, the software will be unable to as well.
WipWare recommends using any solid scaling device with a contrasting color to the material which can be laid down flat onto the material in question. Range rods, yard/meter sticks and customized frames can all be used. WipWare discourages the use of balls as they can expand and contract with changes in temperature and altitude. Be sure to have the scaling device perpendicular to the camera. Be sure to use two scaling devices when you cannot be parallel to the sample. This will allow you to use the tilt-correction within the software for more accurate results. If in doubt, use two scales. One in the foreground of the sample and one in the background.
Digital zooming reduces the definition in your images. When you choose to digitally zoom, your camera is actually cropping and expanding the image. This effect makes it appear as if the image has been zoomed in. The problem is, when the camera expands the image, it needs to interpolate pixels which reduces the clarity and definition of your photo. Wide angle lenses should be avoided as well. In order to obtain a wide format image, distortion is created at the edges of the photo. The wider the lens, the more distortion there is.
WipFrag has been tested for images up to 11Mp (4000×2650 pixels) without any problems. Some have commented that their computers freeze up when analyzing these images. Please note that large complex images can take upwards of twenty seconds to be analyzed depending on processor speed, memory, the EDP and the number of particles in the image. If you need to speed the process up, you will need to make your images smaller. You may want to consider taking 2-3 smaller images during your next test. Smaller sized images analyze and are edited faster. You can always merge the data together afterwards.
If you wish to resolve smaller particles, there are two options. You can choose to use a higher zoom lens. Zooming in allows the system to resolve the smaller particles much easier. It can however reduce the number of the larger particles analyzed. The other option is to update your camera. New camera technology has allowed us to greatly increase the minimum resolvable particle size within images and still keep the larger particles within the results. By moving from the standard 0.3Mp camera to one of our 2.1 or 10.7Mp options, you can increase your resolved particle magnitude from 43x to 267x. Simply put, your system will be able to analyze particles up to 1/8th the size of the smallest particle that your system is measuring now.
The user should take special care not to inadvertently bias the sample by altering the method in which image samples are taken, setting the scale improperly, selectively editing the net or changing the EDP between samples that will be merged to each other. All analysis of a study should be performed in the same way. Be systematic and develop a routine for image acquisition and analysis.
Distribution Model selects between two separate analytical models for the 2 dimensional to three-dimensional unfolding function. The “well graded” model is to be used for blast fragmentation assessment. The “highly uniform” model is to be used for applications such as consistant crusher products on conveyor belts. Typically, the size range of the material should be very narrow, ie. pellets, greenballs, prills, aggregate, etc. Users should be cautioned to use one model only. Empirical calibrations differ as a result of using the different models!
If you change the sieve outputs in the software often, it is recommended to save (and backup) copies of your custom size classes. You can save as many of these files as you require and can label them as needed. When you require the custom sieve output, simply load the xml file from within the "Output" tab located in the 'Options' menu. This is a very useful tool for consultants and quarries who are constantly changing the 'sieve' outputs for analyzing various material specifications (ie. Granular A, Granular B, washed stone) Saving/loading these custom sieve sizes saves a great deal of time when you need to change your outputs.




WipWare recognizes that legacy devices such as parallel ports are being eliminated from current notebook computers, at any time if you wish to upgrade your license key to the USB version you can do so by contacting WipWare Technical Services. The fee for license key exchange is minimal. Cross shipping is available to lessen downtime with the software.
WipFrag 3.0 is designed to run on Windows XP, Windows Vista, Windows 7, and Windows 10. It is available as an app on the appstore and can be used on any iOS devices. If you wish to download the app, click here. Unfortunately, WipWare no longer supports the use of the software on older operating systems.
WipFrag is designed to detect Firewire/IEE1394/iLink video cameras and some analog streaming class WDM compatible video cards. This message is simply stating that no such devices were found when the software was started. If you received this message and have a Firewire/IEEE1394/iLink camera attached, please make sure that it is turned on prior to starting WipFrag so it can be detected properly. When using an analog video camera the camera must be attached to the video card/framegrabber and turned on prior to starting the software. With some cards, there must also be a video feed coming into the card for it to properly be detected. Due to the vast numbers of cards on the market, WipWare technical services are unavailable to troubleshoot problems for this hardware.
Windows 2000/XP users will need to install the Rainbow Super Sentinel Pro license key driver on their computer for WipWare Software Products to work. This driver is located on the WipWare CD-ROM and can also be downloaded at (right-click and save as.) If this driver update does not work, please call WipWare Technical Services with your software version and build number ready.
The number of images needed to properly analyze muckpiles or another sample is dependant on a number of things and changes from project to project. The main question to ask yourself when you think you are done obtaining your images is "did I gather an adequate statistical representation of the material in question?". If you have missed the smaller particles, or feel that perhaps they were to small to be delineated, you should take a few zoomed in images of them. As well, if you have neglected the oversize material, you may need an image of them as well. Remember, you can merge multiple analysis together within the software very easily.
If you see a great deal of fines when acquiring the images, capture some zoomed in images of the material. WipFrag’s ability to merge analyses will allow you to incorporate these fines into your overall study.When analyzing images containing material that cannot be delineated, you can choose to mark blocked areas as fines. Go to Options - Sieve Options tab. Input the “Average Fines Size” in the designated area. The units can be inches or meters – this unit can be changed within the ‘Set Scale’ dialog. Once this size is entered, you can choose to mark areas as fines by one of three ways: right clicking on the block and selecting ‘Mark as Fines’ or by choosing ‘Mark as fines mode’ in the edit tab, or by pressing F7 and then left click in the desired blocks.
Hotkeys have been added to the software to help speed up editing. The keys are as follows.F2 – ‘Draw Line Mode’ F3 – ‘Draw Polyline Mode’ F4 – ‘Erase Line Mode’ F5 – ‘Erase Block Mode’ F6 – ‘Ignore Block Mode’ F7 – ‘Mark as fines Mode’ Some of us have found that these hotkeys can cut editing time in half.
This is a common occurrence when you have forgotten to set the scale or have set an improper tilt scale. To remedy this, reset the scale/tilt scale and ‘sieve’ the image again. There is no need to regenerate the net.
It is recommended to avoid acquiring images early in the morning or lat in the day when the sun is at a low point. It is during these times that long shadows are created around the particles (especially oversize) making it harder to find an adequate edge detection parameter.From our experience, the most ideal images are taking late morning or early afternoon on overcast days. Lighting is usually very even during these times creating a slight shadow around all particles. This makes finding an EDP very easy and greatly reduces editing times.
WipFrag for Windows software keys support network license sharing. WipFrag hardware keys do not, but can be moved from computer to computer. For more information, please refer to WipFrag Network Keys.pdf in the Customer Download Area.
This known issue has only been reported with ATI graphics chipsets running on Windows XP. To resolve this issue do the following:

Right-click on desktop and select Properties

Under the Settings tab select Advanced

Select the Troubleshoot tab

Turn the Hardware acceleration down 2 steps (4th from the left)
If WipFrag was uninstalled improperly or if a newer installer was run before uninstalling the old version you may get duplicate entries for the same version of WipFrag in the Add/Remove Programs list. To remedy this issue do the following:

From the Start menu select Run and type 'regedit' without the quotes and hit OK.

Browse to: HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Uninstall

Expand Uninstall and look for the duplicate entry you wish to remove (named 'WipFrag', 'WipFrag Online' or something similar). If you are unsure which one to remove select each and use the information on the right to determine which version or build shouldn't be there.

Delete the duplicate key(s) on the left. Note: If you are still unsure of which one to delete make sure you uninstall WipFrag from your machine and then delete all WipFrag keys that shouldn't be there.
After updating WipFrag you may receive XML errors on startup. These errors should only appear the first time a new version is run. These errors mean new WipFrag settings are detected and will be added. However, if you continue to get XML errors even after restarting WipFrag then please contact WipWare Technical Support.
The reason that the WipFrag 2010 will not play a video file is because your PC does not have the required Codec Pack. The Codec pack needed can be downloaded by clicking Here (Note: This download is for WipWare customers, as such you will be prompted to enter your username and password before you can start the download). Once you have downloaded the pack, simply Start the Codec Installer, click “Next”, “Choose Simple Install” you may now proceed by selecting “next” (Note: all the pages from here until the final install button are optional but should be left alone) then select “Install” and then “finish” to complete the installation. You should now find that your WipFrag 2010 plays video in .mpeg, .avi and .mts formats.
In cases where WipFrag is installed to the 'Program Files' or 'Program Files (x86)' folder and when running under Windows Vista or Windows 7, the WipFrag.xml and WipFrag.xsd files will be saved to your 'My Documents' folder.

Note: WipFrag.xml contains all your settings within the software, and WipFrag.xsd must reside in the same folder as WipFrag.xml.

If updating from a previous build, WipFrag will make a copy of the WipFrag.xml that was previously located in the ‘Virtual Store’ directory. Also, all directories that were previously pointing to the ‘Virtual Store’ directory will automatically be changed to point to your ‘My Documents’ folder. Any directories that were not pointing to the ‘Virtual Store’ will not be changed.

If you are receiving the message 'Unspecified Error’ and/or 'Failed to load WipFrag.xml' please check the following: You have read and write access to:

C:/Users/[your_user_name]/Documents/ Example, if your Windows username is 'User': C:/Users/User/Documents/ Start WipFrag and ensure the following directory structure has been created:

C:/Users/[your_user_name/Documents/WipWare/WipFrag/ WipFrag.xml and WipFrag.xsd should now be located within this folder. The default 'Project' folder should now be located here, unless you have specified otherwise.

If you have confirmed that you have read and write access to the 'My Documents' folder but you are still receiving errors please contact WipWare Technical Services.
Currently, WipFrag 2010 supports Windows 2000/XP/Vista/7/10.
There is a known issue when attempting to run the initial release of WipFrag 2010 Build 2 when in Spanish or French regions. If WipFrag 2010 Build 2 won't start please do the following:

Go to 'Start - Program Files - WipFrag' and run 'TrueUpdate Client' or

Browse to where you installed WipFrag (default is C:Program FilesWipFrag)

In the 'Update' folder run 'WipFrag 2010 Update Client.exe'

The update client should detect and download a new version of WipFrag and then will prompt you to update from Build 2. Now you should be able to run WipFrag.
A few versions of WipFrag 2010 may have difficulties merging together all of the 'frag' files from analysis if the image file name was long.

This issue has been fixed and will be remedied by updating your software.

To update your software, open your WipFrag 2010 software, open the 'Help' menu and select 'Check for updates.'




Have you tried to access your online system from remote desktop for the first time and found that you can't start the software? This problem is due to an issue with one of the dongles dll files. This can be fixed by replacing the sx32w.dll file found in the WipFrag Momenutm or Reflex folder with version Search your installation CD/folder for a copy of it, or contact WipFrag Technical Services for an update.
WipFrag Momentum would allow you to monitor material on as many 8 conveyor belts at one time in real time. If you need to measure anything from prills and pellets to fines and boulders, WipFrag Momentum may be what you are looking for. Please contact us and we can send you more information on the topic.
If you load an image and receive a message that states “Existing Saved Exclusion Zone size does not match the current image." you can still continue with the analysis.

This message has appeared because your system has been set to use an exclusion zone of a different image size previously set. (ie. An exclusion zone was set for images at 800×600 pixels, but you are now analyzing images that are 1024×768.) This message can be stopped by opening any image, selecting ‘edit exclusion zone’ and un-checking the ‘Enable’ check box.

If for any reason you still receive this message afterwards, you can always choose to delete or move the actual exclusion zone image. Depending on the version you are using, you’ll find it in the same folder in which you are loading your images or in the wipfrag/bmp/ folder. the name of the file is ~exlu*.bmp
All of our outputs are available within the CSV file. This means that each analysis writes over 60 values. A normal momentum system running at full speed will produce four entries/second. This results in 5+Mb csv files daily. To reduce the size of these files in Momentum or Solo you can reduce the sampling interval, reduce the imaging interval or increase the number of images per merge. These options are all available in the Online Options menu and are camera specific.
WipFrag online systems are designed to run on a dedicated computer under a single user with full administration access. This problem has most likely been caused by multiple user accounts on the computer.

When the WipFrag 'Autostart' settings are enabled, when another user logs on, the system senses the startup and WipFrag re-starts under someone elses account. This can create confusing and lost information. To fix this, the best solution is to have only one user account on the system. Alternately, remove all autostart features in WipFrag. Start the software under its installed account. Inform other users not to start the software under their account.
If you notice the system has suddenly started triggering early you will need to check if all software settings are fine. If satisfactory, check the TTL input display in the status bar. A signal of 0000 0010 means that a truck is dumping (something is breaking the beam.) If no truck is dumping, then the emitter has lost power or the emitter and receiver are no longer pointed at one another. You'll need to check the physical status of the sensors and re-point them if necessary.

If a sensor was damaged and you are waiting for a replacement, you can temporarily fix the early triggering by enabling the 'Pixel Trigger' option.

Simply enable the pixel trigger (Online Options- Pixel Trigger) to top or bottom. Place the pixel (x,y cordinates) near the bottom center of the screen. Lower threshold = 0, Upper threshold = 255, Delta 15. Go to online options – trigger order, and select Pixel as the second trigger. This simply creates a lag in the triggering. Refer to your user manual to fine tune the settings.

When you get your sensor fixed/replaced simply go to the Trigger Order and change your second trigger to TTL.
WipFrag Momentum systems are designed to accept up to 16 Analog cameras or 8 Ethernet cameras (up to 255 is possible) into a solitary workstation. Please note that for every camera added to a workstation, the fewer samples/camera/second is achieved. If a high sampling rate is required, it is recommended to keep the number of cameras/workstation to a minimum.
Note to online system users:

Please remember that if you change the zoom on your cameras or alter the lighting, you will most likely need to reset your EDP. Take 20-30 images over a day and find an EDP that works well on all of them. Recheck the EDP after 1 week to verify it is still working well. EDPs should not be altered during studies, projects, etc. Unlike scaling errors, EDP mistakes can not be corrected for when post processing the data. EDPs will not work perfectly for all images. A few small fusion and disintegration errors are common in all photoanalysis software.
WipFrag Momentum can be calibrated. The process does take some time and requires multiple analysis and sieve samples.

Stop belt with material present.

Manually capture image with Momentum, analyze image and save results.

Remove the section of material from belt (that was in the image) and sieve.

Repeat this procedure at least 5 times to get adequate representation of material. Email all of the results to We will use our calibration tools to get a Rosin-Rammler or SweBrec calibration target and email you back the figures. You can then set these values in the Sieve options menu to finalize the calibration.
WipFrag supports OPC Data Access version 2.05 as a server or as a client. OPC Data Access provides a means of moving data values between a server and client. When WipFrag is online cycling, WipFrag makes available the same data values written to the log file, e.g. D10, D25, D50, etc. at the end of each process cycle. Please refer to your manual for more information on OPC. The manual is available on the WipFrag Installation CD. If you have misplaced your CD please contact WipWare Technical Services.
Reflex cannot accurately be calibrated.
If using a Piccolo Pro3I framegrabber card, and you have a video signal coming in on all inputs, the computer may reboot when launching WipFrag with the 5.1 MultiCam drivers. To fix this, download and install the latest MultiCam drivers from Customer Download Area.
If you are using WipFrag as an OPC Client and you can connect to the server but are having difficulties browsing OPC tags (ex: structures infinitely looping) first make sure all DCOM permissions are correct for both the client and the server (see WipFrag OPC – Windows XP SP2.pdf on the WipFrag installation CD). If DCOM is fully configured properly and you are still unable to browse the tags on the server you can manually edit the OPCMap.txt file located in the WipFrag installation folder. This file holds all client/server mappings. You can use the formatting in the following examples to populate all desired mappings:

Camera 1/C1 D10 MyTags.Network2.Objects.WipFrag.iD10

Camera 1/C1 D20 MyTags.Network2.Objects.WipFrag.iD20

Camera 1/C1 D25 MyTags.Network2.Objects.WipFrag.iD25

Camera 1/C1 Nros2 MyTags.Network2.Objects.WipFrag.iNros2

Camera 2/C2 D10 MyTags.Network2.Objects.WipFrag.iD10

Camera 2/C2 D20 MyTags.Network2.Objects.WipFrag.iD20

Camera 2/C2 D25 MyTags.Network2.Objects.WipFrag.iD25

Camera 2/C2 Nros2 MyTags.Network2.Objects.WipFrag.iNros2 'Camera x' and 'Cx' indicate the camera number. Then a space followed by the value you wish to map. Next is a tab and then the item as located on the server (edit to match your server).
These ranges affect the minimum and maximum allowed shutter speed for the camera. However, these values are not represented in any units of time. Unfortunately, these ranges for the shutter speed cannot be easily converted to milliseconds (the conversion changes depending on many factors). Therefore, you will need to use trial and error by increasing/decreasing the values and taking note of the resulting shutter speeds displayed directly above these range values. To try and further explain, below is an example of its behaviour. However, the below numbers are NOT necessarily correct and are used only for demonstration.

Let’s say a system has the shutter limits set to 10-100.

You introduce a lot of light and find the shutter never goes below 0.3ms (while the image remains too bright), then 10=0.3ms.

You take away light and the shutter never goes above 3ms (while the image remains too dark), then 100=3ms.

However, the entire shutter range of the camera cannot be expressed with a linear equation and you will probably find that solving for values outside of this range will be incorrect. For example, you may expect 1=0.03ms, but you should expect to find that this is incorrect once you actually enter these values into the software.