Cookies are used on our website. Some of them are mandatory, while others allow us to improve your user experience on our website.
Essential cookies are required for basic website functions. This ensures that the website functions properly.
Name | fe_typo_user |
---|---|
Provider | TYPO3 |
Purpose | This cookie is a standard session cookie of TYPO3. It saves the entered access data for a closed area when a user logs in. |
Cookie life cycle | End of session |
Name | be_typo_user |
---|---|
Provider | TYPO3 |
Purpose | This cookie tells the website whether a visitor is logged into the Typo3 backend and has the rights to manage them. |
Cookie life cycle | End of session |
Name | PHPSESSID |
---|---|
Provider | php |
Purpose | PHP data identifier, set when the PHP session() method is used. |
Cookie life cycle | End of session |
Name | __utma |
---|---|
Provider | |
Purpose | In this cookie the main information is stored to track visitors. In this cookie, a unique visitor ID, the date and time of the first visit, the time at which the active visit is started and the number of all visitors that a unique visitor has made to the website is stored. |
Cookie life cycle | 2 years |
Name | __utmc |
---|---|
Provider | |
Purpose | This cookie belongs to the past and is no longer used by Google Analytics. For the backwards compatibility of pages that still use the urchin.js tracking code, this cookie is still written and expires when the browser is closed. However, this cookie does not need to be considered when debugging and using the new ga.js tracking code. |
Cookie life cycle | Session |
Name | __utmz |
---|---|
Provider | |
Purpose | This cookie is the visitor resource cookie. It contains all visitor resources information of the current visit, also information that was passed on via campaign tracking parameters. This cookie also stores whether the visitor source of the last visit was different from the current one. If no information about the visitor source can be determined, the cookie is not changed. In this way, Google Analytics can associate visitor information such as conversions and e-commerce transactions with a visitor source. The cookie does not contain historical information about past visitor sources. |
Cookie life cycle | 6 months |
Name | _ga |
---|---|
Provider | Google Tag Manager Google |
Purpose | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
Cookie life cycle | 2 years |
Name | _gid |
---|---|
Provider | |
Purpose | Used by Google Analytics to limit the request rate. |
Cookie life cycle | 1 day |
Name | _ym_d |
---|---|
Provider | Yandex |
Purpose | Contains the date of the visitor's first visit to the website. |
Cookie life cycle | 1 year |
Name | _ym_isad |
---|---|
Provider | Yandex |
Purpose | Determines whether a user has ad blockers. |
Cookie life cycle | 2 days |
Name | _ym_uid |
---|---|
Provider | Yandex |
Purpose | Used to identify site users. |
Cookie life cycle | 1 year |
M130162 | |
Chemistry, Geology / mineralogy | |
< 80 µm | |
d50 < 10 nm | |
100 ml | |
To achieve a maximum fineness, we recommend using a Planetary Micro Mill PULVERISETTE 7 premium line with a ball acceleration of up to 95 g. We recommend using bowls and balls made of zirconium oxide. |
|
Planetary Micro Mill PULVERISETTE 7 premium linemain disk speed: 1100 rpm |
|
Equipment: |
80 ml grinding bowl made of zirconium oxide (ZrO2) + 100 g of 2,0 mm Ø ZrO2 grinding balls. |
|
|
20 g | |
|
< 80 µm (checked by optical microscopy) | |
|
+ 45 ml water | |
|
15 min | |
|
d50 < 150 nm | |
|
In our first test, we used 20 g of sample and started grinding with 2 mm Ø grinding balls. To maintain a motor oil like slurry (for an optimum grinding result), we added 45 ml of water.
To avoid over pressure, we ground the sample in steps of 3 minutes, followed by a programmed pausing time of 10 minutes. After several cycles, the outside temperature of the bowl should be checked (remain below 80°C); grinding time or programmed pausing time might be readjusted afterwards. This is counting for the following grinding trial too.
For a proper detection of fine particles (< 2 µm), Mie parameters are required. We don’t provide proper parameters for barium titanate and used best fitting. With this parameters, we found d50 < 150 nm after a total grinding time of 15 minutes. By proceeding grinding, equal d50 has been detected after 30 minutes of grinding too. For this, the used 2 mm grinding balls didn’t achieve a better grinding result.
A change of balls might be required (e.g. < 0,1 mm Ø) to improve the grinding result. We packed this sample for demonstration and used an equal perpetrated sample for pre grinding in result 2.
|
|
Download: | M130162_BaTiO3_-_2mm__15min.pdf |
|
Planetary Micro Mill PULVERISETTE 7 premium linemain disk speed: 1100 rpm |
|
Equipment: |
80 ml grinding bowl made of zirconium oxide (ZrO2) + 100 g of 0,1 mm Ø ZrO2 grinding balls. |
|
|
5 g | |
|
d50 < 150 nm (pre ground analogue result 1) | |
|
+ 10 ml water | |
|
+ 90 min (∑ 105 min) | |
|
d50 < 125 nm | |
|
In this trial, we started grinding with 2 mm Ø grinding balls for the first 15 minutes analogue result 1 and changed the balls to 0,1 mm Ø afterwards.
Now we proceeded grinding with 0,1 mm Ø grinding balls for 30 minutes (total 45 min) and checked the fineness again with the same Mie parameters we used in result 1. After a total of 45 minutes, the result has been almost equal without big changes.
We proceeded grinding for a further hour (total 105 min.) and found a d50 < 125 nm. For this, even with smallest available grinding balls, particle size does not change significantly.
For a better grinding result, it might be possible using grinding agents like acids, bases, tensides or salts which might be able to improve the grinding process and show a better fineness. Also other liquids like organic solvents (benzine, hexane, ethanol, etc) are plausible as well.
If proper Mie parameters can be provided, a recalculation of the measurements is possible to give a more precise result.
|
|
Download: | M130162_BaTiO3_-_0_1mm__105min.pdf |