10.46243/jst.2021.v6.i03.pp189-200 registered
MULTI-TERRAIN ROBO DESIGN
Resolves to https://www.jst.org.in/index.php/pub/article/view/873
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2021.v6.i03.pp189-200
Registered 29 Sep 2026 via crossref · record version 2 · last change 30 Sep 2026, 12:00 AM · record sha256 09f13da19bae76af…
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
MULTI-TERRAIN ROBO DESIGN (PrincipalTitle)
Published 2021-05-16
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 06 · issue 03 · pages 189–200
Agents
- Dr.B.James Prasada RAO (author)
- Dr.Babu.R (author)
- Dr.Ravinaik Banothu (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2021.v6.i03.pp189-200
Abstract
Due to the rapid progress in the field of robotics, it is a high time to concentrate on the development of a robot that can man in all type of landscapes, ascend and descend stairs and sloping surfaces autonomously. This paper presents details of a prototype robot which can navigate in very rough terrain, ascend and descend staircase as well as sloping surface and cross ditches. The robot is made up of six differentially steered wheels and some passive mechanism, making it suitable to cross long ditches and landscape undulation. Static stability of the developed robot have been carried out analytically and navigation capability of the robot is observed through simulation in different environment, separately. Description of embedded system of the robot has also been presented and experimental validation has been made along with some details on obstacle avoidance. Finally the limitations of the robot have been explored with their possible reasons.
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/jst.2021.v6.i03.pp189-200 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | MULTI-TERRAIN ROBO DESIGN (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Dr.B.James Prasada RAO author: Dr.Babu.R author: Dr.Ravinaik Banothu publisher: Longman Publishers published: 2021-05-16 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 06 · no. 03 · pp. 189–200 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-12 | 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) | 89 fields set · sha256 6c720086ecab… |
| 2 | 30 Sep 2026, 12:00 AM | 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.
