- 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.
- 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)
- 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)
- 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.
However, if you continue to get XML errors even after restarting WipFrag then please contact WipWare Technical Support.
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:
- Example, if your Windows username is 'User': C:/Users/User/Documents/
- Start WipFrag and ensure the following directory structure has been created:
- 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.
- Go to 'Start > Program Files > WipFrag' and run 'TrueUpdate Client'
- 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.
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.'
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 0.5.0.0. Search your installation CD/folder for a copy of it, or contact WipFrag Technical Services for an update.
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.
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
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.
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 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.
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.
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.
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 firstname.lastname@example.org.
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.
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.
To fix this, download and install the latest MultiCam drivers from Customer Download Area
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).
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.