Go Back   The Supercar Registry > General Discussion > Supercar/Musclecar Discussion


Reply
 
Thread Tools Display Modes
  #1  
Old 12-02-2021, 01:00 PM
70 copo 70 copo is offline
Senior Member
 
Join Date: Oct 2000
Location: chillicothe Ohio 45601
Posts: 3,834
Thanks: 219
Thanked 1,231 Times in 576 Posts
Default 1969 Norwood Trim tag date anomaly's

After exchanging some PM's I have decided to start this thread myself to properly preserve the topic as searchable where several forum participants had asked questions pertaining to Body Plate data fields that have been observed to contain anomalous or questionable data fields.

The Factory called them Body Plates, the hobby generally calls them Trim Tags, Cowl Tags, or Body Tags.

The following are the questions submitted from the Christmas party thread:

Quote:
Originally Posted by Mr.Nickey Nova View Post
Here's one. Why were all trim tags in June of 69 at the Norwood Plant stamped (06A)??
Quote:
Originally Posted by 69LM1 View Post
Or April stamped 4L ?

Rich
Quote:
Originally Posted by rlw68 View Post
... and why did 02D get used for the first two weeks of March?? Inquiring minds want to know !

My bet is on the computer fumbling the leap year.

Quote:
Originally Posted by William View Post
Body tag questions would have to be directed to Fisher Body Production Control employees. They released the order to produce the body, including punching the tag. Chevrolet Final Assembly had nothing to do with the tag, never looked at it.

02D tags were built into March; there was no 03A for some reason.
Original thread is located here: https://www.yenko.net/forum/showthread.php?t=169828
Reply With Quote
Attachments - The Supercar Registry program unit.JPG key punch card.JPG Capture.JPG 5OR.jpg
O Garage vBulletin Plugins by Drive Thru Online, Inc.
Click here to view all the pictures posted in this thread...
  #2  
Old 12-02-2021, 01:19 PM
70 copo 70 copo is offline
Senior Member
 
Join Date: Oct 2000
Location: chillicothe Ohio 45601
Posts: 3,834
Thanks: 219
Thanked 1,231 Times in 576 Posts
Default

Given the numerous questions on what is basically the same general topic, I decided to explore for an answer in advance of the Christmas party, and the replies that I got were as follows: From the key punch ladies, "We keyed in what we had from the option sheets, what the machine spit out in the form of a completed punch card- well that could be a different story, and we did not have time to look or audit, that was done elsewhere"

From the Data processing guy: All these issues sound like defective switches in the key punch tabulation machine or more likely a punch card reader error .


This is a model 29 card punch station as used at Norwood from 1965-1972:
Attached Images
 
Reply With Quote
The Following User Says Thank You to 70 copo For This Useful Post:
NorCam (12-02-2021)
  #3  
Old 12-02-2021, 01:28 PM
70 copo 70 copo is offline
Senior Member
 
Join Date: Oct 2000
Location: chillicothe Ohio 45601
Posts: 3,834
Thanks: 219
Thanked 1,231 Times in 576 Posts
Default

Here is one of the punch cards generated by the key punchers. This card takes all the build content of the vehicle order and places it on this card in a form of punch code that can be deciphered and then re read by a card reader. The reader can then rebroadcast portions of the main punch card data as often as is needed for scheduling purposes. For the purpose of this discussion I will confine the topic to the body plates.
Attached Images
 
Reply With Quote
  #4  
Old 12-02-2021, 01:30 PM
70 copo 70 copo is offline
Senior Member
 
Join Date: Oct 2000
Location: chillicothe Ohio 45601
Posts: 3,834
Thanks: 219
Thanked 1,231 Times in 576 Posts
Default

Video is instructive:
Reply With Quote
  #5  
Old 12-02-2021, 01:37 PM
70 copo 70 copo is offline
Senior Member
 
Join Date: Oct 2000
Location: chillicothe Ohio 45601
Posts: 3,834
Thanks: 219
Thanked 1,231 Times in 576 Posts
Default

An additional source of error could also be a root programming error where the root data fields are improperly applied for the root batch, meaning the programming spool created for the production period contained a error carried forward and maintained until detected or a new programming spool was created.

Another excellent video:
Reply With Quote
  #6  
Old 12-02-2021, 01:40 PM
70 copo 70 copo is offline
Senior Member
 
Join Date: Oct 2000
Location: chillicothe Ohio 45601
Posts: 3,834
Thanks: 219
Thanked 1,231 Times in 576 Posts
Default

Programming Spool:
Attached Images
 
Reply With Quote
  #7  
Old 12-02-2021, 02:00 PM
70 copo 70 copo is offline
Senior Member
 
Join Date: Oct 2000
Location: chillicothe Ohio 45601
Posts: 3,834
Thanks: 219
Thanked 1,231 Times in 576 Posts
Default

So what I am saying is if the program spool (drum) is improperly formatted then the error will be a constant, meaning if read by a reader it will be reproduced as an error carried forward.

The key punch machine by its self was prone to errors also. These were related to internal switch failures which would conspire to punch nothing at all, punch the wrong character, or punch no character at all.

Finally the reader had the same error pretext meaning that the error could be at the reader and the reader only- at the point in plant where the Body plate was being read and then the data transmitted to the Graphotype where the Graphotype then punches the plate with an error.

So what do we have? Like almost everything else simple human error. or failure to properly maintain the system. (Again root cause is human error)


Drum programming at the key punch (human Error)
Defective switch at the key punch (Maintenance Problem)
Key Punch error (human Error)
Read error at the graphotype key card reader (Maintenance Problem)

The consensus is that an incorrectly coded "bad programming drum" is the most likely cause of these batch anomalies.

Ken Shirriff is a wealth of knowledge on these machines the following describes the problems and complexity of how these machines worked along with the various modes of failure.
http://www.righto.com/2017/12/repair...-keypunch.html
Reply With Quote
The Following 3 Users Say Thank You to 70 copo For This Useful Post:
L_e_e (12-02-2021), mssl72 (12-02-2021), SS427 (12-03-2021)
  #8  
Old 12-02-2021, 02:25 PM
AnthonyS's Avatar
AnthonyS AnthonyS is offline
Yenko Advertising Member
 
Join Date: Dec 2017
Location: SoCal
Posts: 3,045
Thanks: 122
Thanked 607 Times in 366 Posts
Default

Very interesting. Thanks for undertaking this!
Anthony
Reply With Quote
The Following User Says Thank You to AnthonyS For This Useful Post:
70 copo (12-02-2021)
  #9  
Old 12-02-2021, 03:18 PM
Keith Seymore's Avatar
Keith Seymore Keith Seymore is offline
Yenko Contributing Member
 
Join Date: Feb 2009
Location: Motor City
Posts: 2,493
Thanks: 2,613
Thanked 4,476 Times in 1,242 Posts
Default

Thank you, Phil.

Good information, which I'm sure transfers to other assembly locations and GM nameplates (….like Pontiac!).

K
__________________
'63 LeMans Convertible
'63 Grand Prix
'65 GTO - original, unrestored, Dad was original owner, 5000 mile Royal Pontiac factory racer
'74 Chevelle - original owner, 9.85 @ 136 mph best
Reply With Quote
The Following User Says Thank You to Keith Seymore For This Useful Post:
70 copo (12-02-2021)
  #10  
Old 12-02-2021, 03:21 PM
William William is offline
Yenko Contributing Member
 
Join Date: Jun 2001
Location: New Berlin WI USA
Posts: 2,468
Thanks: 194
Thanked 2,113 Times in 664 Posts
Default

Another Norwood body tag anomaly involves standard trim converts built as of March 3, 1969. No more X44.
__________________
Learning more and more about less and less...
Reply With Quote
The Following 4 Users Say Thank You to William For This Useful Post:
69M22Z (12-04-2021), 70 copo (12-02-2021), rlw68 (12-04-2021), Steve Shauger (12-02-2021)
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 08:41 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.