Skip to main content

CarPC - updates

It has been a while since I've wrote about my CarPC setup, up to now, it still not functioning 100% as what I wanted. Anyway, updates on what I've done so far:

1. Failed HD, for some reason, my HD failed on me, its pretty new HD, manufactured in March 2010. So, I've replaced the WD 250GB HD with Hitachi 320GB HD. The Hitachi should be faster since it is running on 7200rpm compared to WD's 3600rpm. I've sent the WD to Singapore and hopefully I'll get a replacement.

2. Added Logitech Webcam Pro 9000 to the setup. I don't have the photo right now, but it is epoxyed to the rearview mirror. Quality wise, not as good as expected, probably because I'm using xvid/mp4 format to save some space. Example of video captured during one of my drive around:



3. Not really a CarPC related but I've modified the EBY701 TFT monitor to do auto-switching for my rearview camera. The mod works as expected but the camera is a bit grainy .. probably because it uses CMOS technology but what do you expect from the camera bought from China in EBay :)

4. My DAB+ module just arrived, along with the DAB/FM antenna. I haven't fix this inside the car but during my test on my desktop PC, I found 15 channels are available but only five that have active broadcast. The FM part seems to be useless when tested on bench but I don't know will it be different when installed in the car. I need to fix the GTI like antenna on the roof first, bought the wrong one, a passive DAB but active FM antenna .. grr.. what to do.. will update with photos when installed.

5. My CarPC setup interferes with my ham rig especially on APRS frequency. I need to move my ham rig to the back of my pickup truck (behind rear passenger's bench/seat). This will hopefully helps reduce the interference and I could have APRS POI back on my Nuvi 350. I still couldn't get PC based APRS to work with the Malaysian map. Will try to make this thing working..

That's all for now.

Comments

Popular posts from this blog

Raspberry Pi + svxlink = Low power echolink node

What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:

For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD cardA USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.  Here is the configuration on how to get the things working together, courtesy of svxlink.de website:

For software:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zipUnzip the file and copy it to your SD card using the following instructions that can be found here.Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connec…

Configuring TechniColor TG784N V3 (Maxis issued broadband router) to use different DNS servers

Previous write up deleted. It seems to change the DNS servers in as shown on the status, but it does not really work.

Check the following website, this seems to work:

http://www.o2help.co.uk/router-change-dns/

This can be done from the WEB GUI too, go into the following configuration path:


In my example above, I'm using paid service unblock-us instead of google public DNS servers.

Debugging DMEE

I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the few suggestion was to create a user exit just before the node that we would like to debug and put our breakpoint there. It seems that SAP has built-in this feature without needing us to create a user exit (available in ECC 6, have no idea if this is available on prior releases). Here is how you can put your breakpoint without any coding.

1. Display your DMEE tree using transaction: DMEE_DEBUG.


2. Click on the node that you would like to debug.
3. Go to conditions tab, you could see the Set Breakpoint button. Click to set.



4. Run the SAPFPAYM and specified the payment run date/id, payment format etc. SAP will stop at the node which you point your breakpoint at, as in 2.
5. To remove your breakpoint, just run the DMEE_DEBUG again, there is an option to delete all own breakpoints or all.