Thermoelectrics enable the direct conversion of heat into electrical energy - and vice versa. This makes them interesting for a range of technological applications. In the search for thermoelectric materials with the best possible properties, a research team at TU Wien investigated various metallic alloys. A mixture of nickel and gold proved particularly promising. The researchers recently published their results in the renowned journal "Science Advances".
Using thermoelectrics to generate electricity is nothing new. Since the middle of the 20th century, they have been used to generate electrical energy in space exploration, but thermoelectrics are also used in everyday applications such as portable refrigerators. Moreover, they could also be used in industrial environments to convert waste heat into green electricity, to name just one of the potential applications.
How thermoelectricity works
The thermoelectric effect is based on the movement of charged particles that migrate from the hotter to the colder side of a material. This results in an electrical voltage - the so-called thermoelectric voltage - which counteracts the thermally excited movement of the charge carriers. The ratio of the built-up thermoelectric voltage and the temperature difference defines the Seebeck coefficient, named after the German physicist Thomas Johann Seebeck, which is an important parameter for the thermoelectric performance of a material. The important requirement here is that there is an imbalance between positive and negative charges, as they compensate each other.
Nickel-gold alloys with outstanding properties
Physicists from the Institute of Solid State Physics ( TU Wien ) have now succeeded in finding metallic alloys with high conductivity and an exceptionally large Seebeck coefficient. Mixing the magnetic metal nickel with the noble metal gold radically changes the electronic properties. As soon as the yellowish colour of gold disappears when about 10 % nickel is added, the thermoelectric performance increases rapidly. The physical origin for the enhanced Seebeck effect is rooted in the energy-dependent scattering behavior of the electrons - an effect fundamentally different from semiconducting thermoelectrics. Due to the particular electronic properties of the nickel atoms, positive charges are scattered more strongly than negative charges, resulting in the desired imbalance and hence a high thermoelectric voltage."Imagine a race between two runners, where one person runs on a free track, but the other person has to get through many obstacles. Of course, the person on the free track advances faster than the opponent, who has to slow down and change direction much more often," compares Andrej Pustogow, senior author of the study, the flow of electrons in metallic thermoelectrics. In the alloys studied here, the positive charges are strongly scattered by the nickel electrons, while the negative charges can move practically undisturbed.
Record breaking material
The combination of extremely high electrical conductivity and simultaneously a high Seebeck coefficient leads to record thermoelectric power factor values in nickel-gold alloys, which exceed those of conventional semiconductors by far. "With the same geometry and fixed temperature gradient, many times more electrical power could be generated than in any other known material," explains Fabian Garmroudi. In addition, the high power density may enable everyday applications in the large-scale sector in the future. "Already with the current performance, smartwatches, for instance, could already be charged autonomously using the wearer’s body heat," Andrej Pustogow gives as an example.Nickel-gold is just the beginning
"Even though gold is an expensive element, our work represents a proof of concept. We were able to show that not only semiconductors, but also metals can exhibit good thermoelectric properties that make them relevant for diverse applications. Metallic alloys have various advantages over semiconductors, especially in the manufacturing process of a thermoelectric generator," explains Michael Parzer, one of the lead authors of the study.The fact that the researchers were able to experimentally show that nickel-gold alloys are extremely good thermoelectrics is no coincidence. "Even before starting our experimental work, we calculated with theoretical models which alloys were most suitable," reveals Michael Parzer. Currently, the group is also investigating other promising candidates that do not require the expensive element gold.
Original publication
Fabian Garmroudi, Michael Parzer, Alexander Riss, Cédric Bourgès, Sergii Khmelevskyi, Takao Mori, Ernst Bauer, Andrej Pustogow: High thermoelectric performance in metallic NiAu alloys. Science Advances9, adj1611 (2023), https://doi.org/10.1126/sciadv.adj1611 .Andrej Pustogow Research Unit Functional and Magnetic Materials TU Wien +43 1 58801 13128 pustogow @ ifp.tuwien.ac.at www.ifp.tuwien.ac.at/forschung/pustogow-research/home Sarah Link Our website uses cookies and integrates content from third-party providers to ensure you get the best experience on our website, for analytical purposes, to provide social media features, and for targeted advertising. This it is necessary in order to pass information on to respective service providers. If you would like additional information about cookies and content from third-party providers on this website, please see our Data protection declaration.
CookieConsent Saves your settings for the use of cookies on this website. 1 year HTML Homepage TU Wien SimpleSAML This is needed to distinguish between the sessions of the logged-in users. session HTTP Login TU Wien SimpleSAMLAuthToken This is needed to distinguish between the sessions of the logged-in users. session HTTP Login TU Wien fe_typo_user Is needed so that in case of a Typo3 frontend login the session ID is recognized to grant access to protected areas. session HTTP Homepage TU Wien staticfilecache Is needed to optimize the delivery time of the website. session HTTP Homepage TU Wien These cookies help us to continuously improve our services and adapt our website to your needs. We statistically evaluate the pseudonymized data collected from our website.
_pk_id Used to store a few details about the user such as the unique visitor ID. 13 months HTML Matomo TU Wien _pk_ref Is used to store the information of the users home website. 6 months HTML Matomo TU Wien _pk_ses Is needed to store temporary data of the visit. 30 minutes HTML Matomo TU Wien nmstat Is used to record the behaviour on the website. It is used to collect statistics about website usage, such as when the visitor last visited the website. The cookie does not contain any personal data and is only used for website analysis. 1000 days HTML Siteimprove siteimproveses Is used to track the sequence of pages that a visitor views during his/her visit to the website. The cookie does not contain any personal data and is used solely for website analysis. session HTTP Siteimprove AWSELB Always occurs in pairs with siteimproveses (for load balancing on the provider server) session HTTP Siteimprove With the help of these cookies and third-party content we strive to improve our offer for our users. By means of anonymized data of website users we can optimize the user flow. This enables us to improve ads and website content.
_ga Is needed to distinguish the sessions of the users from each other. persistent HTTP Google Analytics _gali Is needed to determine which links are clicked on a page. expires immediately HTTP Google Analytics _gat This is a function-related cookie, whose tasks may differ. 2 years HTTP Google Analytics _gid Is needed to distinguish users and create statistics. 24 hours HTTP Google Analytics _gads Required to enable websites to display advertising from Google, including personalized advertising. 13 months HTTP Google Analytics _gac_ Required by advertisers to measure user activity and the performance of their advertising campaigns. 90 days HTTP Google Analytics _gcl_ Required by advertisers to determine how often users who click on their ads end up taking an action on their website. 90 days HTTP Google Analytics _gcl_au Contains a randomly generated user ID. 90 days HTTP _gcl_aw Is set when users click on a Google ad on the website and contains information about which ad was clicked. 90 days HTTP __utma Is used to record visits and visitors. 2 years HTTP Google Analytics __utmb Is used to detect new visits. 30 minutes HTTP Google Analytics __utmc Is used in connection with __utmb to determine whether it is a new (recent) visit. session HTTP Google Analytics __utmd Is used to store and track visitor journeys through the site and classifies them into groups (marketing/tracking). 1 second HTTP Google Analytics __utmt Is needed to limit the query rate on Google Analytics. 10 minutes HTTP Google Analytics __utmz Is needed to determine from which source/campaign visitors come. 6 months HTTP Google Analytics __utmvc Is needed to collect information about user behavior on multiple websites. This information is used to optimize the relevance of advertising on the website. 24 hours HTTP Google AdSense utm_source Is needed to tag URLs with parameters to identify the campaigns that forward traffic. expires immediately HTTP Google Analytics __utm.gif Is needed to save browser details. session HTTP Google Analytics gtag Is needed to perform remarketing. 30 days HTTP Google AdSense Is needed to perform remarketing. 2 years HTTP Google AdWords 1P_JAR Is needed to optimize advertising, provide ads that are relevant to users, improve campaign performance reports, or prevent users from seeing the same ads more than once. 2 years HTTP Is needed to activate targeted advertising. 2 years HTTP Google Analytics ANID Is needed to display Google ads on non-Google websites. 2 years HTTP Google AdSense APISID Unknown functionality 2 years HTTP Google Ads Optimization Is needed to profile visitors’ interests and display relevant ads on other websites. This cookie works by uniquely identifying your browser and device. 2 years HTTP Google AdSense CONSENT Is needed to store the preferences of visitors and personalize advertising. persistent HTTP DSID Is needed by DoubleClick for advertising displayed in various places on the web and used to store the preferences of users. 2 years HTTP Doubleclick Is needed to store user preferences and other information. This includes, in particular, the preferred language, the number of search results to be displayed on the page, and the decision whether or not to activate the Google SafeSearch filter. 2 years HTTP HSID Contains the Google account ID and the last login time of the user. 2 years HTTP Is needed by DoubleClick to record and report the actions of users on the website after viewing or clicking on one of the provider’s ads, with the purpose of measuring the effectiveness of an advertisement and displaying targeted advertisements to users. 2 years HTTP Doubleclick LOGIN_INFO Is used to store the credentials of users of Google services. 2 years HTTP Is used to store information about user settings. 6 months HTTP Is needed to link activities of visitors with other devices that are previously logged in via the Google account. In this way, advertising is tailored to different devices. 1 month HTTP Is needed by DoubleClick to determine whether advertising has been displayed correctly in order to make marketing activities more efficient. 1 year HTTP Doubleclick SAPISID Is needed by YouTube to store user settings and to calculate user bandwidth. persistent HTTP SEARCH_SAMESITE Enables servers to mitigate the risk of CSRF and information leakage attacks by specifying that a particular cookie may only be sent on requests originating from the same registerable domain. 6 months HTTP Contains the Google account ID and the last login time of the user. 2 years HTTP SIDCC Is needed to store information about user settings and information for Google Maps. 3 months HTTP SSID Is needed to collect visitor information for videos hosted by YouTube on Google Maps integrated maps. persistent HTTP __SECURE-1PAPISID Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP __SECURE-1PSID Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP __SECURE-3PAPISID Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP __SECURE-3PSID Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP __SECURE-3PSIDCC Is needed for targeting purposes to create a profile of the interests of website visitors. 2 years HTTP __SECURE-APISID Is needed to profile the interests of website visitors in order to display relevant and personalized advertising through retargeting. 8 months HTTP __SECURE-HSID Is needed to secure digitally signed and encrypted data from the unique Google ID and to store the last login time that Google uses to identify visitors, prevent fraudulent use of login data, and protect visitor data from unauthorized parties. This may also be used for targeting purposes to display relevant and personalized advertising content. 8 months HTTP __SECURE-SSID Is needed to store information about how visitors use the site and about the ads they may have seen before visiting the site. Also used to customize ads on Google domains. 8 months HTTP test_cookie Is set as a test to check whether the browser allows cookies to be set. Does not contain any identification features. 15 minutes HTTP VISITOR_INFO1_LIVE Is needed by YouTube to store user settings and to calculate user bandwidth. 6 months HTTP Is used to Enable ad delivery or retargeting 90 days HTTP Meta (Facebook) __fb_chat_plugin Is needed to store and track interactions (marketing/tracking). persistent HTTP Meta (Facebook) _js_datr Is needed to save user settings. 2 years HTTP Meta (Facebook) _fbc Is needed to save the last visit (marketing/tracking). 2 years HTTP Meta (Facebook) Is needed to store account data (marketing/tracking). 1 year HTTP Meta (Facebook) Is needed to store a unique session ID (marketing/tracking). 1 year HTTP Meta (Facebook) Is needed to log the screen resolution. 1 week HTTP Meta (Facebook) Is needed to serve ads and measure and improve their relevance. 3 months HTTP Meta (Facebook) Is needed to store logged in users (marketing/tracking). 90 days HTTP Meta (Facebook) _fbp Is needed to store and track visits to various websites (marketing/tracking). 3 months HTTP Meta (Facebook) datr Is needed to identify the browser for security and website integrity purposes, including account recovery and identification of potentially compromised accounts. 2 years HTTP Meta (Facebook) Is used for analysis purposes. Technical parameters are logged (e.g. aspect ratio and dimensions of the screen) so that Facebook apps can be displayed correctly. 1 week HTTP Meta (Facebook) Is needed to store browser details and security information of the Facebook account. 2 years HTTP Meta (Facebook) dbln Is needed to store browser details and security information of the Facebook account. 2 years HTTP Meta (Facebook) spin Is needed for promotional purposes and social campaign reporting. session HTTP Meta (Facebook) presence Contains the "chat" status of logged in users. 1 month HTTP Meta (Facebook) cppo Is needed for statistical purposes. 90 days HTTP Meta (Facebook) locale Is needed to save the language settings. session HTTP Meta (Facebook) Required for Facebook Pixel. 2 years HTTP Meta (Facebook) Required for Facebook Pixel. 2 years HTTP Meta (Facebook) c_user Required for Facebook Pixel. 3 months HTTP Meta (Facebook) bcookie Is needed to store browser data (marketing/tracking). 2 years HTTP li_oatml Is needed to identify LinkedIn members outside of LinkedIn for advertising and analytics purposes. 1 month HTTP BizographicsOptOut Is needed to save privacy settings. 10 years HTTP li_sugr Is needed to store browser data (marketing/tracking). 3 months HTTP UserMatchHistory Is needed to provide advertising or retargeting (marketing/tracking). 30 days HTTP linkedin_oauth_ Is needed to provide cross-page functionality. session HTTP lidc Is needed to store performed actions on the website (marketing/tracking). 1 day HTTP bscookie Is needed to store performed actions on the website (marketing/tracking). 2 years HTTP X-LI-IDC Is needed to provide cross-page functionality (marketing/tracking). session HTTP AnalyticsSyncHistory Stores the time when the user was synchronized with the "lms_analytics" cookie. 30 days HTTP lms_ads Is needed to identify LinkedIn members outside of LinkedIn. 30 days HTTP lms_analytics Is needed to identify LinkedIn members for analytics purposes. 30 days HTTP li_fat_id Required for indirect member identification used for conversion tracking, retargeting and analytics. 30 days HTTP U Is needed to identify the browser. 3 months HTTP _guid Is needed to identify a LinkedIn member for advertising via Google Ads. 90 days HTTP
