Welcome! Log In Create A New Profile

Advanced

Memory issues

Posted by Anton Dmitrievsky 
Memory issues
July 13, 2011 03:54AM
Hi,

I'm working with FiveD_GCode firmware released on 2011/05/09.

I have a Sanguino board with ATMega644P-20AU controller.

I've configured the firmware to use the internal extruder (#define EXTRUDER_CONTROLLER EXTRUDER_CONTROLLER_INTERNAL).

When I compile the firmware and upload it into the board I get the following messages from Host Software:

DEBUG: The distribution preferences file and yours match. This is good. [0,004s/-1310547177460ms]
DEBUG: GCode opening port /dev/ttyUSB0 [0,210s/206ms]
Stable Library
=========================================
Native lib Version = RXTX-2.2pre2
Java lib Version = RXTX-2.1-7
WARNING: RXTX Version mismatch
Jar version = RXTX-2.1-7
native lib Version = RXTX-2.2pre2
DEBUG: Attempting to initialize Arduino/Sanguino [1,308s/1098ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,310s/2002ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: [3,314s/4ms]
comms: Response: [3,315s/1ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,316s/1ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: [3,317s/1ms]
comms: Response: [3,317s/0ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,318s/1ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: [3,318s/0ms]
comms: Response: [3,318s/0ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,320s/2ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: [3,320s/0ms]
comms: Response: [3,320s/0ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,322s/2ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: [3,322s/0ms]
comms: Response: [3,322s/0ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,324s/2ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: [3,324s/0ms]
comms: Response: [3,325s/1ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,326s/1ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: [3,326s/0ms]
comms: Response: [3,326s/0ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,328s/2ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap: [3,328s/0ms]
comms: Response: [3,329s/1ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,330s/1ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap:704640773 [3,330s/0ms]
comms: Response: 704640773 [3,330s/0ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,332s/2ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap:704640873 [3,332s/0ms]
comms: Response: 704640873 [3,332s/0ms]
comms: G-code: N0 M110 *3 dequeued and sent [3,334s/2ms]
ERROR: GCodeWriter.waitForResponse() - dud response from RepRap:704640773 [3,334s/0ms]
--- and so on.

The Host Software user interface is not starting.

But if I change the RESPONSE_SIZE constant from 256 to 50 bytes in the features.h file all works fine. The constant defines the size of the buffer for communication with the host.

I think it's a lack of RAM. But the ATMega644P has 4 KByte of RAM and it's more than enough for reprap.

Am I the only person that experience that difficulties? Perhaps I'm doing something wrong?

I'm using:
* 64-bit Ubuntu 11.04
* uname -a: Linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
* avr-gcc: 4.3.5
* avr-libc: 1.6.8-2
* arduino-0018 with Sanguino board extension.

The similar thread: [forums.reprap.org] but there is no solution.

There is configuration.h file in the attachment.
Attachments:
open | download - configuration.h (21.5 KB)
VDX
Re: Memory issues
July 13, 2011 05:11AM
... could be you have the wrong baudrate, as the displayed response - "comms: Response: [3,329s/1ms]" - seems to be a 'non printable character' ...


Viktor
--------
Aufruf zum Projekt "Müll-freie Meere" - [reprap.org] -- Deutsche Facebook-Gruppe - [www.facebook.com]

Call for the project "garbage-free seas" - [reprap.org]
Re: Memory issues
July 13, 2011 05:18AM
Baud rate is 57600. I've tried to use jpnevulator and the start message appears ok. And if I change RESPONSE_SIZE constant all works fine.
Sorry, only registered users may post in this forum.

Click here to login