Calibration - Revision history

Brian: /* Determine RAMPS units to ml conversion factor */

2025-03-06T05:50:14Z

Determine RAMPS units to ml conversion factor

Brian: /* Determine RAMPS units to ml conversion factor */

2025-03-06T05:48:21Z

Determine RAMPS units to ml conversion factor

Brian: /* Determine RAMPS units to ml conversion factor */

2025-03-06T01:50:45Z

Determine RAMPS units to ml conversion factor

Brian at 01:36, 6 March 2025

2025-03-06T01:36:10Z

Brian at 00:26, 6 March 2025

2025-03-06T00:26:07Z

Brian: /* Determine RAMPS units to ml conversion factor */

2024-08-16T23:45:21Z

Determine RAMPS units to ml conversion factor

Brian: /* Determine RAMPS units to ml conversion factor */

2024-08-07T08:23:59Z

Determine RAMPS units to ml conversion factor

Brian: /* Determine max pump speed */

2024-08-07T08:21:56Z

Determine max pump speed

Brian at 08:07, 7 August 2024

2024-08-07T08:07:15Z

Brian: /* Generating Gcode */

2024-08-07T08:06:16Z

Generating Gcode

@@ Line 22: / Line 22: @@
 So on 3/5/25 we calibrated from scratch. The 2000 RAMPs units pumped about 70 mls. There was a distinct difference in the Z from X and Y. This is likely some underlying effect I do not quite understand whereas X and Y are treated the same when the gcode is run to control a 3d-printer. The values we wound up for in terms of ml / units. x=.0348 , y=.03565, z=.03085.
-Do not use the 2k unit to test with. 10k seems to be a lot more reasonable where the outcome it about 350-400 mls in our setup which is weighed on most digital scales. Also - weigh the empty container each time. So run calibration, weigh, empty water thoroughly then weigh again. Also - run the 10k script for a few seconds until all the air bubbles disappear.
+Do not use the 2k unit to test with. 10k seems to be a lot more reasonable where the output is about 350-400 mls in our setup which is weighed on most digital scales. Also - weigh the empty container each time. So run calibration, weigh, empty water thoroughly then weigh again. Also - run the 10k script for a few seconds until all the air bubbles disappear. Then hit the reset button and put the output in the actual container. Then execute the script until completion.
 == Volume to fill mixer ==

← Older revision		Revision as of 05:48, 6 March 2025
Line 21:		Line 21:

	So on 3/5/25 we calibrated from scratch. The 2000 RAMPs units pumped about 70 mls. There was a distinct difference in the Z from X and Y. This is likely some underlying effect I do not quite understand whereas X and Y are treated the same when the gcode is run to control a 3d-printer. The values we wound up for in terms of ml / units. x=.0348 , y=.03565, z=.03085.		So on 3/5/25 we calibrated from scratch. The 2000 RAMPs units pumped about 70 mls. There was a distinct difference in the Z from X and Y. This is likely some underlying effect I do not quite understand whereas X and Y are treated the same when the gcode is run to control a 3d-printer. The values we wound up for in terms of ml / units. x=.0348 , y=.03565, z=.03085.
		+
		+	Do not use the 2k unit to test with. 10k seems to be a lot more reasonable where the outcome it about 350-400 mls in our setup which is weighed on most digital scales. Also - weigh the empty container each time. So run calibration, weigh, empty water thoroughly then weigh again. Also - run the 10k script for a few seconds until all the air bubbles disappear.

	== Volume to fill mixer ==		== Volume to fill mixer ==

@@ Line 20: / Line 20: @@
 This is done by 100Xcalibration, 10kXcalibration, 20k, 40k. These scripts exist for all of the X,Y and Z pumps. Start with the smaller ones and find one that will pump 100s of mls. We had a plastic graduated cylinder but any large light-weight cup would work. The idea is to run one of the above scripts and weigh how many grams of water it pumps. Make sure to tare the cup's added weight out and the grams will show you MLS. Then take the amount the amount pumped in RAMPS units (it is the value in the script's name) and divide it by the grams of waters. This will give you the  units/ml setting.
-So on 3/5/25 we calibrated from scratch. The 2000 RAMPs units pumped about 70 mls. There was a distinct difference in the Z from X and Y. This is likely some underlying effect I do not quite understand whereas X and Y are treated the same when the gcode is run to control a 3d-printer.
+So on 3/5/25 we calibrated from scratch. The 2000 RAMPs units pumped about 70 mls. There was a distinct difference in the Z from X and Y. This is likely some underlying effect I do not quite understand whereas X and Y are treated the same when the gcode is run to control a 3d-printer. The values we wound up for in terms of ml / units. x=.0348 , y=.03565, z=.03085.
 == Volume to fill mixer ==

← Older revision		Revision as of 01:36, 6 March 2025
Line 19:		Line 19:

	This is done by 100Xcalibration, 10kXcalibration, 20k, 40k. These scripts exist for all of the X,Y and Z pumps. Start with the smaller ones and find one that will pump 100s of mls. We had a plastic graduated cylinder but any large light-weight cup would work. The idea is to run one of the above scripts and weigh how many grams of water it pumps. Make sure to tare the cup's added weight out and the grams will show you MLS. Then take the amount the amount pumped in RAMPS units (it is the value in the script's name) and divide it by the grams of waters. This will give you the units/ml setting.		This is done by 100Xcalibration, 10kXcalibration, 20k, 40k. These scripts exist for all of the X,Y and Z pumps. Start with the smaller ones and find one that will pump 100s of mls. We had a plastic graduated cylinder but any large light-weight cup would work. The idea is to run one of the above scripts and weigh how many grams of water it pumps. Make sure to tare the cup's added weight out and the grams will show you MLS. Then take the amount the amount pumped in RAMPS units (it is the value in the script's name) and divide it by the grams of waters. This will give you the units/ml setting.
		+
		+	So on 3/5/25 we calibrated from scratch. The 2000 RAMPs units pumped about 70 mls. There was a distinct difference in the Z from X and Y. This is likely some underlying effect I do not quite understand whereas X and Y are treated the same when the gcode is run to control a 3d-printer.

	== Volume to fill mixer ==		== Volume to fill mixer ==

@@ Line 10: / Line 10: @@
 pumpmaxspeedtest.gcode - So this needs to be spooled in pronterface so the console can be observed. I didn't see a way to have printf type functionality in gcode so instead you will need to watch the console as it spools the command directly. When it starts to skip, make note of the last speed sent to the RAMPs board via the gcode. This is the absolute max speed of the pump but should be lowered again. It may be the case that the pump skips when there is more pigment than solution in the hose. This hasn't been tested but reduce it by 10% and keep lowering it until success. Try smaller batches at first.
-Alternatively would just be to create a series of files by hand. Or count the number of beeps using the beepingspeedtest.gcode. This will require you to count the beeps yourself and note at what point it failed. Then multiple this beep number by 500 to know the speed at which is started to skip. -- DOUBLE CHECK
+Alternatively would just be to create a series of files by hand. Or count the number of beeps using the pumpmaxbeatspeedtest.gcode. This will require you to count the beeps yourself and note at what point it failed. Then multiple this beep number by 200 to know the speed at which is started to skip. If you look at the source-code, it will likely have steps of 200. For example "G1 X-200 F5400" will test the  pump by moving it 200 RAMPS units at a speed of 5400. There are no loops in gcode so there is just a big list of increments. The next line should have F5600. This way it increases and beeps on each increase, allowing a test without a console to read from. (the output is done via beeps) We gave the advice of cutting back the speed 10% from where it fails but this is likely not enough and when the pumps do jam up it will interrupt the process and if not caught - require discarding of the existing mixer or pigment solution. The first pump starts at 5000. There is a beep first and then 1 for every 200 increment. So if you hear 31 beeps before the pump jams then it should be using a speed of "5000 + 200 * 31". We suggest looking at the source-code to verify this. It will jam before earlier speeds and why some amount needs to be trimmed off this.
 == Determine RAMPS units to ml conversion factor ==

← Older revision		Revision as of 23:45, 16 August 2024
Line 16:		Line 16:

	If the pumps are not identical then we suggest you try on all 3 to verify they pump the same amount. If they are not the same then reach out to us on the forum or email. The current php script that generates the gcode does not handle pumps that vary amongst themselves.		If the pumps are not identical then we suggest you try on all 3 to verify they pump the same amount. If they are not the same then reach out to us on the forum or email. The current php script that generates the gcode does not handle pumps that vary amongst themselves.
		+
		+	This is done by 100Xcalibration, 10kXcalibration, 20k, 40k. These scripts exist for all of the X,Y and Z pumps. Start with the smaller ones and find one that will pump 100s of mls. We had a plastic graduated cylinder but any large light-weight cup would work. The idea is to run one of the above scripts and weigh how many grams of water it pumps. Make sure to tare the cup's added weight out and the grams will show you MLS. Then take the amount the amount pumped in RAMPS units (it is the value in the script's name) and divide it by the grams of waters. This will give you the units/ml setting.

	== Volume to fill mixer ==		== Volume to fill mixer ==

@@ Line 13: / Line 13: @@
 == Determine RAMPS units to ml conversion factor ==
-RAMPs units to ml - There are many variables at play when determining how a RAMPs unit translates into a ML. The unit would be a mm on the 3d-printer. Instead of you trying to figure it all out and still not knowing if it is correct, we ask everyone calibrate their pumps. The doesn't actually calibrate the pumps but will determine constants which are then used to generate new specific gcode. If the pumps are not identical then we suggest you try on all 3 to verify they pump the same amount. If they are not the same then reach out to us on the forum or email. The current php script that generates the gcode does not handle pumps that vary amongst themselves.
+RAMPs units to ml - There are many variables at play when determining how a RAMPs unit translates into a ML. The unit would be a mm on the 3d-printer but is not specified in our device. We refer to it as a "RAMPS unit" Instead of you trying to figure it all out and still not knowing if it is correct, we ask everyone calibrate their pumps using a well documented straightforward process. The doesn't actually calibrate the pumps but will determine the constants used to generate new specific gcode.
 == Volume to fill mixer ==

@@ Line 8: / Line 8: @@
 == Determine max pump speed ==
-pumpmaxspeedtest.gcode - So this needs to be spooled in pronterface so the console can be observed. I didn't see a way to have printf type functionality in gcode so instead you will need to watch the console as it spools the command directly. When it starts to skip, make note of the last speed sent to the RAMPs board via the gcode. This is the absolute max speed of the pump but should be lowered again. It may be the case that the pump skips when there is more pigment than solution in the hose. This hasn't been tested but reduce it by 10% if keep lowering it until success.Try smaller batched at first.
+pumpmaxspeedtest.gcode - So this needs to be spooled in pronterface so the console can be observed. I didn't see a way to have printf type functionality in gcode so instead you will need to watch the console as it spools the command directly. When it starts to skip, make note of the last speed sent to the RAMPs board via the gcode. This is the absolute max speed of the pump but should be lowered again. It may be the case that the pump skips when there is more pigment than solution in the hose. This hasn't been tested but reduce it by 10% and keep lowering it until success. Try smaller batches at first.
-Alternatively would just be to create a series of files and count the number of beeps using the beepingspeedtest.gcode. This will require you to count the beeps yourself and note at what point it failed. Then multiple this beep number by 500 to know the speed at which is started to skip.
+Alternatively would just be to create a series of files by hand. Or count the number of beeps using the beepingspeedtest.gcode. This will require you to count the beeps yourself and note at what point it failed. Then multiple this beep number by 500 to know the speed at which is started to skip. -- DOUBLE CHECK
 == Determine RAMPS units to ml conversion factor ==

@@ Line 17: / Line 17: @@
 == Volume to fill mixer ==
 If the RAMP units to ml translation is correct then simply pouring water into your mixing container should suffice. You do not want this to be too large because it currently requires a slow mixing of the 2 ingredients and the larger the amount in each mix cycle then the longer the period of time during when the 2nd solution is mixed in. (The larger the mix amount, the longer it takes to pump in the 2nd solution, and therefore the further away from instantaneous mixing)
 [[Generating Gcode]]

← Older revision		Revision as of 08:06, 7 August 2024
Line 18:		Line 18:
	If the RAMP units to ml translation is correct then simply pouring water into your mixing container should suffice. You do not want this to be too large because it currently requires a slow mixing of the 2 ingredients and the larger the amount in each mix cycle then the longer the period of time during when the 2nd solution is mixed in. (The larger the mix amount, the longer it takes to pump in the 2nd solution, and therefore the further away from instantaneous mixing)		If the RAMP units to ml translation is correct then simply pouring water into your mixing container should suffice. You do not want this to be too large because it currently requires a slow mixing of the 2 ingredients and the larger the amount in each mix cycle then the longer the period of time during when the 2nd solution is mixed in. (The larger the mix amount, the longer it takes to pump in the 2nd solution, and therefore the further away from instantaneous mixing)

−	== Generating Gcode ==	+	[[Generating Gcode]]