10.46243/jstj.2018.v3.i5.188 registered
Algorithmic Approach of Estimating And Selection of Inverse Kinematics For Planar Robotic Arm
Resolves to https://www.jst.org.in/index.php/pub/article/view/188
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jstj.2018.v3.i5.188
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 076551ffc7abe0c7…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Algorithmic Approach of Estimating And Selection of Inverse Kinematics For Planar Robotic Arm (PrincipalTitle)
Published 2018-09-29
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 03 · issue 05 · pages 31–42
Agents
- Rhenius J.Bright (author)
- S.Parthasarathi (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jstj.2018.v3.i5.188
Abstract
In this project, I researched the kinematic analysis of robot arm. The kinematic analysis is the relationships between the positions, velocities, and accelerations of the links of a man ipulator. The kinematics is divided into two types, forward kinematics and inverse kinematics. In forward kinematics, the length of each link and the angle of each joint is given and we have to calculate the position of any point in the work volume of the robot. In inverse kinematics, the length of each link and position of the point in work volume is given and we have to calculate the angle of each joint.The forward kinematic analysis is not difficult to solve. It is solved by using simple homogeneous matr ices. On the other hand, the inverse kinematics is so hard to solve and it will be harder if we increase the degrees of freedom. There are different methods to solve the inverse kinematics. The analytic method and Jacobian method are well -known.In the project, I used the analytic method. In the thesis, I designed a prototype robot arm with 3 freedom degrees. User interface application was created in the personal computer and the data was sent to the hardware application board by using serial communication c able. The program that runs over the application board receives the data and operates. So the end -effecter can be moved to the position we want to go
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jstj.2018.v3.i5.188 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Algorithmic Approach of Estimating And Selection of Inverse Kinematics For Planar Robotic Arm (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Rhenius J.Bright author: S.Parthasarathi publisher: Longman Publishers published: 2018-09-29 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 03 · no. 05 · pp. 31–42 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2026-09-08 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 88 fields set · sha256 2877220946bc… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
