halfbakedmaker.org Report : Visit Site

Technical data of the halfbakedmaker.org

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host halfbakedmaker.org. Currently, hosted in United States and its service provider is Squarespace Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

-- about rss feed about rss feed filter all augmented reality game babbage-boole rodulator cat hair sweater cnc router cnc x2 mill conversion diy book scanner half-baked projects learning latin machine learning monroe calculator restoration not a project roomba uncategorized june 5, 2018 robert baruch documenting the toupcam wireless protocol june 5, 2018 robert baruch [ touptek ] makes some nice microscope cameras. for my integrated circuit imaging microscope, i wanted to move away from my current canon dslr, which has survived a few tens of thousands of mechanical shutter release activations, so i'd like a cheaper backup. canon rebel t3i mounted on my olympus trinocular bhmj metallurgical microscope. i used a generic [ ndpl-2 (2x) adapter ]. it was quite loose and didn't even come with an o-ring, so i just hot-glued the thing. even then it was a little wobbly so i put some paper shims in there with the glue. surprisingly, the images come out almost, but not quite, perpendicular to the light path. amscope has [ a wireless camera ] which seems to perform well. a little research showed that amscope basically sells rebranded cameras from [ touptek ]. even amscope's camera software and microscope camera adapters are just rebranded. amscope's hd205-wu camera. it is a rebranded [ t ouptek x cam1080phb ]. you also need the adapter, [ amscope ru050 ], or [ touptek fma050 ]. now, the camera doesn't have a convenient logic level trigger input like the dslr does, so i need some way of triggering the camera. the camera, which i'll start calling toupcam, has a wifi interface, a usb interface, an hdmi interface, and an sd card slot. toupcam mounted on an amscope inspection microscope, showing the hdmi output. yes, that's a mouse cursor in the top part of the "e". the usb interface is, in fact, just a usb port. you can either plug in a mouse or the included wifi usb dongle. with the mouse, you can move the cursor around and pull up the native interface on the hdmi monitor. with the wifi dongle attached, the camera presents itself as an access point. if you connect your computer's wifi to that access point, you can then run touptek's toupview (amscope's amscope) software, and it will find the camera. you can then control the camera from the software. there's just one problem. if your computer is connected to the camera's wifi ap, you can't connect to the internet. maybe if you had two wifi adapters you could do it, but then you'd have to be sure to route internet traffic to your internet-connected adapter. i had no internet access when i took this screenshot. so the camera sends live video, and can also send a "snap" (i.e. higher-resolution image). you can also send it commands changing various controls such as exposure. now, ideally, i'd like to connect to this camera using the beaglebone black that i already use to control the microscope stage and the camera trigger, and save the images to an sd card. however, the wifi protocol is undocumented. luckily, wireshark can show me the wifi packets. 192.168.7.1 is the camera, and 192.168.7.2 is the address the camera gave to my computer. we can see that video is sent from the camera to the computer via the rtp protocol. it appears the camera looks like an ordinary ip camera accessible through an rtsp url. of course, i don't care about video unless i want to display the video via the bbb, which could be convenient for focusing. what i really want to do is (a) get an image and (b) adjust controls. so, i hit the snap button and see what happens... apparently snapping an image involves connecting to port 555 and sending this package that starts with "ge". the response appears to be a ge reply, with a jpg file in there somewhere. the red portion is the request, the blue portion is the response. i've highlighted the beginning of the jpg file. also note that there's a suspicious-looking "gepj" backwards "jpeg" in there. the 0x001e1e29 just prior to the jpg file appears to be the size of the enclosed jpg file, which goes from offset 0x6d to 0x1e1e95. there's also another length before that, 0x001e1e3a, so it appears there's yet another wrapper, and a 0x001e1e4a before even that, so yet another layer of wrappers. we don't really care about the details of these wrappers, just that they exist and can be used to get to the actual jpg file content. now, in terms of the controls, here's what happened when i fiddled around with the exposure setting: from what i can tell, toupcam is using the [ connectionless network protocol ] (clnp) to port 12000. the only thing i recognized in the data field is 0xb4 (180), which is what the exposure value is. the rest of the clnp packets come from the toupcam itself, and appear to indicate the current settings of everything. what these settings are, i don't know. but in the data above, it appears that 03 is like a register number, 04 never changes so could be a payload length, and then 000000b4 is the data. here's the data for the clnp packet coming back from the toupcam reporting the exposure value: 00 00 00 00 02 03 04 00 00 00 b4. that 03 is in the position that changes for the clnp packets from toupcam, along with the last two bytes, so is probably a register number. for example, for register 01, the value is e290 (58000), a suspiciously round number. color temperature in 1/10 k? register 0a contains 2bc (700), another round number. there's a gamma setting of 7.00 that might be this register. so the next step is to write a simple program which attempts to connect to the camera, pull a still image, and modify some values. rss june 5, 2018 robert baruch comment february 8, 2018 robert baruch building lmarv-1: a tangible risc-v processor, part 1 february 8, 2018 robert baruch a new project, hooray! background risc-v is not a processor in the sense of an arm processor or x86. it is, in fact, an open specification for an instruction set architecture (isa). this means that the instruction set is standardized by the [ risc-v foundation ], and then anyone can implement [ that instruction set ] free of any licenses, royalties, or legal requirements. risc-v is the result of much study of existing isas. the result is regular , which makes an instruction decoder easy to create. it's also modular . there is only one subset of the isa that is required to be implemented, the 32-bit integer set. this is called the 32i extension, meaning that all instructions and registers are 32 bits. everything else is optional. for example, the m extension include multiplication and division instructions. a is for atomic operations. f and d are for single- and double-precision floating point. the g extension means "general", and means that you implement all of imaf and d. in general, if your implementation doesn't implement a particular g extension, you will have to provide libraries that do the same thing in software. otherwise a compiler wouldn't be able to compile certain standard expressions. there's also a 64-bit extension, 64i, and a 128-bit extension, 128i. there is a 32e extension, which is for smaller (e.g. embedded) processors which halves the number of required integer registers. quad-precision floating points are in the q extension. there's even an extension, c, for compressed instructions, which allows 16-bit and variable-length instructions. some other interesting extensions, which have not yet been frozen (i.e. fully developed and agreed upon), are v (vector instructions), l (decimal floating point, as in calculators), and b (bit manipulation). speaking of extensions, risc-v is extensible . if you have some piece of specialized hardware that you want custom instructions for, there is a whole range of opcodes reserved for that. of course, your compiler would have to support those custom opcodes, or you could just wrap the assembly language. and speaking of instructions, it should be pretty clear that the isa is a reduced-instruction set . there are fewer than 50 instructions in the g extension! all the instruc

URL analysis for halfbakedmaker.org

http://www.halfbakedmaker.org/?category=cnc+router
http://www.halfbakedmaker.org/#header
http://www.halfbakedmaker.org/?category=monroe+calculator+restoration
http://www.halfbakedmaker.org/?category=cat+hair+sweater
http://www.halfbakedmaker.org/?category=cnc+x2+mill+conversion
http://www.halfbakedmaker.org/blog/retroassembling#comments-5a5eca5853450ae875f69fba
http://www.halfbakedmaker.org/?category=augmented+reality+game
http://www.halfbakedmaker.org/?category=roomba
http://www.halfbakedmaker.org/blog?format=rss
http://www.halfbakedmaker.org/blog/lmarv1-1#comments-5a7cf51353450a1218b031a4
http://www.halfbakedmaker.org/about/
http://www.halfbakedmaker.org/?category=babbage-boole+rodulator
http://www.halfbakedmaker.org/?category=uncategorized
http://www.halfbakedmaker.org/?category=not+a+project
http://www.halfbakedmaker.org/?category=half-baked+projects

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

WHOIS LIMIT EXCEEDED - SEE WWW.PIR.ORG/WHOIS FOR DETAILS

  REFERRER http://www.pir.org/

  REGISTRAR Public Interest Registry

SERVERS

  SERVER org.whois-servers.net

  ARGS halfbakedmaker.org

  PORT 43

  TYPE domain

  REGISTERED unknown

DOMAIN

  NAME halfbakedmaker.org

NSERVER

  DNS1.REGISTRAR-SERVERS.COM 216.87.155.33

  DNS2.REGISTRAR-SERVERS.COM 216.87.152.33

  DNS3.REGISTRAR-SERVERS.COM 216.87.155.33

  DNS4.REGISTRAR-SERVERS.COM 216.87.152.33

  DNS5.REGISTRAR-SERVERS.COM 216.87.155.33

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .