There is a manual throttle body available for 1G-FE vvti motors. They can be found on GXE10 Altezzas and late (vvti 1G) GX100s, only on the non-TRC variants. They have stepper motor idle control, so will not be compatible with an IS200 ECU.
E-throttle on the left, Mechanical on the right (click for full size):
This is an option for running aftermarket ecus which don’t support drive-by-wire. They can be found easily and cheaply on yahoo japan, but you will need a forwarding service or local agent to send it to you.
There’s been talk about this option on forums and youtube comments for years without solid information, so I hope this clears things up a bit.
In the past I have successfully used the factory amp and speakers with an aftermarket head unit by soldering RCA positives onto the 4 signal lines. The signal ground is common, so I joined the RCA negatives together.
The amplifier turns on with positive signal voltage like an aftermarket amplifier.
Amplifier pin out
The factory amplifier worked quite well at first. Over time it developed a constant quiet hiss from the speakers, and a speaker pop when turning off the amp. The amplifier did this without a head unit connected.
The harness connecting the amplifier to the car body is standard Toyota. In Toyota vehicles the amplifier is viewed as the head of the system.
The 4 rear speakers in the 8 speaker system are driven separately, with 4 ohm midrange speakers and 2 ohm woofers. Because the mids have a narrow frequency range, and the woofers are low impedance, it is common to replace them with aftermarket 6×9’s.
If you care about impedance:
Head unit line outs are 10k between channel+ and sgnd
Amplifier line input is over 2m
Amplifier speaker output is over 2m on the mids, 3.6k on the woofers
These neat little modems are already unlocked, but don’t automatically connect to non-Vodafone networks. They also need the other network’s APN configuration to access the internet. In order to connect, we need to manually set these up.
When plugged in, the modem menu is at 192.168.9.1. Make sure you aren’t connected to another network.
This is a common problem on Lenovos, remedied temporarily by pushing in the charger plug.
Circled below is the problem area. The center pin of the plug is connected to the ring, the hard wire is connected to the board. The problem occurs when the connection between the two breaks. We will repair this with a solder joint. To do this repair you will need to remove the board from the machine, if you’re unsure how to do this refer to youtube disassembly videos.
Once the board is removed from the case you will have access to the top side as shown above. This is where we have enough access to solder a connection.
Flow solder between the two parts, as shown above.
If you updated to high sierra and are reinstalling your ports, you may run into:
---> Building osxfuse
Error: Failed to build osxfuse: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/main.log for details.
Look in that main.log
:debug:build Failed to locate 'lbzip2' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it?
There’s an unlisted requirement of lbzip2. Install it.
$ sudo port install lbzip2
After installing lbzip2, try to install the package again, then check the main.log
:info:build /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': dlopen(/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle, 9): Library not loaded: @rpath/libclang.dylib (LoadError)
Chances are it failed with the above error. Basically, the build script couldn’t find the libclang library. There is some in-depth discussion on the cause and workarounds at: https://trac.macports.org/ticket/54939 To fix this, we’re going to add an aditional symlink to the library, as Xcode has a broken address for the library by default.