Before “mechatronics” was called that, in the industry they just called it “automation”. The field is dominated in North America initially by Ladder logic, which everyone on this website (except me) would absolutely hate if they saw it. It has its purposes however.

In the last 10 years you see a lot more standardization of automation languages, specifically the IEC-61131-3 standard, which includes the following languages:

• LD (Ladder Diagram) – a.k.a. ladder logic
• FBD (Function Block Diagram) – similar to your labview
• SFC (Sequential Function Chart) – a fancy state machine or state diagram
• ST (Structured Text) – a “normal” computer language with a syntax similar to BASIC/Pascal
• IL (Instruction List) – kind of like assembly, but not really

In real life (I do this for a living) I see a lot of LD, and then secondarily a bunch of FBD and ST. I myself have used SFC in several projects over the last 5 years, and I like some of its features, but it has some problems (notably gentle recovery from faults is usually harder in SFC than in LD).

Note that IEC-61131-3 is only a standard that nails down the data types and the features of the languages, but the syntax of each language typically differs greatly from vendor to vendor. You can’t just export code from one vendor’s IDE and import it into another. They’re not compatible.

There was one other proprietary automation language I used, called Steeplechase. It’s a flowchart based language, similar to SFC, but simpler. I believe it was purchased by Entivity, which was then purchased by Phoenix Contact, so I think they still sell it. I remember it also had a ladder logic engine as well.

Edit:

For an example of ladder logic (and a bit of SFC), here’s an introductory tutorial I wrote on how to get going with Rockwell Software’s RSLogix 5000 ladder logic programming software for Allen-Bradley’s popular line of ControlLogix PLC’s: RSLogix 5000 Tutorial. It’ll give you a good idea of how it works, even though the example is a bit contrived.

I am using the Wikipedia definition of mechatronics, which would encompass things as common as a Dishwashers, ABS brakes in cars etc.

@Scott gives a very good answer for products focused on field programmable and bespoke systems. Another class of products – specific products developed with production runs of 1000’s or millions of units in mind (Toys/cameras, automotive systems such as ABS, remote door opening etc…..), Software in these automation systems are indistinguishable from traditional embedded systems, using identical software tools and development practices. Most of these are programmed in general purpose languages focused on reliability, efficiency and ability to run on resource constrained systems (obviously tradeoffs have to be made). These include as C/C++ (most common so must be mentioned despite the question) Modulo2, Ada, D. More recently Erlang was designed with principles more aligned to mechatronics than most general purpose languages.

As an addition to Scotts answer, there is also another strong force in the field of industrial automation: Siemens. Their PLC, the S7, is very common and comes with some – non-IEC-compatible – languages:

• graph (like SFC)
• kop
• fup
• scl (like ST): a little bit comparable to an programming language like C. It’s actually readable
• awl (like IL): Assembler-like programming.

Which language you like is totally based on your own decision. For easy I/O Mapping and simple decision-making i would stick with il/awl, if i have to programm complexer things, i rather stick with st/scl.

First of all I think actually all programming languages ​​which allows you to write Hardware related. e.g. C/C++, Assembler. In my opinion for hardware-oriented programming, you do not manage it without C/C++. It’s the best and safest choice. But you can try it with python! There existing many hardware-oriented libs for Pyro, myro.
I search for this, here is my result:

google python, sensor, robotic

python hardware programming