poppy-project / poppy-ergo-jr Goto Github PK

Hello,

I am trying to use the face tracking primitive but its not working since the pi (booted with the ergo os image) seems to be missing a package that the camera/face-tracking relies on. We are unable to install the package using pip since the pi will only connect local networks and not the internet. (we tried playing around the the network settings but that broke the system and we have to re-burn the os image on the sd card)

Could you recommend what I do to access face tracking?

Best,

Victor

Hello,

I have successfully been able to connect the 6 ergo jr motors with a u2d2 ftdi and have checked its functioning using herborist as suggested.

However, when I try to create a robot using your python library [poppy = PoppyErgoJr()] I get the following error: OSError: Could not initialize robot: [Errno 2] could not open port /dev/ttyAMA0: [Errno 2] No such file or directory: '/dev/ttyAMA0'

The problem I think is that the u2d2 is connect to ttyUSB0 as verified by command "dmesg | grep FTDI".

Do you have any suggestions on how to fix this? Any help would be very much appreciated :))

P.S. while working on this project, we found that printing the lamp head for the Ergo either resulted in a weak motor connector part or a weak lamp shade dependent on the orientation of the lamp head. One of my teammate designed and printed a two part version of the lamp head that is significantly stronger and we were wondering if you'd be interested in seeing it and maybe including it with the ergo cad files as an option?

We have a strange issue with a standard Ergo Jr kit (Pixl, rapsberry pi, pypot v2.11.1).

The robot instanciation raises this error:

Python 2.7.10 |Continuum Analytics, Inc.| (default, Oct 28 2015, 19:48:38) 
Type "copyright", "credits" or "license" for more information.

IPython 4.0.0 An enhanced Interactive Python.

In [1]: import poppy_ergo_jr

In [2]: poppy = poppy_ergo_jr.PoppyErgoJr()
select timeout
select timeout
Segmentation fault

Communication with motors seems ok:

import pypot.dynamixel
dxl = pypot.dynamixel.Dxl320IO('/dev/ttyAMA0')
dxl.scan(range(10))
>> [1, 2, 3, 4, 5, 6]

But not the camera ...

poppy@poppy:~ $ raspistill -o cam.jpg
mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board

Hey I burnt the latest image using etcher and when I boot it, it's stuck on the rainbow screen.

Hello, I cloned the project from two different operating systems (i,e, Ubuntu and OSX) and in each attempt the result was the same: files's are broken (file size is 132 bytes). So, I cannot open any of the files including the pdf files.

How many motors did you use in the installation tutorial? Is it a servo motor or a stepper motor?

Using this image: 2016-09-09-poppy-ergo-jr.img.zip

I encounter the following problem while configuring the ergo jr motors:

poppy@poppy:~ $ poppy-configure ergo-jr m1
usage: dxl-config [-h] --id ID --type
                  {RX-64,MX-12,AX-18,MX-64,RX-24,RX-28,AX-12,MX-28,XL-320,MX-106}
                  [--port {/dev/ttyAMA0}]
                  [--return-delay-time RETURN_DELAY_TIME]
                  [--angle-limit ANGLE_LIMIT ANGLE_LIMIT] [--goto-zero]
dxl-config: error: argument --port: invalid choice: '/dev/serial0' (choose from '/dev/ttyAMA0')

It seems like a problem specific to the raspberry pi 3.

Hey I after running curl -L https://raw.githubusercontent.com/poppy-project/raspoppy/master/raspoppyfication.sh | bash -s "poppy-ergo-jr" The default user isn't changed. Also what is the bare minimum I need to install to use the ergo jr arm as in I am working with python scripts to read the arms current position and command it to move. It seems excessive to need to change the user and so on.

For end-users, motors seem not precise, but with better PID coefficients it could fix it.

A shutdown primitive which will stop all running primitive and set motors compliant.
We should make it well because it can cause race conditions.
Related to poppy-project/puppet-master#21.

Note: it should be mabye usefull to add it directly in pypot.

When lauch rostopic list, there is an error in the terminal

No module named Cryptodome

[...]Will do more investigation later[...]

Hi,

I'm trying to slice the .stl files into .gcode and have been using Cura version 3.1.0. Cura isn't able to open any of the .stl files though, returning a vague error message that says, "Failed to load {path to file}". Has anyone else had this problem? If not, what slicer did you use?

We should draw an hole on the disk_support to unmount the μSD card more easily.

Tests done after a fresh install of the last release image

Here are two videos to compare RPi 2 & 3 with the same dance primitive, the same robot, the same SD card, connected by ethernet.
Rpi2: https://www.youtube.com/watch?v=VN0-8D-YalY
RPi3 : https://www.youtube.com/watch?v=C2j_SZYeXww

For an unknown reason, it's even worse if the RPi3 is connected by wifi.

L'idée de Didier d'avoir une notice de montage « à la IKEA » me semble être une bonne idée.
On peut utiliser nos modèles 3d pour le faire, il faut en revanche avoir un scénario avant de faire les captures.

Hello,

First, thanks for open-sourcing the robots and platform in general! I am using Pinocchio and trying to plug the Poppy Ergo Jr robot inside. However, I can see that you updated the stl files in the master branch without updating the urdf file. The urdf points to the stl files of the URDF branch and as is the master branch does not work for me. Would it be possible to update the urdf file of the master branch ?

I would like to use the Poppy Ergo Jr robot with an horizontal gripper (the default urdf is with the gripper in vertical mode). However the stl files of the URDF branch are in 5 sections only whereas I can see the stl of the master branch are break down into more pieces. Thus if I had the urdf of the master branch, I could modify it easily to get what I want.

Thank you,

Robin

I used today a Raspberry Pi 2 rev 1.2 (in a Kubi package) with a Official Generation Robot kit, and the official image does not work with it.
When we plug the Raspberry Pi with the SD card, the green LED blinks with a specific pattern, which correspond to this issue : "SDRAM not recognised. You need newer bootcode.bin/start.elf firmware".
This is very strange, our official image is compatible with Raspberry Pi 2 rev1.1 and with Raspberry Pi 3 rev1.1 and the Raspberry Pi 2 rev1.2 is supposed to be older than Raspberry Pi 3...

I tested with the last Jessie version and it works well, so we have to do another image very soon.

The wifi on my rpi connects pretty faster, but after installing the libraries I see a clear issue with the wifi where it takes a long time to connect and sometimes I have to reconnect it to make it work.

Bonjour,

Nous avons essayé de lire les fichiers STL de Popy ergo jr avec Cura, Makerbot, Meshmixer et Solidworks mais sans succès.
Les fichiers semblent invalides.

We should improve long_U to reduce the slack on m1. It is quite annoying, it reduces a lot the precision of the end effector.
There is less slack between m4 and short_U, but it should be improved too.

Mercredi 28/10 à 11h
Objectifs :

• spécification mécanique de Ergo Jr
• discussion pour préparer l’ergo junior (vendu par génération Robot)
• mettre dates sur tout les items de la RoadMap Poppy Ergo ( https://app.asana.com/0/59071714089938/60793782743427 )

Thingiverse could be a great communication tool for the project.
@matthieu-lapeyre could you do it ?

• Positions of jump pritive are not valid for the Poppy Ergo Jr
• Pid registers are not reset to default after the stop

In the test image page, when you push the capture button, we have a 500 internal error

I would like to inquire why this project has not continued to be updated and developed. This is a great project, and I can't see the latest news on the community forum. It seems like I can't post on the community forum

We need to write a set of demo/introduction Python notebooks for the Poppy Ergo Jr:

Discover your robot:

• Make motors move, turn on LEDs...
• Start/stop pre-programmed behaviours
• Record/Replay motions learnt by demonstration

Advanced:

• Write a simple visual servoing of the head of the robot using blob detection
• Add a Snap block to use the blob detection
• Using Explauto to make the robot jump as far as possible (in V-REP probably)
• Benchmark the robot performance and debug
• Connect to processing

Fondation Cartier like Activity:

• play with a cube using curiosity
  • using V-REP
  • with the real robot

Do not hesitate to propose ideas for notebooks, or even better notebooks ;-)