BreakPoint
Random Posts (An alternate to side discussions)
@Blokk wrote:
@Ben wrote:
Agreed and so we went with the mechanical dial version when we place the order on Saturday. The safe will weigh in at just over 1000 lbs. They will bring in three brutes and an electric dolly to climb the steps in the front yard.
Ben
That is huge, roughly 500kg !!
It is a good thing, you pay for a two in one product. You can use it as a press. Press cheese, or post apocalyptic newspapers! 🙂
That makes me wonder...
What else can Ben use his safe for? I'll start with the obvious.
@Blokk wrote:
@Ben wrote:
Agreed and so we went with the mechanical dial version when we place the order on Saturday. The safe will weigh in at just over 1000 lbs. They will bring in three brutes and an electric dolly to climb the steps in the front yard.
Ben
That is huge, roughly 500kg !!
It is a good thing, you pay for a two in one product. You can use it as a press. Press cheese, or post apocalyptic newspapers! 🙂
Once it is bolted down to the reinforced concrete slab it would be quite an undertaking to use that way.
We have been planning on getting one for years and the time has finally come. I think it is quite pretty but I have to confess I used to work for Diebold back in the late 70's and had the chance to work with REAL safe crackers. One of which was part of a national board of safe crackers. I watched him break into and old cash machine and I was impressed. He left the safe more secure, after repairing the damage he did breaking in than before.
How he did it.
The machine in question had a combination that only the fired bank manger knew. So he located an exact duplicate model and he studied the mechanical working of one that he could get into. He took careful measurements and examined the mechanical workings to find the weakest point. In this case it was a few lever made rom aluminum that did nothing aside from move the bolts in/out. Once extended the actuators were not used. He attacked them by first drilling and tapping hole that were aligned with each of the bolts. Inserted screws into the threaded holes and gradually cranked down on each pushing the bolts back clear of the jam. Loosened his screws and the door swung right open. After replacing the aluminum components then inserting and welding hardened screws into the holes he drilled and then some touch-up paint... done!
BTW:
If he was going to be doing the same thing to a walk-in vault, he said he would attack a wall near the door and then insert a mechanical arm to punch the emergency release located inside the vault. Well I thought it was interesting!
Ben
While it's known by old Tek fans (old Teks, fans could be younger 😉 ) ...
Beside the fact that you find the schematics in the (good old days) manuals ... the Tek manuals writer included some fun.
Maybe a good idea for the NI writers to motivate customers to RTFM 🙂
Note: If you have serious products, you don't have to serious all the time 😄
Here an example I just found in an old manual (1963) I was handed over to save it from the dumpster (and already found a lucky new owner that owns such a device)
@Henrik_Volkers wrote:
While it's known by old Tek fans (old Teks, fans could be younger 😉 ) ...
Beside the fact that you find the schematics in the (good old days) manuals ... the Tek manuals writer included some fun.
Maybe a good idea for the NI writers to motivate customers to RTFM 🙂
Note: If you have serious products, you don't have to serious all the time 😄
Here an example I just found in an old manual (1963) ...
I have encountered a few of those in code developed by one-man-shops that obviously were a bit challenged by LabVIEW. In one application the previous developer had dropped the Head explodes gif
on the block diagram and soon after ran away from that job (most likely) screaming. Thinking now... Was that the same application where I chased down a problem to a case with the comment "This should never happen." ?
I have been tempted to add some humor in the low-level VIs I have developed over the years, but since I code for others, I have resisted doing so. Chances are it will go unseen. I have a theory that goes;
The issue with writing a perfect sub-VI is chances are nobody will ever look at it.
Ben
@Ben wrote:
@Henrik_Volkers wrote:
While it's known by old Tek fans (old Teks, fans could be younger 😉 ) ...
Beside the fact that you find the schematics in the (good old days) manuals ... the Tek manuals writer included some fun.
Maybe a good idea for the NI writers to motivate customers to RTFM 🙂
Note: If you have serious products, you don't have to serious all the time 😄
Here an example I just found in an old manual (1963) ...
I have encountered a few of those in code developed by one-man-shops that obviously were a bit challenged by LabVIEW. In one application the previous developer had dropped the Head explodes gif
on the block diagram and soon after ran away from that job (most likely) screaming. Thinking now... Was that the same application where I chased down a problem to a case with the comment "This should never happen." ?
I have been tempted to add some humor in the low-level VIs I have developed over the years, but since I code for others, I have resisted doing so. Chances are it will go unseen. I have a theory that goes;
The issue with writing a perfect sub-VI is chances are nobody will ever look at it.
Ben
Commited this yesterday
Got an email a while back from someone I had worked with quite a long time ago on my original contracting gig, post Lockheed-Martin. I had created my own blank sub-vi templates, with my preferred error in/error outs, etc., and had prepopulated the "Documentation" part, allowing users to just over write some initial data. To make it easier to find those that hadn't been update I used the developer name "Todeleo Goldfarb", which was a old family joke, dating to when my mom had seen that name in the newspaper in Hawaii. The email told me that in some fairly recent work, at the original company that I had worked at, thought the business group I was in had been dissolved, he had found vi's (newish ones) with that name in them, knew where the original template had come from. I hadn't thought to drop gifs on diagrams though. I have found amusing "comments" in obscure corners of both sub-vis and in text based code.
This gem makes me giggle every time I see it. The code in the "OCR" sub-VI makes me happy...
It's in a package released by a very prominent LabVIEW solutions provider. 😄 It should remain, not only because it's funny, but because it would make Rube Goldberg proud.
@jcarmody wrote:
This gem makes me giggle every time I see it. The code in the "OCR" sub-VI makes me happy...
I loved that code. If I'm not mistaken that was used at one point to find what state in an event structure was handling a value change for a control, for example. Before LabVIEW scripting had the ability to return information like "[0] Timeout", someone wrote code to get the image of the event structure, then perform OCR on the text at the top. This of course had issues with Clear-Type, or localization that may change that text causing the OCR to crap out. Luckily it was only a couple versions of LabVIEW later that I think the official scripting methods were added for the event structure. Still I love these hacky solutions.
