Hardinge HLV with chucks, steadies, taper turning and a full set of collets.
It remains to be seem how much of a strip down and rebuild job it is going to be, not been run in 12 years apparently, so I bet the lube tanks are going to be gnarly. Hopefully nobody used soluble oil in the thing.
Now just waiting for the pallet with 770kg of lathe on it to arrive, then comes the 'sort out a three phase supply' fun.
Just received 2 pairs of optical transceivers today to experiment with high-speed optical links.
(Those are bidirectional 1.25Gbps 1x9 transceivers.)
The postman brought my nice Katsu mini drill press today.
So far, I'm favourably impressed. I'm sure the simple triac based variable speed motor controller can be improved, but it's a surprisingly solid machine. The oversized base is cast iron and the head, cast alloy. In addition to the variable speed, there's a 3 step pulley change allowing it to get up to 8500rpm - An ideal companion for my big Sealey pillar drill when using small drill bits. Something I was worrying about when I ordered it was accuracy, but I can't detect any slack at all between the quill and the head casting and there's no noticeable runout on the little 6mm chuck. No flex between the head and the base either.
The wiring looks ok. It's properly earthed and there are decent insulated crimps and additional fibreglass sleeving where the wires pass the motor. I might put some additional strain relief on the motor wiring though as the motor and pulleys go up and down with the quill.
Overall, really chunky for such a small capacity drill press. The motor is only a 100W brushed, but that ought to be sufficient for small diameter drills - maybe I'll experiment with a brushless one at some point as there's plenty of room.
P.S. The adjustable quill stop seems a bit odd - I think they've put the scale sticker on in the wrong position!
Yea, I am NOT a fan of NMOS (Which does NOT refer to the old logic family with no noise margin).
I've got Nevion "control" (the guys who do not believe in multicast routing protocols), and there's LAWO "control" (the solution that can't even control all of their own gear nor interoperate with their own control system) around the corner. I am not impressed with either.
I've got Nevion "control" (the guys who do not believe in multicast routing protocols), and there's LAWO "control" (the solution that can't even control all of their own gear nor interoperate with their own control system) around the corner. I am not impressed with either.I thought Nevion was basically a bit of Sony?
Lawo is a funny one, I mean Ember+ is basically what happens when you give a German SNMP and tell them to make something almost, but not completely, completely unlike this.... They could SO easily have grafted on a few extensions for discoverability and realtime data and it would have just worked, but no, have you SEEN that spec? It has wonders in it, like the fact that the 'oids' are NOT required to be consistent from one run to the next, it is the text strings you have to match on.... <Spit>. And then you get VSM, classic consultantware.
Trouble is, with GV clearly doing the pivot into being a software company with cloudish aspirations, that don't leave a whole lot of choices, BNCS maybe?
The thing that narks me about the whole NMOS thing is that absolutely NO consideration appears to have gone into doing little things like plugging an IP truck into an IP facility over IP.... You pretty much CANNOT do it without a LOT of forward planning on both ends, and this even applies when using trucks from a few different vendors on one job, it is all SDI and MADI between the islands of IP.
</rant>
MDNS? Yea, that was AMWA/NMOS wanting to do the existing tools thing, completely unsuitable IMHO for this kind of scale (Especially the way NMOS does it).
Mind you AES dropped the ball as well with not putting the minimal amount of metadata needed to successfully decode an AES67 flow into the flow itself... Grumble.
There does seem to be a LOT of reinventing the cockup going around, the control systems are grossly unsuitable (They think in terms of routers still, not controlling endpoints and trunking), the customers don't understand the technology, the standards folks mostly don't understand broadcast, and the SIs are doing their usual trick of over promising and then blaming the vendors.
I loved that there really does not seem to be a way to build an NMOS configuration in advance of having all the kit on site and connected to the registration server, I mean being able to build the config back at the office before getting to that expensive time on site would make all this shit way too easy would it not?
While SDI had its issues, god knows, SWP08, Quartz and TSL UMD got you control of basically everything, would that the new world was as easy.
Just received 2 pairs of optical transceivers today to experiment with high-speed optical links.
(Those are bidirectional 1.25Gbps 1x9 transceivers.)
I casually put into operation 2 links of 4x25Gbit/s capacity today. (4 wavelengths in one fiber, 1295.56, 1300.05, 1304.59 and 1309.14 nm, adding up to 100Gbit/s, 100GBASE-LR4, IEEE802.3ba-2010)
1.25 Gbit is impressive, and more than most people would need for many different purposes, but high-speed it is not, not anymore. (I run singlemode 10Gbit links at home, so it is common.)
Granted, a coherent 100G system, that is something extra. Not for the faint of heart. 4x25G is much easier.
1 Gbsps is indeed considered "high-speed communication" in the digital design context these days. Just a technical term. I thought we were on some electronics forum, not Twitter.
As the word 'experiment' and the bare transceivers suggested, my intent is to design my own links, using FPGA and stuff. Prototype stuff. "Advanced" DIY. Not using existing networks and switches.
While doing that for 1 Gsps is already challenging, it's doable. But I dare you to do that kind of thing with 25 Gbps or higher. This is certainly nothing "casual" ( ), unless you are just using off-the-shelf equipment, which I thought was clearly not the case here, but if it wasn't clear, now it should be. =)