Technical Papers and Discussions - Miscellaneous Metals and Alloys - An Electron Diffraction Study of Oxide Films Formed on Alloys of Iron, Cobalt, Nickel and Chromium at High Temperatures (Metals Tech., Oct. 1946, T. P. 2069, with discussio

The American Institute of Mining, Metallurgical, and Petroleum Engineers
J. W. Hickman E. A. Gulbransen
Organization:
The American Institute of Mining, Metallurgical, and Petroleum Engineers
Pages:
27
File Size:
1011 KB
Publication Date:
Jan 1, 1947

Abstract

In a previous paper' the authors have investigated the structure of the oxide films formed on most of the metals that make up the alloys of this study. The metals were studied in order to provide basic information on the structures, both physical and chemical, of the oxide films and to determine how these structures are effected by the temperature, time of oxidation, and surface preparation. It was felt that an understanding of the physical and chemical structure as well as the stability of the oxide film might furnish clues as to the nature of the reaction process and the protective quality of the film. The oxidation of the metals was studied over the temperature range 300' to 7o0°C. except for copper, wherc the range selected was 100' to 500°C. The results of these studies were presented in graphical form as existence diagrams of the oxides on a time-temperature scale. For some of the metals the existence diagrams were simple and showed few chemical transitions, but there were numerous cases where the physical state of the oxide surface was a function of time and temperature. In general the physical state of the oxide surface changed with increasing temperature so as to increase the sharpness of the diffraction patterns and to cause orientation effects to be more pronounced. Deviatiois in lattice Darameters from X-ray values were noted. In general these deviations were of positive nature and may be due to solid solution of the metal in the oxide lattice. This effect might be expected in thin oxide films. In a study of the oxidation of alloys containing two or more metals, there may arise the complicating factor of identification of the oxides formed. A thorough understanding of the oxides formed on the pure metals, therefore, was, essential before investigation of the oxidation of alloys. In this paper it is our purpose to present a study of the following problems: 1. The existence diagrams of various alloys. 2. The effect of the structure of the alloying metal on the existence diagram of iron. 3. The effect of the percentage of chromium on the oxides formed on Fe-Cr alloys. 4. The relationships, if any, between the oxides formed and the protective quality of the oxides. The following alloys are included in this study: alloys of iron with body-centered cubic, face-centered cubic and other metals, 13 Cr-Fe, 18-8 stainless steel, K4²B, Nichrome V, Hipernik, Inconel, Stellite "²I," Refractaloy, Kovar, mild steel, a series of Cr-Fe alloys and a series of Co-Fe alloys. Since many of the commercial alloys in this list contain more than two metals, various complicating factors in the identification of the oxides formed may arise.
Citation

APA: J. W. Hickman E. A. Gulbransen  (1947)  Technical Papers and Discussions - Miscellaneous Metals and Alloys - An Electron Diffraction Study of Oxide Films Formed on Alloys of Iron, Cobalt, Nickel and Chromium at High Temperatures (Metals Tech., Oct. 1946, T. P. 2069, with discussio

MLA: J. W. Hickman E. A. Gulbransen Technical Papers and Discussions - Miscellaneous Metals and Alloys - An Electron Diffraction Study of Oxide Films Formed on Alloys of Iron, Cobalt, Nickel and Chromium at High Temperatures (Metals Tech., Oct. 1946, T. P. 2069, with discussio. The American Institute of Mining, Metallurgical, and Petroleum Engineers, 1947.

Export
Purchase this Article for $25.00

Create a Guest account to purchase this file
- or -
Log in to your existing Guest account

Unexpected error retrieving advertisement for PageView: Home_Index, Key: SidebarTop Name : Microsoft.Data.SqlClient.SqlException Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.) Stack : at Microsoft.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod(Exception e) at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen() --- End of stack trace from previous location --- at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenAsync(CancellationToken cancellationToken, Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.InitializeReaderAsync(AsyncEnumerator enumerator, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.MoveNextAsync() at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable`1 asyncEnumerable, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable`1 asyncEnumerable, CancellationToken cancellationToken) at OneMine.Advertisements.Data.Queries.AdvertisementQueries.GetActiveAdvertisementByNameKeyAsync[T](Guid siteId, String pageViewName, String placementKey, CancellationToken cancellationToken) in D:\a\1\s\Lib\Data\Advertisements\Data\Queries\AdvertisementQueries.cs:line 39 at OneMine.Web.ViewComponents.ZoneTagViewComponent.InvokeAsync(String pageViewName, String placementKey) in D:\a\1\s\Web\ViewComponents\ZoneTagViewComponent.cs:line 84 -- Inner Exception -- Name : System.ComponentModel.Win32Exception Message: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. Stack :