Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Filament counter reset
#61
Hi
Is anybody can tell me if this is because the firmware J that I have this problem or if it's a bad slicing ?
I'm already doing a few pieces from the reset and it does not make me

On the left side of the room, it's me that I broke

Thank[Image: DSC_0030_2014-09-12.jpg][Image: DSC_0031.jpg]
Reply
#62
Hi,

The firmware reset bug normally makes the prints very brittle, the ones I had looked thin and when squeezed broke up very easy.
Reply
#63
Thin this is exactly what makes me
Yet I have not touched anything since
Because of a bad filament, I cogwheel which was filled with ABS, I will do another test to check

Edit: Finally after test, the problem is slicing or the cogwheel of the extruder which was dirty
Reply
#64
Great news that it's working for you now.
Reply
#65
I'm trying to reset the filament counter with my Arduino UNO R3 and could use some help please.

I copied the sketch found here into the Arduino IDE and got this error.(see image below)

sketch_sep14a.ino: In function 'void setup()':
sketch_sep14a:370: error: expected `;' before 'Serial'


Does anyone know what might have gone wrong?

[img]
Reply
#66
Hi Manny,

There is a wrong bracket on the line:-
IncrementSerial(&buf[0], 0, 12];

It should be :-

IncrementSerial(&buf[0], 0, 12);
Reply
#67
Just did the hack to the cartridge and so far so good. Using G firmware as recommended by many and testing software versions at the moment. Since the DaVinci printer is quite cheap when compared to competitors as a matter of principle I wouldn't mind paying for their expensive filament, but the quality is crap. Just used the cheaper filament on ebay and quality is much better (it looks like the prints were done on a different printer). Now I need to try the voltivo as it should be far superior.
Reply
#68
I am trying to use a Digispark (http://digistump.com/category/1) in place of an Arduino UNO, but I am not sure how to change the read/write pin (I believe it is supposed to be PIN 7) to a pin the Digispark can use. Is there a reason we are using Pin 7? Can I use any digital out pin? Thank you for the help.

https://github.com/voltivo/davinci_filam..._eprom.ino
Reply
#69
you should be able to modify the code to use just about any pin you wish, other than the pen for the on-board LED. The code (sketch ) defines the pin that will be used. it is quite possible the code works just fine on your board, you likely only need to locate the physical pin that would correspond to the PIN defined for the Arduino.

Kieth
Reply
#70
Thanks Keith, that is what I am trying to do, but I can't figure out where in the code it defines Pin 7 (or the LED pin for that matter). The digispark only has 5 pins, so unfortunately that means I have to change to code.

It wouldn't be the end of the world to buy a new arduino, I just figured if I could use a board that I already had, I could save a few bucks.
Reply
#71
I think this is the code you're looking for .....

void setup() {
pinMode(13, OUTPUT);
Serial.begin(115200);
}

Presumably, you would change 13 to whatever pin you're using.
Davinci 1.0 with repetier 0.92 & E3D hotend
Slicer - Simplify3d 


Reply
#72
Thanks Scott, but pin 13 is just for the LED. I did some research on the library the code uses, and the library itself calls out Pin 7 specifically - still don't know why or how to change it. So I just went ahead and bought an Arduino from micro center for $10 (which is much less than the $27 I spent last time).
Reply
#73
Yeah OK, the post is 4 months old, but I did all this yesterday so.... now no one else has to.

Code:
// extruder temp, default is 210 C for ABS
//char et[] = {0x96,0x00}; // 150 C
//char et[] = {0x9b,0x00}; // 155 C
//char et[] = {0xa0,0x00}; // 160 C
//char et[] = {0xa5,0x00}; // 165 C
//char et[] = {0xaa,0x00}; // 170 C
//char et[] = {0xaf,0x00}; // 175 C
//char et[] = {0xb4,0x00}; // 180 C
//char et[] = {0xb9,0x00}; // 185 C
//char et[] = {0xbe,0x00}; // 190 C
//char et[] = {0xc3,0x00}; // 195 C
//char et[] = {0xc8,0x00}; // 200 C
//char et[] = {0xcd,0x00}; // 205 C
char et[] = {0xd2,0x00}; // 210 C XYZ ABS Default
//char et[] = {0xd7,0x00}; // 215 C
//char et[] = {0xdc,0x00}; // 220 C
//char et[] = {0xe1,0x00}; // 225 C
//char et[] = {0xe6,0x00}; // 230 C
//char et[] = {0xeb,0x00}; // 235 C
//char et[] = {0xf0,0x00}; // 240 C
//char et[] = {0xf5,0x00}; // 245 C
//char et[] = {0xfa,0x00}; // 250 C
//char et[] = {0xff,0x00}; // 255 C UPPER LIMIT

// bed temp, default is 90 C for ABS
//char bt[] = {0x19,0x00}; // 25 C Room Temp More or Less
//char bt[] = {0x1e,0x00}; // 30 C
//char bt[] = {0x23,0x00}; // 35 C
//char bt[] = {0x28,0x00}; // 40 C
//char bt[] = {0x2d,0x00}; // 45 C
//char bt[] = {0x32,0x00}; // 50 C
//char bt[] = {0x37,0x00}; // 55 C
//char bt[] = {0x3c,0x00}; // 60 C
//char bt[] = {0x41,0x00}; // 65 C
//char bt[] = {0x46,0x00}; // 70 C
//char bt[] = {0x4b,0x00}; // 75 C
//char bt[] = {0x50,0x00}; // 80 C
//char bt[] = {0x54,0x00}; // 85 C
char bt[] = {0x5a,0x00}; // 90 C XYZ ABS Default
//char bt[] = {0x5f,0x00}; // 95 C
//char bt[] = {0x64,0x00}; // 100 C
//char bt[] = {0x69,0x00}; // 105 C
//char bt[] = {0x6e,0x00}; // 110 C
//char bt[] = {0x73,0x00}; // 115 C

EDIT: Well, that was supposed to be in reply to Taylor Teune's post....
Reply
#74
It was my understanding that an external UNI/O library was required to compile the filament reset sketch, but reading through the posts here that is not mentioned. Am I just making things up? Because if there is a way to make something more difficult than it needs to be I am certainly the one to find it.
Reply
#75
(05-26-2014, 02:21 PM)Bob Wrote: The code is configured to use digital port D7 for the data line, which maps to digital pin 7 on the Pro Mini. D7 maps to digital pin 38 on the Mega2560, so try using pin 38 for the data line. (I used a teensy 2 by hooking up pin 14 for the data line.)

You fixed my issue. Thanks.
Reply
#76
(05-29-2014, 04:28 PM)I\M trying to recalculate the filament length Wrote: I could not get the python terminal to replicate your python answer, using the python script you posted.  When I finally got it to run in cmd prompt, it gave me no answer at all.  I'm sure it was a user error...me.  If you could please calculate the length of the filament to "360m" in this section, of the reset code; I would like to try it with my "J" software because the setting for "400m" does not work:
Code:
// Value to write to the EEPROM for remaining filament lenght
// Default Starter Cartdridge is 120m
//char x[] = {0xc0,0xd4,0x01,0x00}; //120m
char x[] = {0x80,0xa9,0x03,0x00}; //240m
//char x[] = {0x80,0x1a,0x06,0x00}; //400m doesnt work with j firmware
I feel 360m will work because it is a derivative of 120...240...360.
In python, you can compute the bytes with:

Code:
# create a little-endian string of hex-encoded bytes for 999000 (length is in mm)
hexval='%0.8x' % 999000
# Swizzle to big-endian order:
bytes=[hexval[i-2:i] for i in range(len(hexval),0,-2)]
# compose the assignment for x:
'char x[] = {' + ','.join(['0x'+s for s in bytes]) + '};'

which returns:

Code:
char x[] = {0x58,0x3e,0x0f,0x00};
Reply
#77
(05-11-2014, 01:53 PM)pdiddy Wrote:
Quote:On the purple,  I used ext temp 240, bed temp 95, no glue,  no rafts. It sticks okay at the higher temps.

Kieth

And which method did you use for setting those ? Filament eeprom or slic3r ?

thanks

I bought purple fillament.... I set mine to 93 bed 130 degree extruder, and burnt out the wire connector to the extruder.  I see that is a common occurance and ordered some deans connectors.  In the meantime I rigged the connector with black tape to hold it in place, but now when I printing the extruder temperature soars way above the 130 degrees I set it at, and all the cables next to the extruder get very hot also, causing me to have to cancel the print and possibly damaging the machine further.   Is this because of the bad connector?  Any ideas?
Reply
#78
(01-11-2017, 11:25 PM)tonyi Wrote:
(05-11-2014, 01:53 PM)pdiddy Wrote:
Quote:On the purple,  I used ext temp 240, bed temp 95, no glue,  no rafts. It sticks okay at the higher temps.

Kieth

And which method did you use for setting those ? Filament eeprom or slic3r ?

thanks for answering.  I used the slic3r method shown here:  //www.youtube.com/watch?v=UiF1Jt65RYk  I received my Dean connectors today and still have to install them.  I wanted to take a look here before installing them and trying it all out, in case I missed something.  I'll try printing with xyz software only at first to see how it goes with the purple filament...

I bought purple fillament.... I set mine to 93 bed 130 degree extruder, and burnt out the wire connector to the extruder.  I see that is a common occurance and ordered some deans connectors.  In the meantime I rigged the connector with black tape to hold it in place, but now when I printing the extruder temperature soars way above the 130 degrees I set it at, and all the cables next to the extruder get very hot also, causing me to have to cancel the print and possibly damaging the machine further.   Is this because of the bad connector?  Any ideas?
Reply
#79
(01-18-2017, 10:51 PM)tonyi Wrote:
(01-11-2017, 11:25 PM)tonyi Wrote: [quote pid='174' dateline='1399816410']
I replaced the connectors with the Deans and the DaVinci is working fine, while using the XYZ software; without temperature spiking upwards and also without the cables getting burning hot.   The connectors seem to have resolved all the problems, even though my soldering isn't the greatest.

[/quote]
Reply
#80
(05-29-2014, 04:28 PM)bobd Wrote: In python, you can compute the bytes with:

Code:
# create a little-endian string of hex-encoded bytes for 999000 (length is in mm)
hexval='%0.8x' % 999000
# Swizzle to big-endian order:
bytes=[hexval[i-2:i] for i in range(len(hexval),0,-2)]
# compose the assignment for x:
'char x[] = {' + ','.join(['0x'+s for s in bytes]) + '};'

which returns:

Code:
char x[] = {0x58,0x3e,0x0f,0x00};

I'm still trying to get this code, to spit out "char x[] = {0x58,0x3e,0x0f,0x00};" after it runs.  I got the code to run on python 27 and Thonny but, neither program spits out any answer, after it runs.  Am I missing something that needs to be added to the above code?  Has anybody had any luck getting the script to run correctly and give an answer when finished running?
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)