Taurob tracker

Taurob tracker is a mobile robot, manufactured by taurob GmbH in Austria. It has been originally developed as a remote controlled reconnaissance platform for fire departments. [1][2][3] but is currently used also by the military,[4][5] civil-defense units, universities [6] and the oil and gas industry [7] around the world.

taurob tracker robot

Since 2013 an ATEX certified variant (Zone 1), called taurob tracker Ex is available, which is able to drive in explosive atmospheres safely.[8]

A taurob tracker version with sensors for environments with extreme smoke (e.g. fires in tunnels or subway stations) is currently being developed in the EU funded "SmokeBot" project[9]

Specifications [10]

Dimensions100 x 58 x 42 cm
Weight60 kg
Payload25 kg
Operating Distance (Line of sight)500 – 1000 m
Speed7 km/h
Temperature Range-20 °C to +60 °C
Battery Endurance3 hrs. (driving), 10 hrs. (measuring)
CertificationsATEX, IP 67
Max. Climb Capabilities40°, 35 cm obstacles, stairs
Arm – Mobility4 Degrees of Freedom
Arm – Max. Reach140 cm
Arm – Max. Lifting Capacity5 kg fully extended

Track assembly

Argonaut robot with forward wheels lowered for better climbing traction

Compared to most other mobile robots, the taurob tracker has a unique track geometry which allows it to climb over obstacles with just one pair of tracks. Due this geometry the tracks do not lose their tension when raising or lowering the front wheels. Further advantages include improved traction (thus the name of the robot) on uneven ground and a rapid track exchange mechanism.[11]

Notable appearances

In 2016 a taurob tracker platform was used in the RoboCup Rescue League by team Hector.[12]

In 2017 a variant of taurob tracker called "Argonaut" has won the ARGOS Challenge organised by Total S.A.. It is the first fully autonomous, ATEX certified mobile inspection robot for Oil and Gas installations. According to Total it will be used on their industrial sites by 2020.[13][14]

gollark: <@!206233133228490752> Sorry to bother you, but keypairs generated by `ccecc.py` and the ECC library in use in potatOS appear to have different-length private and public keys, which is a problem.EDIT: okay, apparently it's because I've been accidentally using a *different* ECC thing from SMT or something, and it has these parameters instead:```---- Elliptic Curve Arithmetic---- About the Curve Itself-- Field Size: 192 bits-- Field Modulus (p): 65533 * 2^176 + 3-- Equation: x^2 + y^2 = 1 + 108 * x^2 * y^2-- Parameters: Edwards Curve with c = 1, and d = 108-- Curve Order (n): 4 * 1569203598118192102418711808268118358122924911136798015831-- Cofactor (h): 4-- Generator Order (q): 1569203598118192102418711808268118358122924911136798015831---- About the Curve's Security-- Current best attack security: 94.822 bits (Pollard's Rho)-- Rho Security: log2(0.884 * sqrt(q)) = 94.822-- Transfer Security? Yes: p ~= q; k > 20-- Field Discriminant Security? Yes: t = 67602300638727286331433024168; s = 2^2; |D| = 5134296629560551493299993292204775496868940529592107064435 > 2^100-- Rigidity? A little, the parameters are somewhat small.-- XZ/YZ Ladder Security? No: Single coordinate ladders are insecure, so they can't be used.-- Small Subgroup Security? Yes: Secret keys are calculated modulo 4q.-- Invalid Curve Security? Yes: Any point to be multiplied is checked beforehand.-- Invalid Curve Twist Security? No: The curve is not protected against single coordinate ladder attacks, so don't use them.-- Completeness? Yes: The curve is an Edwards Curve with non-square d and square a, so the curve is complete.-- Indistinguishability? No: The curve does not support indistinguishability maps.```so I might just have to ship *two* versions to keep compatibility with old signatures.
gollark: > 2. precompilation to lua bytecode and compressionThis was considered, but the furthest I went was having some programs compressed on disk.
gollark: > 1. multiple layers of sandboxing (a "system" layer that implements a few things, a "features" layer that implements most of potatOS's inter-sandboxing API and some features, a "process manager" layer which has inter-process separation and ways for processes to communicate, and a "BIOS" layer that implements features like PotatoBIOS)Seems impractical, although it probably *could* fix a lot of problems
gollark: There's a list.
gollark: Lots of them.

References

  1. Matthias Biegl, Rainer Hasenauer, Lukas Silberbauer, Peter Filo, Jozef Orgonáš, Barbora Paholková, Charles Weber "Marketing testbeds for high tech innovation: The case of taurob robotics", IEEE, International Conference on Management of Engineering & Technology (PICMET), Kanazawa, Japan, 2014
  2. Kotrba, David. "Ein Roboter aus Wien hilft der Feuerwehr", Kurier, Vienna, 4 April 2013. Retrieved on 25 April 2017.
  3. Johannes Maurer, Gerald Steinbauer, Peter Lepej, and Suzana Uran. "TEDUSAR White Book - State of the Art in Search and Rescue Robots", TEDUSAR, Retrieved on 27 March 2017.
  4. doppeladler.com "Spürhund 2.0 der ABC Abwehr: Taurob Tracker", DOPPELADLER.COM - Plattform für Österreichs Militärgeschichte, Vienna, 1 November 2016. Retrieved on 27 March 2017.
  5. Radio Televizija Crne Gore "Opasnost im profesija", RTCG, Montenegro, 15 September 2016. Retrieved on 25 April 2017.
  6. Team Hector. "Our Robots", Team Hector, Retrieved on 27 March 2017.
  7. Argos Challenge Website "TEAM ARGONAUTS", ARGOS Challenge, Retrieved on 27 March 2017.
  8. "Interlink Petroleum Services", Oil Review Middle East, Retrieved on 27 March 2017.
  9. Guangfen Wei, Julian W. Gardner, Marina Cole, Yuxin Xing "Multi-Sensor Module for a Mobile Robot Operating in Harsh Environments", IEEE, 2016 IEEE SENSORS, Orlando, Florida, USA, 2016.
  10. taurob GmbH. "UGV – taurob tracker", taurob GmbH, Retrieved on 27 March 2017.
  11. EU patent EP2527235A1, Dr. Lukas Silberbauer, "Track assembly mounting", published Nov 28, 2012, issued May 4, 2011, assigned to taurob OG
  12. Stefan Kohlbrecher, Christian Rose, Dorothea Koert, Paul Manns, Florian Kunz, Benedikt Wartusch, Kevin Daun, Alexander Stumpf and Oskar von Stryk "RoboCup Rescue 2016 Team Description Paper Hector Darmstadt", RoboCup Rescue 2016 TDP Collection, Retrieved on 27 March 2017.
  13. Argos Challenge Website "TEAM ARGONAUTS", ARGOS Challenge, Retrieved on 27 March 2017.
  14. Total Website "THE ARGONAUTS ROBOT WINS THE ARGOS CHALLENGE!", Total S.A., Retrieved on 13 May 2017.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.