Institute of Metals Division - Some Aspects of Martensitic Transformation in Copper Aluminum Alloys (TN)

The American Institute of Mining, Metallurgical, and Petroleum Engineers

Rajendra Kumar V. Balasubarmanian

Organization:: The American Institute of Mining, Metallurgical, and Petroleum Engineers
Pages:: 2
File Size:: 304 KB
Publication Date:: Jan 1, 1961

Abstract

Email to a Friend

ISOTHERMAL formation of martensite in a copper-aluminum-nickel alloy was previously reported by Hull and Garwood.' In the present work an attempt has been made to investigate some of the character- istics of the formation of isothermal martensite in binary copper-aluminum alloys containing 14.00 and 14.50 pct Al, respectively. Chill-cast alloys were prepared from OFHC copper and aluminum of greater than 99.5 pct purity. They were homogenized for 24 hr at 950° C. Polished samples were soaked at 1000°C and quenched in water to retain the p phase untransformed; martensite did not form during the quench. The surface was then repolished for isothermal microscopic studies at room temperature. The salient features of the martensitic transformation in copper-aluminum alloys observed in this investigation are: a) The transformation progresses (i) by nuclea-tion at new sites and (ii) by simultaneous slow isothermal growth of existing martensite plates. Slow isothermal growth of martensite has previously been observed by Holden2 in an uranium-chromium alloy and by Hull and Garwood in copper-aluminum-nickel alloy. b) Martensite plates nucleate preferentially at the pin holes formed during the casting of the specimen, Fig. 1. c) Some of the martensite plates pass right through other plates lying in their path, Fig. 1. d) Martensite plates cross grain boundaries without any change in the direction of growth. e) An irregular network of markings, Fig. 2, appears simultaneously with the formation of martensite. It was less prominent in the case of 14.5 pct alloy. The markings may arise due to spontaneous deformation under the lattice strains of the martensitic transformation. Crossing of martensite plates was first observed by Kulin and cohen3 when a high-nickel steel was cooled to 77°K. They suggested that the rapidly advancing plates atquire considerable kinetic energy and strike the obstructing plate with a momentum so as to nucleate the process on the other side of the plate. This, however, fails to explain the present observation where the slow isothermally growing martensite plates cross each other. Such plates would not possess large momentum to bodily displace the obstructing plate. Fig. 1 shows the martensite plates crossing each other without body displacements. This should be contrasted with Fig. 3 of Kulin and Cohen's paper where crossing of plates is accompanied by shearing or body displacements of the plates. The present observations can, how-

Citation

APA: Rajendra Kumar V. Balasubarmanian (1961) Institute of Metals Division - Some Aspects of Martensitic Transformation in Copper Aluminum Alloys (TN)

MLA: Rajendra Kumar V. Balasubarmanian Institute of Metals Division - Some Aspects of Martensitic Transformation in Copper Aluminum Alloys (TN). The American Institute of Mining, Metallurgical, and Petroleum Engineers, 1961.

Export

CSV

RIS

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 :