Many of us doesn't know the full features or our car as its either not provided in stock vehicle or kept as hidden. Some can be activated/added without extra cost and some with additional cost.
Here are some features of i20 which you can add in your car with or without additional cost.
1.Auto Door lock at 40kmph - You can activate this feature from the Authorized Service Center.
The central locking enables when you cross the speed of 40 kmph. Also in a scenario if you forgot to lock the car manually with the remote key after parking it - the doors gets locked with in 30 sec.
2.Auto Door Unlock - You can activate this feature from the Authorized Service Center.
The central locking disables when you take out the key from the keyhole making the exit easy as no need to manually unlock the doors.
Here are the button combination for displaying this text ( Press one by one but immediately)
Press and Hold 1FF, then 6
if the version shows in MID is VER M58 S71 D29 or higher then you HU is a good one
if the version shows in MID is VER M08 S69 D18 ( important to look for S69) then your HU have some issues like
1. HU automatically switches OFF while running
2. HU fuse pops up when you press Eject button while ignition is at OFF position.
You can get a free replacement of HU from Hyundai if you found your version as S69
Enabling RDS (Radio Data System)
i. Press and hold 1FF and then immediately press 4, release both the fingers ,then press 1FF Four times as fast as you can.
ii. Now you can see the display in MID as VER M58 S71 D29 (or higher), immediately press button 6 so you can see your present region as General in MID.
iii. Rotate the File/Enter/Tune knobe to change the region to Europe and Press/Push the Knob, now you can see the display as area changed.
iv. Switch ON the HU by Press/push the Power Button and press the SETUP button, Rotate the File/Enter/Tune knobe and enable the features you want and press/push the knob to store the settings.
i. Press and hold 1FF and then immediately press 4, release both the fingers ,then press 1FF Four times as fast as you can.
ii. Now you can see the display in MID as VER M58 S71 D29 (or higher), immediately press button 6 so you can see your present region as General in MID.
iii. Rotate the File/Enter/Tune knobe to change the region to Europe and Press/Push the Knob, now you can see the display as area changed.
iv. Switch ON the HU by Press/push the Power Button and press the SETUP button, Rotate the File/Enter/Tune knobe and enable the features you want and press/push the knob to store the settings.
Rheostat Ilumination Control - Add-on
Rheostat Ilumination Control is to control the illumination brightness of the Dash board lightings. Very useful in night driving. To get this you need to order theRheostat Ilumination Control - Part Number: 94950-1J0009P.
Its plug and play ( i.e connection wires , socket everything is present in the car, you just need to buy this item and attach it to the socket)
Cost: Rs.579.00
F.A.T.C (Fully Automatic Temperature Control) Self Diagnostic
If you have FATC (fully automatic Temperature Control) equipped in your i20 , you can run a self-diagnostic to make sure the components related to it working properly.
To get into the self diagnosis mode
1. Put the key into the ignition hole
2. Turn the key into ON position so the dashboard lights illuminates (No starting of engine)
3. Press and hold the OFF button, then press the MODE button more than 4 times within 2seconds
4. The you can see the Display unit of a/c illuminates like in the video and display codes starts blinking.
5. Now the diagnosis starts
6. press the A/C button to proceed to next step
7. after completion it will come into the original condition
8. Incase if you wants to quit anytime press OFF button
Here are the other codes which will display if any of the component related to F.A.T.C malfunctions.
00 = Normal
11 = In-car temparature sensor open
12 = In-car temparature sensor short
13 = Ambient temparature sensor open
14 = Ambient temparature sensor short
17 = Evaporator temparature sensor open
18 = Evaporator temparature sensor short
19 = Temparature control actuator feed back open
20 = Temparature control actuatore failure
21 = Mode Control actuator open
21 = Mode control actuator short
22 = Mode control actuator failure
25 = Intake potentiometer open
25 = Intake potentiometer short
26 = Intake potentiometer failure
Airconditioner Temperature Unit Conversion
Turn the key ON (Till the dash board lights illuminates)
Press and Hold OFF Button then Auto Button , the display changes from °C to °F. Repeat the same to Change back to °C.
8.Glove Box Illumination
This was badly missing in i20 and there was no light provided in the Glove Box. To add this you need to purchase Lamp Assy- Glove Box, Part No. 92630-1J000. Its Plug and Play so NO alternation/additions required.
note: Park light should be ON to make the Glove box lamp to work
Cost: Rs.118.00
Friday, December 16, 2011
Progressive enhancement
Progressive enhancement is a strategy for web design that emphasizes accessibility, semantic HTML markup, and external stylesheet and scripting technologies. Progressive enhancement uses web technologies in a layered fashion that allows everyone to access the basic content and functionality of a web page, using any browser or Internet connection, while also providing those with better bandwidth or more advanced browser software an enhanced version of the page
Now that it’s 2011 I hope more .NET web developers really start to take progressive enhancement seriously. Sure many ASP.NET devs work on internal LOB apps and can enforce javascript requirements, but if you’re working on an internet-facing site I encourage you to take advantage of the many PE/unobtrusive javascript techniques we have available these days, especially in MVC 3.
building a contact us form
JavaScript enabled
As you can see when a user visits our site with JavaScript enabled and clicks on the Contact Us link, they are presented with a nice jQuery UI dialog window. They can fill in the form and get a nice confirmation message inside the dialog, and finally close it without ever leaving the page they were on.
JavaScript disabled
A visitor without JavaScript will still get the same functionality, just a slightly lesser experience. Without JavaScript logic attached to our Contact Us link it behaves like a plain old hyperlink, navigating the browser to a new page. Once they fill out the form and press Send Message we redirect them back to the Home page with a confirmation message.
the general idea behind this code
On the server-side (your controller) use Request.IsAjaxRequest() to determine whether the incoming request was invoked via JavaScript or not
Use Partial Views to re-use the same markup in both the Ajax view and the standard view
Use jQuery to make Ajax calls to our Controller, which will return a Partial View of only the HTML we need to display. We then inject this HTML into the DOM where we need it.
Now that it’s 2011 I hope more .NET web developers really start to take progressive enhancement seriously. Sure many ASP.NET devs work on internal LOB apps and can enforce javascript requirements, but if you’re working on an internet-facing site I encourage you to take advantage of the many PE/unobtrusive javascript techniques we have available these days, especially in MVC 3.
building a contact us form
JavaScript enabled
As you can see when a user visits our site with JavaScript enabled and clicks on the Contact Us link, they are presented with a nice jQuery UI dialog window. They can fill in the form and get a nice confirmation message inside the dialog, and finally close it without ever leaving the page they were on.
JavaScript disabled
A visitor without JavaScript will still get the same functionality, just a slightly lesser experience. Without JavaScript logic attached to our Contact Us link it behaves like a plain old hyperlink, navigating the browser to a new page. Once they fill out the form and press Send Message we redirect them back to the Home page with a confirmation message.
the general idea behind this code
On the server-side (your controller) use Request.IsAjaxRequest() to determine whether the incoming request was invoked via JavaScript or not
Use Partial Views to re-use the same markup in both the Ajax view and the standard view
Use jQuery to make Ajax calls to our Controller, which will return a Partial View of only the HTML we need to display. We then inject this HTML into the DOM where we need it.
tips for family life
We trust each other.
We ensure - even when we can't be together - that we "touch bases" daily.
We make each other laugh.
We are each other's best friends.
we communicate when we feel bad
we trust each other to do the right thing
we pick up the slack when the other cant
we compromise
we are honest with each other
we dont take offese when one of us has a problem with a behavior, we talk it out.
we interject humor into just about everything, even fights.
We ensure - even when we can't be together - that we "touch bases" daily.
We make each other laugh.
We are each other's best friends.
we communicate when we feel bad
we trust each other to do the right thing
we pick up the slack when the other cant
we compromise
we are honest with each other
we dont take offese when one of us has a problem with a behavior, we talk it out.
we interject humor into just about everything, even fights.
Tip for the future of Software Engineers
With the recent changes in the economy, a lot of developers are focused on their short-term job prospects. At the same time, it’s important to make sure that you get the most bang for your buck when it comes to taking the time and energy to learn new skills. Here is our list of 10 skills you should be learning right now to make sure that your resume is relevant for the next five years. The list is hardly exhaustive, and there are huge swaths of the industry it won’t cover (mainframe developers, for example). Nonetheless, for average mainstream development, you can’t go wrong learning at least seven of these skills — not only to the point where you can talk convincingly about them at a job interview, but actually use them on the job.
1: One of the “Big Three” (.NET, Java, PHP)
Unless there is a radical shift in the development world (akin to an asteroid hitting Redmond), most developers will need to know at least one of the Big Three development systems — .NET (VB.NET or C#), Java, or PHP — for the near future. It’s not enough to know the core languages, either. As projects encompass more and more disparate functionality, you’ll need to know the associated frameworks and libraries more deeply.
2: Rich Internet Applications (RIAs)
Love it or hate it, in the last few years, Flash is suddenly being used for more than just animations of politicians singing goofy songs. Flash has also sprouted additional functionality in the form or Flex and AIR. Flash’s competitors, such as JavaFx and Silverlight, are also upping the ante on features and performance. To make things even more complicated, HTML 5 is incorporating all sorts of RIA functionality, including database connectivity, and putting the formal W3C stamp on AJAX. In the near future, being an RIA pro will be a key resume differentiator.
3: Web development
Web development is not going away anytime soon. Many developers have been content to lay back and ignore the Web or to just stick to “the basics” their framework provides them with. But companies have been demanding more and more who really know how to work with the underlying technology at a “hand code” level. So bone up on JavaScript, CSS, and HTML to succeed over the next five years.
4: Web services
REST or SOAP? JSON or XML? While the choices and the answers depend on the project, it’s getting increasingly difficult to be a developer (even one not writing Web applications) without consuming or creating a Web service. Even areas that used to be ODBC, COM, or RPC domains are now being transitioned to Web services of some variety. Developers who can’t work with Web services will find themselves relegated to legacy and maintenance roles.
5: Soft skills
One trend that has been going for quite some time is the increasing visibility of IT within and outside the enterprise. Developers are being brought into more and more non-development meetings and processes to provide feedback. For example, the CFO can’t change the accounting rules without working with IT to update the systems. And an operations manager can’t change a call center process without IT updating the CRM workflow. Likewise, customers often need to work directly with the development teams to make sure that their needs are met. Will every developer need to go to Toastmasters or study How to Win Friends and Influence People? No. But the developers who do will be much more valuable to their employers — and highly sought after in the job market.
6: One dynamic and/or functional programming language
Languages like Ruby, Python, F#, and Groovy still aren’t quite mainstream – but the ideas in them are. For example, the LINQ system in Microsoft’s .NET is a direct descendent of functional programming techniques. Both Ruby and Python are becoming hot in some sectors, thanks to the Rails framework and Silverlight, respectively. Learning one of these languages won’t just improve your resume, though; it will expand your horizons. Every top-flight developer I’ve met recommends learning at least one dynamic or functional programming language to learn new ways of thinking, and from personal experience, I can tell you that it works.
7: Agile methodologies
When Agile first hit mainstream awareness, I was a skeptic, along with many other folks I know. It seemed to be some sort of knee-jerk reaction to tradition, throwing away the controls and standards in favor of anarchy. But as time went on, the ideas behind Agile became both better defined and better expressed. Many shops are either adopting Agile or running proof-of-concept experiments with Agile. While Agile is not the ultimate panacea for project failure, it does indeed have a place on many projects. Developers with a proven track record of understanding and succeeding in Agile environments will be in increasingly high demand over the next few years.
8: Domain knowledge
Hand-in-hand with Agile methodologies, development teams are increasingly being viewed as partners in the definition of projects. This means that developers who understand the problem domain are able to contribute to the project in a highly visible, valuable way. With Agile, a developer who can say, “From here, we can also add this functionality fairly easily, and it will get us a lot of value,” or “Gee, that requirement really doesn’t match the usage patterns our logs show” will excel. As much as many developers resist the idea of having to know anything about the problem domain at all, it is undeniable that increasing numbers of organizations prefer (if not require) developers to at least understand the basics.
9: Development “hygiene”
A few years ago, many (if not most) shops did not have access to bug tracking systems, version control, and other such tools; it was just the developers and their IDE of choice. But thanks to the development of new, integrated stacks, like the Microsoft Visual Studio Team System, and the explosion in availability of high quality, open source environments, organizations without these tools are becoming much less common. Developers must know more than just how to check code in and out of source control or how to use the VM system to build test environments. They need to have a rigorous habit of hygiene in place to make sure that they are properly coordinating with their teams. “Code cowboys” who store everything on a personal USB drive, don’t document which changes correspond to which task item, and so on, are unwelcome in more traditional shops and even more unwelcome in Agile environments, which rely on a tight coordination between team members to operate.
10: Mobile development
The late 1990s saw Web development rise to mainstream acceptance and then begin to marginalize traditional desktop applications in many areas. In 2008, mobile development left the launch pad, and over the next five years, it will become increasingly important. There are, of course, different approaches to mobile development: Web applications designed to work on mobile devices, RIAs aimed at that market, and applications that run directly on the devices. Regardless of which of these paths you choose, adding mobile development to your skill set will ensure that you are in demand for the future.
1: One of the “Big Three” (.NET, Java, PHP)
Unless there is a radical shift in the development world (akin to an asteroid hitting Redmond), most developers will need to know at least one of the Big Three development systems — .NET (VB.NET or C#), Java, or PHP — for the near future. It’s not enough to know the core languages, either. As projects encompass more and more disparate functionality, you’ll need to know the associated frameworks and libraries more deeply.
2: Rich Internet Applications (RIAs)
Love it or hate it, in the last few years, Flash is suddenly being used for more than just animations of politicians singing goofy songs. Flash has also sprouted additional functionality in the form or Flex and AIR. Flash’s competitors, such as JavaFx and Silverlight, are also upping the ante on features and performance. To make things even more complicated, HTML 5 is incorporating all sorts of RIA functionality, including database connectivity, and putting the formal W3C stamp on AJAX. In the near future, being an RIA pro will be a key resume differentiator.
3: Web development
Web development is not going away anytime soon. Many developers have been content to lay back and ignore the Web or to just stick to “the basics” their framework provides them with. But companies have been demanding more and more who really know how to work with the underlying technology at a “hand code” level. So bone up on JavaScript, CSS, and HTML to succeed over the next five years.
4: Web services
REST or SOAP? JSON or XML? While the choices and the answers depend on the project, it’s getting increasingly difficult to be a developer (even one not writing Web applications) without consuming or creating a Web service. Even areas that used to be ODBC, COM, or RPC domains are now being transitioned to Web services of some variety. Developers who can’t work with Web services will find themselves relegated to legacy and maintenance roles.
5: Soft skills
One trend that has been going for quite some time is the increasing visibility of IT within and outside the enterprise. Developers are being brought into more and more non-development meetings and processes to provide feedback. For example, the CFO can’t change the accounting rules without working with IT to update the systems. And an operations manager can’t change a call center process without IT updating the CRM workflow. Likewise, customers often need to work directly with the development teams to make sure that their needs are met. Will every developer need to go to Toastmasters or study How to Win Friends and Influence People? No. But the developers who do will be much more valuable to their employers — and highly sought after in the job market.
6: One dynamic and/or functional programming language
Languages like Ruby, Python, F#, and Groovy still aren’t quite mainstream – but the ideas in them are. For example, the LINQ system in Microsoft’s .NET is a direct descendent of functional programming techniques. Both Ruby and Python are becoming hot in some sectors, thanks to the Rails framework and Silverlight, respectively. Learning one of these languages won’t just improve your resume, though; it will expand your horizons. Every top-flight developer I’ve met recommends learning at least one dynamic or functional programming language to learn new ways of thinking, and from personal experience, I can tell you that it works.
7: Agile methodologies
When Agile first hit mainstream awareness, I was a skeptic, along with many other folks I know. It seemed to be some sort of knee-jerk reaction to tradition, throwing away the controls and standards in favor of anarchy. But as time went on, the ideas behind Agile became both better defined and better expressed. Many shops are either adopting Agile or running proof-of-concept experiments with Agile. While Agile is not the ultimate panacea for project failure, it does indeed have a place on many projects. Developers with a proven track record of understanding and succeeding in Agile environments will be in increasingly high demand over the next few years.
8: Domain knowledge
Hand-in-hand with Agile methodologies, development teams are increasingly being viewed as partners in the definition of projects. This means that developers who understand the problem domain are able to contribute to the project in a highly visible, valuable way. With Agile, a developer who can say, “From here, we can also add this functionality fairly easily, and it will get us a lot of value,” or “Gee, that requirement really doesn’t match the usage patterns our logs show” will excel. As much as many developers resist the idea of having to know anything about the problem domain at all, it is undeniable that increasing numbers of organizations prefer (if not require) developers to at least understand the basics.
9: Development “hygiene”
A few years ago, many (if not most) shops did not have access to bug tracking systems, version control, and other such tools; it was just the developers and their IDE of choice. But thanks to the development of new, integrated stacks, like the Microsoft Visual Studio Team System, and the explosion in availability of high quality, open source environments, organizations without these tools are becoming much less common. Developers must know more than just how to check code in and out of source control or how to use the VM system to build test environments. They need to have a rigorous habit of hygiene in place to make sure that they are properly coordinating with their teams. “Code cowboys” who store everything on a personal USB drive, don’t document which changes correspond to which task item, and so on, are unwelcome in more traditional shops and even more unwelcome in Agile environments, which rely on a tight coordination between team members to operate.
10: Mobile development
The late 1990s saw Web development rise to mainstream acceptance and then begin to marginalize traditional desktop applications in many areas. In 2008, mobile development left the launch pad, and over the next five years, it will become increasingly important. There are, of course, different approaches to mobile development: Web applications designed to work on mobile devices, RIAs aimed at that market, and applications that run directly on the devices. Regardless of which of these paths you choose, adding mobile development to your skill set will ensure that you are in demand for the future.
Subscribe to:
Posts (Atom)