Go Down

Topic: Is Deviceprint immpossible to make work? (Read 5483 times) previous topic - next topic


Apr 14, 2009, 11:20 pm Last Edit: Apr 15, 2009, 12:17 am by spencerb8 Reason: 1
I have tried nemerous things to make the DevicePrint demo to work(thanks sirmorris).  You can find it here (http://arduinonut.blogspot.com/2009/02/libraries.html).  I am running arduino-0015 on Ubuntu Linux.  I'm using this circuit: http://circuitfun.files.wordpress.com/2009/02/spi-to-usd.jpg?w=497&h=345.  This is where I run into a snag:

uFat / DevicePrint Demo
2009 arduinonut.blogspot.com

Error  Couldn't initialise microfat
<press reset>uFat / DevicePrint Demo
2009 arduinonut.blogspot.com

Error  Couldn't initialise microfat
<press reset>

I get this over the serial connection.  As you can see I pressed the reset button but the same thing happens again.

I am desperate for help.



It worked first time for me. Where's the program stopping? IIRC the microfat startup can fail in 3 places, find out where it's stopping and that will tell you what the problem is.




Here's is a test sketch that should give some more information:


I have copied the library code into the sketch folder to make it easier to modify. Run the sketch and report what happens. It will not work with the libraries in place. Before you load the arduino-0015 gui and this sketch, DELETE OR MOVE THE FOLLOWING DIRECTORIES AND THEIR CONTENTS:


Report back on what result you get.



When I go to compile the brown bar shows up but it does not say anything.  What do I do?



Is the board connected? Is the serial port set correctly?

Can you tell us what you have done so far to find out why this is happening? That would help a lot. If you can say that the board is connected and the IDE can communicate then that narrows things down. Can you upload other sketches? Is there smoke coming from anything?


Its not on my arduino yet.  I did what you said then I clicked the play button to make sure there was no errors and the brownish redish bar came up.  But whats wierd is it said nothing.


Apr 15, 2009, 05:41 pm Last Edit: Apr 15, 2009, 05:44 pm by sirmorris Reason: 1
Did you change the text in the sketch to try and induce an error?
Did you do anything other than click the play button?
Try setting the compiler to verbose output. The information is available  on the main site on how to do this.


No, I didn't change the text at all.  Yes, all I did was click the play button.  I'll try the verbose output.


I turned on the verbose output but the same bar shows up.  If sombody tells me how to upload a pic I will take a screen shot.


Apr 16, 2009, 05:37 am Last Edit: Apr 16, 2009, 07:30 am by spencerb8 Reason: 1
Good news!!!!
DevicePrint is not impossible to make work!!
Well at least with the arduino fourm.

This is what I got:
uFat / DevicePrint Demo
2009 arduinonut.blogspot.com

All initialised OK!

And poof.

I did three things, first, in libraries I changed wconstants to WConstants as well as wprogram to WProgram.  Second, I built sirmorris's circuit instead of some other thing.  Third made sure there was a file on my SD card named data.txt and some data on it(I put 11mb of "B") on it.  Thats it!!

Thanks sirmorris and everybody else!!!! :)

Does anybody know how to make it write over the 512 bytes?


Does anybody know how to make it write over the 512 bytes?

You just keep writing strings. No other action is required. You can't write a string larger than 512 bytes in one go, as this would overflow the buffer.

Glad it's working for you!




I am going to make a barcode datalogger.  I need some help modifying the code.

The code link is at the bottom of the page:

If you are going to help me:
Please make the format like this:

You get the point, I want every scan to be on its own line like up there.  And I want every error that might come up to flash an led continuously on digital pin 8. I want the same led to be lit whenever it can accept another scan(so the led turns off for about 500 ms and turn on again when it can accept another scan).



You may get a better response if you focus on a specific problem that is standing in your way.  Perhaps explain your ideas for  how you want to interface the datalogger to the existing code and say how much you have done?

Go Up