Hahaaha as someone from Eindhoven, where Philips did and still does most of its R&D, this is frighteningly recognizable.
The scary part is that most departments in Philips still prefer heavy processes over progress. I, for one, didn't last more than 6 weeks there.
Re:The void left by the parallel port
by billforsternz on Friday May 06, 2016 @05:22AM
(#11642674)
We were working for the Telecommunications and Data Systems division in Hilversum. A tiny division by Philips standards, but huge relative to our lab in NZ.
Sure, but I bet the culture at Philips was similar :) thanks for the anecdotes! :)
Re:The void left by the parallel port
by billforsternz on Friday May 06, 2016 @06:10AM
(#11642821)
Yes of course the Hilversum operation was no doubt a mini version of the huge R&D operations in Eindhoven. I did enjoy the company of the Dutch engineers. I think my phonetic Dutch pronunciation amused them. I think :)
Hrmm, small world I work for a small company in NZ that used to be part of the post office, telecom and now we're privately owned. We repair Telco equipment. I am sure one of our PABX guys would be familiar with the Philips PABX. I am on the transmission team so it's not really something I would have seen. We still have a fots and rn64 though!
Re:The void left by the parallel port
by billforsternz on Friday May 06, 2016 @05:28AM
(#11642694)
Huge numbers of locally developed Philips small business exchanges were sold in the 1980s. They were pretty simple and robust, I wouldn't be surprised if there were still some in use today.
Now I was young and dumb at the time, and I had decided for some reason to jokingly call the simple bit bashing communication protocol I'd invented to talk to my chess computer "V.69" (The V series protocols - eg V.24 = RS-232 in the USA were big at the time). A V.69 port had actually made it into the final schematics for our board. It was just 5 logic level pins (two inputs two outputs plus ground) - and in production it would not have any impact - but it was possible to solder a 5 pin header onto the pins, and hook it up to a PC running the same terminal software previously discussed - If such a PC was connected my embedded code would emit diagnostic information.
We had many meetings during our visit, with the typically gruff non-nonsense Dutch engineers and their huge vats of extraordinarily strong coffee. One of them was with "the Standards guy" who wanted to audit compliance to all possible standards - I was able to spectate mainly as it was hardware stuff. But suddenly he was pointing at the V.69 connector, clearly labelled as such. We'd forgotten all about it. Us> "Oh well, arrrgh, yes. It's a diagnostic port - for the lab only - no impact on production - the header is just omitted." Him> "But what is this V.69 standard?". Us (hopefully)> "Well, it's just a 5v serial diagnostics standard". Him> "Okay, yes I've heard of it". So as is often the case, the need to save face saved the day.