Show all posts by user
Page 1 of 1 Pages: 1
Results 1 — 20 of 20
It would have been easier to debug this problem if I had found and enabled
#define DEBUG_LEVELING_FEATURE
by
jtrantow
-
Firmware - Marlin
Some digging into the code revealed my probing problem.
I home to Z_MAX and since I'm still adjusting the Z hardware my nozzle was touching at [8.5 - 9.0] mm. This is outside the tolerance.
#define Z_PROBE_ERROR_TOLERANCE 3 // (mm) Tolerance for early trigger (<= -probe.offset.z + ZPET)
This can be fixed by:
Increasing Z_PROBE_ERROR_TOLERANCE (hack) Decreasing Z_MAX_POS to be closer t
by
jtrantow
-
Firmware - Marlin
I reworked my printer to include a nano connected to a HX711 and strain gauge. Printer is running Marlin bugfix on a SKR1.4 board. The nano provides a TRIGGERED output and a TRIGGER_ENABLE that connect to Zmin and Probe pins.
I modified Configuration.h with the following:
(Probe)
#define NOZZLE_AS_PROBE
#define NOZZLE_TO_PROBE_OFFSET { 0, 0, 0 }
#define PROBE_ENABLE_DISABLE
#define DELAY_BEFOR
by
jtrantow
-
Firmware - Marlin
I found that if I jog the z axis with Pronterface before I print, the z axis will move correctly. If I don't jog, the z axis moves a fraction (about 1/2) of what I want it to do. I'm not sure what's causing this, but this kludge works for me.
by
jtrantow
-
Firmware - mainstream and related support
I'm running Marlin firmware with the Pronterface frontend on custom CNC hardware. I have had a bunch of problems with homing in my G-code initialization that just didn't seem correct. I finally gave up using an initial sequence and instead use a combination of a home move and Pronterface jog commands to get to the desired z initial position, I use a G92 command in my initial Gcode to set the ori
by
jtrantow
-
Firmware - mainstream and related support
What firmware are you using? These chips need a longer step pulse than some firmware provides. Teacup works. Marlin needs to be modified. Not sure about the others.
by
jtrantow
-
Controllers
If you are using a max6675 TC, search through the issues for a fix I posted. I was having all sorts of firmware lockups until I removed an unnecessary delay from read_max6675(). read_max6675() is called from an interrupt and having an extra 1msec delay every 250msec can cause all sorts of problems that are difficult to identify. Once, I fixed this issue I have successfully completed over 50 p
by
jtrantow
-
Slic3r
I am using the three axis board of this family. I bought the 3 axis thinking it would be nicer to have two three axis boards than be limited to 4 or 5 axis. I'm using a pololu board to temporarily drive an extruder. The biggest problem I have with this board is that it requires a longer step pulse (30usec?) than the 1usec needed by the Pololu A4988 drivers. The TeaCup firmware already has a l
by
jtrantow
-
Controllers
I ran into this problem with a TB6560AHQ based board. I measured 60usec using Teacup and 1.4usec using Marlin.
The TB6560AHQ datasheet says in needs 30usec with a 330pF cap to set the timing. I'm not sure what frequency my TB6550AHQ is running at but this sure explains the wierd things I have been seeing.
My post is has scope pictures.
by
jtrantow
-
Firmware - experimental, borrowed, and future
I'm having the same problem. Works with Teacup (60usec pulse width) but not with Marlin (1.4usec).
The TB6560AHQ datasheet specifies 30usec for 330pF. I'm not sure what capacitor is on my boards.
by
jtrantow
-
Repetier
Ok, I pulled out the scope. scope_9.bmp shows the X step, direction, and enable pins for a 0.1mm move using the Teacup firmware. (works)
Green=step, yellow=dir, blue=enable. This gives exactly what I expect. 125984 steps/m for a 0.1mm move equals 12.5984 steps. This plot shows 12 steps, subsequent moves show 13, and the average should be 12.5984. Also notice, the steps in the center are clos
by
jtrantow
-
Firmware - mainstream and related support
I have #define DISABLE_MAX_ENDSTOPS and
#define X_MIN_PIN -1 //!< X axis Minimum limit pin.
#define Y_MIN_PIN -1 //!< Y axis Minimum limit.
#define Z_MIN_PIN -1 //!< Z axis Minimum limit pin.
#define X_MAX_PIN -1 //!< X axis Maximum limit pin.
#define Y_MAX_PIN -1 //!< Y axis Maximum limit.
#define Z_MAX_PIN -1 //!< Z axis Maximum l
by
jtrantow
-
Firmware - mainstream and related support
Found part of the problem. My XYZ use enable high so I needed:
#define X_ENABLE_ON (1)
#define Y_ENABLE_ON (1)
#define Z_ENABLE_ON (1)
#define E_ENABLE_ON (0) // For all extruders.
Now my Z axis started working. However, my X and Y get enabled but don't move as expected. Loading the Teacup firmware confirms that the hardware and electronics still move the machine as desired. I copied my X,Y
by
jtrantow
-
Firmware - mainstream and related support
I'm trying to port my Teacup configuration over to the Marlin firmware. I'm using custom hardware and electronics with a Mega2560 and max6675 temp 0 sensor. I had a little problem with the files in the ErikZalm-Marlin-ffea800.zip still having a bug in the MAX6675 code which gave out of range temp values. Looks like this problem has been fixed but not in the zipped files.
While I was having te
by
jtrantow
-
Firmware - mainstream and related support
slic3r 0.7.1 has a "Use relative E distances" setting. What I meant was when this box is checked, slic4r still generates the G92 E0. From the comment in config.h I thought I wouldn't see the G92 command with absolute extrusion distances. I guess with absolute you will only see this once while with relative you will see many???
I'm currently using relative (unchecked box in slic3r and comment
by
jtrantow
-
Firmware - mainstream and related support
Thanks, getting absolute/relative extrusion correct straightened out the excess extrusion. Just a note, the config.h has:
/** \def E_ABSOLUTE
Some G-Code creators produce relative length commands for the extruder, others absolute ones. G-Code using absolute lengths can be recognized when there are G92 E0 commands from time to time. If you have G92 E0 in your G-Code, define this flag.
*/
#define
by
jtrantow
-
Firmware - mainstream and related support
Thanks for the advice, Pronterface and Slic3r seem to make more sense and I'm making progress. The first few layers come out ok but I must be extruding too much PLA and the nozzle starts plowing through. The default slic3r config was set up for 3mm filament and I'm using 1.8mm. So it looks like I need to tackle more of the settings.
I have the Printer G-code flavor set to Teacup, but I still
by
jtrantow
-
Firmware - mainstream and related support
Thanks for the reply. I think I understand how Teacup simply takes gcode, but I'm not clear on how information in ReplicatorG machine.xml changes the generated gcode. (And the requirements on machine.xml matching the firmware.) After a bunch of frustration, I think what I need is to edit a skeinforge profile to match my machine. My XYZ already look good, so I think it's just a matter of getti
by
jtrantow
-
Firmware - mainstream and related support
I'm having some problems getting a custom machine up and running. Using the ReplicatorG control panel, I can accurately move the extruder around in 3D space, control the heater temperature and extrude. However, I am having a bunch of problems calibrating the MK7.
I thought it would be easy to find STEPS_PER_M_E, MAXIMUM_FEEDRATE_E, and E_STARTSTOP_STEPS for a MK7 and I'd be printing. Howeve
by
jtrantow
-
Firmware - mainstream and related support
Has anyone figured out how to use multiple MAX6675 sensors with the Teacup firmware?
Looking at file temp.c, line 139, in the TT_MAX6675 switch case the current code uses WRITE(SS, 0) to enable the SPI slave select. Since Slave Select is defined to the default SS (either DIO10 or DIO53) it doesn't appear that multiple SPI devices are supported.
I'm still trying to figure out how the DEFINE_TEM
by
jtrantow
-
Firmware - experimental, borrowed, and future
- 13 years ago