Difference between revisions of "User talk:ForceFlow"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
So, what was ultimately wrong with the M-200 data signal chart? It looks like a lot of continuity test points were lost with the new chart.--[[User:Jimpal|Jimpal]] ([[User talk:Jimpal|talk]]) 20:57, 18 March 2016 (CDT) | So, what was ultimately wrong with the M-200 data signal chart? It looks like a lot of continuity test points were lost with the new chart.--[[User:Jimpal|Jimpal]] ([[User talk:Jimpal|talk]]) 20:57, 18 March 2016 (CDT) | ||
| + | |||
| + | |||
| + | Please forward the inconsistencies in the chart, please. Doing a cursory search over the chart, I could not find any. However, I did not use a fine-toothed comb. I would rather see a chart that had more info. If you've ever had to diagnose a broken trace on a Bally, the more info definitely helps. I've always used the schematics, but a chart would be better, provided that it is accurate.--[[User:Jimpal|Jimpal]] ([[User talk:Jimpal|talk]]) 10:02, 19 March 2016 (CDT) | ||
Revision as of 09:02, 19 March 2016
So, what was ultimately wrong with the M-200 data signal chart? It looks like a lot of continuity test points were lost with the new chart.--Jimpal (talk) 20:57, 18 March 2016 (CDT)
Please forward the inconsistencies in the chart, please. Doing a cursory search over the chart, I could not find any. However, I did not use a fine-toothed comb. I would rather see a chart that had more info. If you've ever had to diagnose a broken trace on a Bally, the more info definitely helps. I've always used the schematics, but a chart would be better, provided that it is accurate.--Jimpal (talk) 10:02, 19 March 2016 (CDT)