Proxxon KT150 CNC conversion

Last year my super loving wife managed to purchase for me the Proxxon  KT 150 coordinate table . The idea was to convert it to a CNC.

proxxon kt150This year, after I have built a Prusa I3 printer, I have finally  moved forward with the Proxxon KT 150 CNC conversion. Starting from product specifications and a few  measurements I’ve managed to design, with the help of OpenSCAD , some great NEMA 23 mounts for the Proxxon KT 150. The motors are the ones that SparkFun sells but I have bought them from a great local supplier RoboFun. Specifications for the stepper motors can be found here.

nema23 Without further ado, I would like to introduce you to my version of KT 150 CNC conversion mounts. You can download and use the mount posted here kt150-xy-mountv3.stl under Creative Commons Attribution-NonCommercial-ShareAlike license.

Thanks to GitHub Stl Viewer you can preview the object bellow:

Keyboard and mouse sharing across desktops with Synergy – Ubuntu Windows Setup

I got tired of switching from my lovely ThinkPad keyboard to the Dell one connected to my desktop so I decided to take the dive and setup Synegy keyboard and mouse sharing.

I have a nice three monitor setup on the desktop side of things ( that is a cool NVIDIA GeForce GTX 650 Kepler card driving three dell 2007FP monitors ) and my favorite Thinpad keyboard “running” on thinkpad X200T. The three dell monitors are situated above my thinkpad thanks to a practical combination between Ikea capita legs and a brown shelf that matches my huge Galant desk.

Considering this positioning we come to the conclusion that the thinkpad running ubuntu  should be the synergy server and the dell workstation running 64bit windows 7 should be just a synergy client.

The first thing I did was to install synergy 1.4.x on windows, when I got to the point of connecting to the ubuntu synergy server I realized that the Ubuntu 12.04.1 LTS was running the 1.3.x version ( that means a different synergy protocol ), so I had to reinstall the synergy 1.3.x branch from this download location. Just for the record the errors that the synergy client was throwing at me was “failed to connect to server: incompatible client 1.3” .

The windows part it’s really easy but it it important to get the screen name, this is normally your computer name but just to be on the safe side you can check it in the “Advanced…” -> “Screen Name:”. This screen name it is used in the Ubuntu Synergy configuration file.

My computers are called paris (thinkpad) and quad(dell) so the resulting synergy screen names are paris and quad. What you have to do now is use your favourite editor ( nano should do it, vi is to complex 🙂 ) and create the ~/.synergy.conf with the following content:


section: screens
paris:
quad:
end


section: links
paris:
left=quad
up=quad
quad:
right=paris
down=paris
end

I just start the synergy server by running “synergys” from comand line in ubuntu and connect with the windows client to the ip of the synergy server. Now I am able to mode from the thinkpad to the dell via the right and upper side of the screen ( paris ) and come back from the quad via left and lower side of the screen.

Opera wingdings webdings rendering error

It seems that sometimes Opera Browser goes haywire and will start to display what looks like wingdings – webdings fonts. I have traced this rendering issues to a cache issue. Though I don’t know what is causing this I can tell you that if you delete “C:\Users\USERNAME\AppData\Local\Opera\Opera\cache\assoc002” directory Opera will start to render properly again, as it does usually.

Wireshark network mapping – switch and port discovery with CDP (Cisco Discovery Protocol) or LLDP (Link Layer Discovery Protocol)

So you find yourself in a new network. The patch panels are a mess and you have a hard time to find the port and the switch you are connected to.
If this situation sounds familiar to you just head to http://www.wireshark.org/ and download this wonderful network protocol analyzer and lets get started.
After you managed to install Wireshark just fire up a capture session on your connected interface and filter by one of these strings: “cdp.version == 2” or “eth.type == 0x88cc”. As you can imagine the first one works only in Cisco La-La Land. Basically cisco switches send by default at an interval of 60 seconds multicast announcements (CDP packets) on each connected port to the multicast destination address 01-00-0c-cc-cc-cc. Connected devices that understand this protocol will store this information in an internal table that can be accessed via SNMP or Cisco CLI (show cdp neighbors).

The cool thing about this is that after you discover one switch and if the public SNMP community is active and accessible you can basically map not just your direct switch and port but all your surrounding switches. If you are up to it you can build your very own PERL discovery script based on this CPAN module.

Anyway, back to the Wireshark thing. Probably by the and of this article you managed to see those cool Cisco Discovery Protocol packets. In case you did not it means that:

  1. CDP is disabled on the switch  via cli: set cdp disable – but why !!! I wonder ? security ? or worse denial of service ? Get the facts at Cisco CDP vulnerabilty
  2. You are a fast reader and you did not wait more than 1 minute, please wait a little longer
  3. You are poor and don’t have a Cisco switch try the LLDP filter mentioned above
  4. Out of ideas – sorry

 

I will try to post some screenshots after I manage to sell one of my kidneys to buy a Cisco switch. Till then …