beep

[César Araújo]

Hello guys, my r2c2 when i turn on after a one second it makes a long beep and never stops, all motor leds stay on. what could it be?

Thanks in advance.

[César Araújo]

If i flash the ribeiro v4 i end up with lights of motors on and the power led on. Nothing more. The Original firmware makes the printer beep a hight pitch sound making it noisy, it wont work at all.

Help me please.

[César Araújo]

This is my video of the printer
https://www.youtube.com/watch?v=v_NeDK44IhY

[Chaslot Nicolas]

hi,

well that's weird.. did you try to upload a new firmware?

nick

--
You received this message because you are subscribed to the Google Groups "R2C2 - Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---suppor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[César Araújo]

yes i have.
the ricardo firmware locks the motors and the original firmware does this.

i think it is in the init since im trying to debug this problem using beep codes (i dont have the necessary cables to read the serial output).

If anyone could help me other wise im shipping it to aveiro :)

sexta-feira, 9 de Janeiro de 2015 às 22:22:12 UTC, César Araújo escreveu:

[Rui Ribeiro]

Hi Cesar,

Please note... My name is "Rui". ;-)

What do you mean by "locks the motors"? It means that the motors are
locked, but they move on commands (if they do, then this is normal
behaviour), or it means that the motors are locked and don't move at
all?

When they are on the "lock state" can you enable/disable the temperature?

Please note that the firmware is kept on the chip, not on the sd card.
Therefor, the test that you do with and without the SD card is
basically the same.

When the firmware runs, it tries to find out if the "boot" is pressed,
if it is, it goes to a second firmware that is on the chip (the
r2c2-usb-bootloader). If not, it will try to mount the sd card. If it
does, then it will try to find firmware.bin file. If it find, it will
load that file, move it to firmware.bck and run it.

The beep happens, in fact two... if you notice, it blocks on the
second tone. While it is trying to do some of the following steps
under the the "init" function: setup the io; read the config file; the
"slow timers" for the temperature monitororing... and, at the end,
state on the serial "Start ok"

Could you please test if you can see the "start ok" on the console? It
may be a bit tricky as it will be very fast from bootup to this string
output. Usually faster than Windows can understand what is the new USB
device. If you use Linux, it is much easier. (I've found out lots of
things about the firmware while debugging it on its boot using a RPi
as my main console)

For me... what you have is a bad firmware file. Try to reload it again
either from mine, or from the webpage. Strange things do happen
sometimes.

Rui Ribeiro

[cesar....@g.xarevision.pt]

Hello rui,

Thanks for the response.
I tried to debug the board using the console without sucess i dont know how to connect it to the pc, i have tried to put a arduino in as serial adapter  but my pc does not detect the arduino port. http://www.zoobab.com/use-the-arduino-as-a-serial-adaptor

Second i tried to write the debug to the sdcard but in the part where i start the code (app_main in the mendel.c file) at the the top of the app_main the sdcard is not initialized yet, and i did not want to mess a lot of code.

Third I tried something the most stupid solution, debug using beep codes. I was compiling a few versions of the original firmware and putting the beep code in some other places until i find where it freezed. I soon quited it. It was to painfull and i was getting nauseas.

This means i can flash code, it beeps and when the long beep freezes i get nothing. Motors are stuck i cannot move them, i can connect to the printer but nothing else, commands are not accepted they get queued.

What else can i do?

Can you tell me rui how do you debug? How do you read the serial port output?

Thanks in advance.

ps: Name rui by any chance ribeiro?

sexta-feira, 9 de Janeiro de 2015 às 22:22:12 UTC, César Araújo escreveu:

[Rui Ribeiro]

Does it blocks with my firmware also?

If you use my firmware, you can just connect to the R2C2 board on the
serial port, it sends lots of debug while booting.

I connect to the PC using a USB serial interface, or directly to the
Arduino, or directly to the RaspPi. Lately I'm using the RaspPi.

The arduino link that you show has not enough information for you to
link the r2c2 board. First you need to have some code on the arduino
to "bridge" the serial R2C2 interface and your usb serial interface.

Something like:
http://arduino.cc/en/Tutorial/MultiSerialMega

I'm using 57600 bitrate on the serial port.

Then you have to make the connections. Actually you will need only 2
wires. One for ground and another for TX (r2c2) that connects to the
RX (arduino) pin.

I will send you a picture later tonight so that you won't miss it.

PS: Yes, my name is Rui Ribeiro

Rui

[Rui Ribeiro]

Hi César,

Look at this photo to see where to put the GND, RX and TX wires.
Please note RX and TX is from the R2C2 standpoint. RX on R2C2 will
connect to the TX pin on the other device and viceversa about the TX
wire. The GND works as "reference" for the digital signals on the TX
and RX wires, so it is the same on both sides.

No need to add anything else as voltage or reset.

Be aware that the voltages should be similar on both devices. As I
said, I'm using 5v devices (arduino, raspberry, usb FDTI serial
interface), so you should be ok with that.

Rui