My Chamberlain Ingernet Gateway power dilemma

Really this is just a post to hopefully help some poor soul who likes to google things rather than call tech support Like I had to end up doing. By the way chamberlain doesn't sell the part seperately, the device didn't have any indication of what voltage or amperage it runs at. Luckily the tech support was able to look at one in person and read the DC information for me. I also opened it up looking for different numbers and various things to see anything that would lead me to the proper volts an amps. No avail anyway here are a bunch of numbers from the PCB, and outside casing.


 

chamberlain internet gateway powercord

CIGBU/C

patent: 7,071,850 7,561,075
FCC ID: HBW7549
IC: 2666A-7549

132B2768-3

014D1205 RevE


Barcode
00000014650

132A2589-1

 Oh yeah maybe why you're here.

DC 3.7V 0.3A
Adaptaplug size 'B'

The Tale of Keyboard Mouse adapters for Consoles

First of all this isn't going to be a history lesson, because if it was, I would have to talk about XFrag 360 from Team Xecuter which didn't allow you to rebind most of the controls (might have in the second revision). Or the Smartjoy for the PS2/OriginalXbox. Nah I'm trying to be a little more modern here. So I decided to make a quick little doc about some of the devices and upcoming device the Xim4. I'm really looking forward to the Xim4 and it's support for the headset while using the Xbone controller. Yes there are workarounds using a second controller logged into a Live guest account, or just using Kinect. But I like my all in one solutions. And the xim settings from a phone is just genius, no need to make their build $50 more expensive to add a screen and a clugey interface. Don't get me wrong I love my XIM3, just I'm looking forward to the future. If you didn't catch the link above here is the comparison chart of the {XIM3(discontinued) XIM Edge(discontinued) XIM4(not released yet) CronusMAX iOGear Keymander PS3 Eagle Eye Penguin United Eagle Eye FragFx PS3 & 360 Variant (two models)}

EDIT: updated the google doc link, and the XIM4 was great, now onto testing XIM Apex

Well Google Reader appears to be going away :-(

Reading the news on Google Reader, something I tend to do multiple times a day whether I am on my phone, at work, or on my personal computer. Well straight from Google's official blog http://googleblog.blogspot.com/2013/03/a-second-spring-of-cleaning.html it's going away July 1st 2013. Any alternatives that appear to be worth looking at, well their pages are down at the time of writing this. For example Tiny Tiny RSS http://tt-rss.org/ So I went ahead and signed a petition, because I figured why not https://www.change.org/petitions/google-keep-google-reader-running . Reddit of course has picked up the story as they always too, and it appears many are just as concerned regarding it's departure http://i.imgur.com/kzzvGSk.jpg Well Google maybe I'll go out and find something better, but just something about what you had just worked and I appreciated that.

Doing Well

I'm doing well and quite proud of my Battlefield 3 post, actually checking the stats on that today. A bit of spike of interest a couple days ago, now considering there is software that does all the hard work to shame, it is surprising to still see it linked to in forums. Anyway just posting to post really. Other not pre-ordered tickets for the Avengers, hopefully it will not be a disappointment

Battlefield 3 Key Binding issue fix, specifically the jet.

UPDATE: http://bf3.realmware.co.uk/settings-editor/downloads since update 2.3 released on January 5th it pretty much does everything now.

First of all I have to thank 2 specific blog entries as they were very helpful
http://expfist.blogspot.com/2011/10/battlefield-3-key-bindings-issue-fix.html
http://www.tumblr.com/tagged/q+spotting
In fact the second was nice benefit as I use ‘E’ to spot and ‘Q’ is how I enter/exit vehicles. The key binding issue in Battlefield 3 comes down to they didn’t necessarily hard code the controls, they just didn’t have the rebind function, do all the commands it should. You can clearly see this in the ‘q’ spotting article. Now the reason I had to write this key binding article the jets. So when I bind a key to decelerate other than ‘s’ you will see that ‘s’ will still decelerate, even if it’s bound to something else. I use a variation of an old quake config that I can’t play first person shooters any other way. [Space=forward, a=backwards, s=strafe left, d=strafe right]. So for me ‘s’ is going to be yaw left which it did, however it would also decelerate. And if I set ‘A’ to throttle down, it did nothing, unless you were in SU-39 Frogfoot which if you were in third person you can see the air brakes deployed. Yet in first person you can clearly see they are not slowing you down with your speed on the

GstKeyBinding.jet.ConceptBrake.0.axis 0
GstKeyBinding.jet.ConceptBrake.0.button 30
GstKeyBinding.jet.ConceptBrake.0.negate 0
GstKeyBinding.jet.ConceptBrake.0.type 0
^this is the only thing the keybinding from the gui does.
This is your throttle up
GstKeyBinding.jet.ConceptMoveFB.1.axis 0
GstKeyBinding.jet.ConceptMoveFB.1.button 57
GstKeyBinding.jet.ConceptMoveFB.1.negate 0
GstKeyBinding.jet.ConceptMoveFB.1.type 0
When binding the throttle down BF3 needs to be patched so it actually binds the following, which You can add into the config.
GstKeyBinding.jet.ConceptMoveFB.2.axis 0
GstKeyBinding.jet.ConceptMoveFB.2.button 30
GstKeyBinding.jet.ConceptMoveFB.2.negate 1
GstKeyBinding.jet.ConceptMoveFB.2.type 0
^this is the throttle down that will actually help.
Cool so I did all this and I should be good to go, ‘A’ will not decelerate, but ‘S’ is still slowing me down as well. That brings me to my next discovery that “GstKeyBinding.gunner” keys actually affect the jet.
So I needed to do the following
GstKeyBinding.gunner.ConceptMoveFB.2.axis 0
GstKeyBinding.gunner.ConceptMoveFB.2.button 30
GstKeyBinding.gunner.ConceptMoveFB.2.negate 1
GstKeyBinding.gunner.ConceptMoveFB.2.type 0
I didn’t have to bother rebinding the rest of the gunner as far as I know, I have not had it break anything.

That’s My story, now like the blog entry above that talks about config fixes I am going to explanation to how BF3 config actually works.

GstKeyBinding.gunner.ConceptMoveFB.2.axis 0
GstKeyBinding.gunner.ConceptMoveFB.2.button 30
GstKeyBinding.gunner.ConceptMoveFB.2.negate 1
GstKeyBinding.gunner.ConceptMoveFB.2.type 0

So let us break this down.
GstKeyBindng = letting the game know this is a key binding
Gunner/vehicle/jet/infantry/etc. = This lets the game know what instance to use this binding in
ConceptMoveFB = This lets the game know what kind of binding it is (side note: FB, most likely stands for forward Back)
2 = it’s the 3rd (because the count starts at 0) key that is bound to do this action
Axis/button/negate/type: a little more explanation needs to go here.
Axis = This is where I am not at a full understanding, this is more for editing mouse movements, joysticks, and controllers. Since this article is focused on keyboard/mouse, axis 0 should suffice.
Button = they key, or joystick button that the action is bound to i.e. 30 on the keyboard is ‘a’
Negate = for FB 0 is forward because it’s not negated, and if its negated with ‘1’ its backwards. And for LR(left right) or YAW, 0 is right, and left is 1.

The keyboard buttons, it starts at tilde which is ‘1’ which 2 is ‘1’ also based on full keyboard.
And it counts from there, however it doesn’t appear to count all the keys in order either.
So I do some work to figure out the keys

Actual Key Button #
`[tilde] 1
1 2
2 3
3 4
4 5
5 6
6 7
7 8
8 9
9 10
0 11
- 12
= 13
[backspace] 14
[tab] 15
q 16
w 17
e 18
r 19
t 20
y 21
u 22
i 23
o 24
p 25
[ 26
] 27
[enter] 28
[left control] 29
a 30
s 31
d 32
f 33
g 34
h 35
j 36
k 37
l 38
; 39
[left Shift] 42
\ 43
z 44
x 45
c 46
v 47
b 48
n 49
m 50
, 51
. 52
/ 53
[right shift] 54
NUM* 55
[left alt] 56
[space] 57
[caps lock] 58
F1 59
F2 60
F3 61
F4 62
F5 63
F6 64
F7 65
F8 66
F9 67
F10 68
NULOCK 69
NUM7 71
NUM8 72
NUM9 73
NUM- 74
NUM4 75
NUM5 76
NUM6 77
NUM+ 78
NUM1 79
NUM2 80
NUM3 81
NUM0 82
NUMDEL 83
F11 87
F12 88
NUMENTER 156
[right control] 157
NUM/ 181
[right alt] 184
HOME 199
[up arrow] 200
PAGEUP 201
[left arrow] 203
[right arrow] 205
END 207
[down arrow] 208
PAGEDOWN 209
INS 210
DEL 211
[left windows] 219
[right windows] 220
[application key] 221
[unbound] 255

New Post Same Subject

The Title says it all, and look my last post was in August, its now November there has been a little bit of an update in the whole Live account situation. They unlocked my account in the middle of September which means I can play games now. That is all I can do with my live account, I can't buy DLC or MSPoints from the dashboard, 1. Because its in Russian, which I don't read very well 2. DLC purchased there doesn't work on United States consoles (so I 'm told).

Since they had an "engineer" confirm to me that I would be fine registering my new GFWL games to my gamertag, I thought the same should apply to NTSC Registration codes. So now when I buy my DLC for my account I go through GameStop, and I thought GameStop selling DLC was idiotic.

current account status: my possession but Russian.

Zune: can't log into the software or device

Windows Phone 7: Not supported in Russia either. (feels the need to tell me I have 7 updates, but when I click on the marketplace says this region is not supported.)

Anyway.

Life in general has been alright, but speeding up in a way I am not sure I appreciate. I goto work, play games, party, and pretty much repeat. I throw some family time in their. There are things I am starting to want again which should be healthy.