Institute of Metals Division - A New Method to Test Steel for Temper Brittleness (TN)

The American Institute of Mining, Metallurgical, and Petroleum Engineers
Abdul-Fattah K. Kaddou P. C. Rosenthal
Organization:
The American Institute of Mining, Metallurgical, and Petroleum Engineers
Pages:
2
File Size:
125 KB
Publication Date:
Jan 1, 1961

Abstract

Email to a Friend
THE authors have studied the problem of temper brittleness in steel1 employing an internal friction method. The specimens are in the form of wire, 14 B and S gage (0.064 in diam), 6 in. long. It was very desirable to have an apparatus to test the wire specimens for temper brittleness without making standard notched-bar Izod or Charpy impact tests. Such a device would have two favorable advantages: the first is that no standard impact specimen would be necessary, thus saving time and labor; the second is that there would be a direct correlation with internal friction results, thus eliminating the size factor if standard impact specimens had to be used. A search was made without result to find a commercial apparatus for this purpose. The literature was surveyed to investigate if such a test had been utilized. No such work has been reported in the literature; however, zapffe2 has described an apparatus used for testing for hydrogen embrittlement in
Citation

APA: Abdul-Fattah K. Kaddou P. C. Rosenthal  (1961)  Institute of Metals Division - A New Method to Test Steel for Temper Brittleness (TN)

MLA: Abdul-Fattah K. Kaddou P. C. Rosenthal Institute of Metals Division - A New Method to Test Steel for Temper Brittleness (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 :