Complete asebahttp integration

[MobsyaBot]

Issue by davidjsherman
Saturday Aug 15, 2015 at 10:08 GMT
Originally opened as aseba-community/aseba#400

---

Add menu entry for "Web Tools for Thymio" that runs asebahttp with the thymio_motion.aesl file parameter, the default TCP port 3000 (for the HTTP interface), and ser:name=Thymio-II; and asks user's web browser to open the javascript welcome page.

Depends on the following issues in https://github.com/davidjsherman/aseba/milestones/Version%201.4:

• write simple javascript page to show asebahttp status davidjsherman/aseba#8
• automatic reconnection when cable is unplugged davidjsherman/aseba#7
• thymio_motion.aesl needs to be installed with Aseba davidjsherman/aseba#6

See also issue #401

[MobsyaBot]

Comment by davidjsherman
Sunday Aug 16, 2015 at 08:54 GMT

---

After thinking about it, I believe that it is reasonable that both the web interface (davidjsherman/aseba#8) and Aseba Studio can communicate with the robot at the same time. If asebahttp is run as described above, it will lock the USB connection and prevent Aseba Studio from communicating with the robot.

Consequently, I think that a better solution would be that the menu entry run asebamedulla in addition to asebahttp as described above. In that way Aseba Studio can share the connection to the robot using dashed target tcp:;port=33333, and asebahttp will relay Aseba tcp:;port=33333 to HTTP localhost:3000.

[MobsyaBot]

Comment by stephanemagnenat
Sunday Aug 16, 2015 at 19:59 GMT

---

I agree but see two open questions:

• Should one run asebamedulla or asebaswitch? To former provides a DBus bridge but is heavier and seems to have some bugs while the later is simpler. Also, asebamedulla does not run on Windows.
• If we answer switch to the previous question, shouldn't the switch feature be provided by asebahttp itself?

[MobsyaBot]

Comment by riedo
Tuesday Aug 18, 2015 at 07:03 GMT

---

asebamedulla is currently not packaged for Mac OS either. Why not use asebaswitch?

[MobsyaBot]

Comment by stephanemagnenat
Tuesday Jan 26, 2016 at 16:51 GMT

---

Asebahttp is now working with protocol 5 (see 31d6374), so I retarget this issue for Aseba 1.6.

[MobsyaBot]

Comment by davidjsherman
Thursday Jan 11, 2018 at 15:53 GMT

---

Asebahttp acts as an asebaswitch since c682c21.

[MobsyaBot]

Comment by stephanemagnenat
Friday Feb 02, 2018 at 14:12 GMT

---

Do we still want this in addition to the launcher (#728)?

[MobsyaBot]

Comment by cor3ntin
Friday Feb 02, 2018 at 14:25 GMT

---

I'd say put all the issues vaguely related to the launcher or the switch in the launcher milestone and we will cleanup from there as we refine the use cases/ ux of the launcher ( and no, I don't think we want that, even though it's actually done on osx/win32, it will need to be improved, a lot )

[cor3ntin]

This is no longer relevant as the thymio device manager replaces the http switch