There's a fairly simple host protocol used in Bluetooth called BCSP that would be very easy to port across. It handles lost packets, stalls and re-transmits. Regards, Jamesby jim_blag - Firmware - experimental, borrowed, and future
You'll need to install Python to run the Skeinforge.py application. Download and install Active Python and you should be good to go. JBby jim_blag - General Mendel Topics
You'll definitely want to use Skeinforge to generate your GCode. Use the Multiply feature in Skeinforge to set the position on the bed. JBby jim_blag - General
Gen6 doesn't work with RepRap Host. It sends messages that are in a subtly different format and RepRap Host can't decipher them as being correct. You'll need to stick with RepSnapper. JBby jim_blag - General
Very neat. I like the filament joiner. JBby jim_blag - Skeinforge
It's a bit of both. If you are using SF40+, E_STEPS_PER_MM needs to be set to the number of steps required to push 1mm of filament into the extruder. There are various techniques to doing this, but I prefer marking 110mm up from the extruder on the filament and running 100mm into the extruder slowly via RepSnapper. Then you can calculate how much filament actually went into the extruder and scalby jim_blag - General
Is it on every thread or just at the end of the print? JBby jim_blag - Skeinforge
Congratulations! Looks like there is hope for your printer yet. You probably want to play with the retraction settings, you've got some stringing going on. Since you've got a bowden cable you might need to set them quite high. Retraction is in the dimension tab, I wouldn't suggest using Oozebane. You may also want to play with first layer height and speed to get good adhesion. Look in bottom anby jim_blag - General
I haven't got Repsnapper working. I have verified that the values being returned from the Teacup firmware are correct using portmon. It purely seems to be a problem with Repsnapper interpreting the response. I have noticed that when it does get around to displaying a result it is 8 values old, making me suspect the command buffering code in RepSnapper is slightly screwy. I haven't looked througby jim_blag - General Mendel Topics
I'm not familiar with your electronics, but is the current setting for the Z-Stepper set correctly? If there isn't enough current then the motor won't turn if it has a heavy load (as with the Z-axis). There should be some trim-pots somewhere on your board that you can adjust. JBby jim_blag - Reprappers
Just saw this thread resurface, and I thought I'd update how things are going with my Gen6 and Teacup. I've been running a bunch of Skinning test prints with Teacup. It took a bit of tweaking but I'm getting really clean prints now. No blobbing, no pausing and with the skin algorithm very smooth external surfaces. I'm playing with the acceleration settings to help close the external surfaces fulby jim_blag - General Mendel Topics
Have you updated the E_STEPS_PER_MM value in your firmware? In SF40+ this value needs to detail how many steps it takes to feed in 1mm of filament to the extruder. Prior to SF40+ it detailed how many steps it took to extrude 1mm of filament from the extruder. That might explain why your object is rather sparse. There are several good posts of the forum for configuring SF40+. JBby jim_blag - General
I just pulled version e05e12c and tested it. Unfortunately, it still hangs with M101 commands on my Gen6. JBby jim_blag - Firmware - experimental, borrowed, and future
I'll pull it and test it tonight. JBby jim_blag - Firmware - experimental, borrowed, and future
The problem occurs with Send.py. I can't use RepSnapper to print, I just use it to keep the temperature on the extruder stable between prints, since Send.py shuts down the extruder when it completes. The issue is definitely in the Teacup firmware. If it is checking the extruder temperature prior to an M101 command (not sure why, it doesn't do it for a M103 command - possibly because it is goingby jim_blag - Firmware - experimental, borrowed, and future
I've figured it out. When it gets round to processing the M101 command in 'gcode_process.c', it performs this check on temperature first: if (temp_achieved() == 0) { enqueue(NULL); } Not sure why it thinks the extruder is not up to temperature yet as it has been at the correct temperature for an age, but it might be to do with prepping it in RepSnapper, then switching to Send.py fby jim_blag - Firmware - experimental, borrowed, and future
Extruder speed settings appear to be fine for all other movements. I've set the Start/Stop value to 500 steps (to match the 1.2mm I was using with Skeinforge). Interestingly, I've found that the M103 commands work for retraction, it's only the M101 commands that cause the thing to hang. I've also found that if I run in Absolute mode the M103 retracts then instantly returns to where it was befoby jim_blag - Firmware - experimental, borrowed, and future
Thanks Sublime, I switched version, but still no joy. It still hangs on the first M101 command. JBby jim_blag - Firmware - experimental, borrowed, and future
I'm also having trouble with retraction in Teacup. Initially I had the M101 and M103 commands commented out in my GCode, but it would appear that these are necessary to the retraction detection. However, when I uncomment them in the GCode my Mendel just hangs at the first M101. Any suggestions? I'm running version b39a7b8 Thanks, Jamesby jim_blag - Firmware - experimental, borrowed, and future
A Portmon trace of the Serial comms shows that Teacup is returning the correct values, but oddly, RepSnapper M105 response works with Sprinter FW though. I'm not sure I understand why that is. JBby jim_blag - Firmware - experimental, borrowed, and future
I was explaining my Mendel to a friend today, he promptly sent me this article asking if this is what I was doing. Not sure what to make of the comment. http://gizmodo.com/5809662/bikinis-made-from-3d+printers-are-custom-fit-for-each-womans-curve/gallery/1 JBby jim_blag - General
OK, I have been playing with Teacup this evening. After some tweaking of settings I have nearly as good prints as I was getting with the original firmware on the Gen6 without any of the little blobs. With a little more tweaking I'm sure it will be even better than before. Interestingly, the printer runs faster than before (which does point towards the old firmware running out of MIPS) and the exby jim_blag - General Mendel Topics
You could try increasing the baud rate, however I don't think that is the source of the problem. There is a 4-command buffer on the hardware, so it shouldn't be running out of commands so quickly, even at 19200. A 25-byte command will be sent in 13ms. The problem is caused by the UART ISR not getting serviced when making fast (or short) moves as the main move ISR consumes all the processor resouby jim_blag - General Mendel Topics
@Triffid_Hunter: Quick question about G161. It's not listed on the RepRap GCodes page, but based on the comments in the code I get the general gist of what it is supposed to do. However, when I send the command the axis moves away from the Min Endstop. If I nudge the axis in the positive direction, it moves away from the endstop, and towards it if I nudge it in a negative direction. So the motorby jim_blag - Firmware - experimental, borrowed, and future
Thanks for the help on this everyone. I've got it all up and running and printing. Still needs a bit of tuning. However, the current version of RepSnapper appears to have taken some serious steps backwards since v352 (the one I typically use, but won't work with Teacup). It won't print without me kicking it a few times every layer plus the temp issues. I've switched to RepRap Host and can printby jim_blag - Firmware - experimental, borrowed, and future
Has anyone got Teacup running on Gen6 hardware? I've been trying to get it up and running this afternoon. I'm using the Config file for Gen6, which appears to have everything configured correctly. I've tweaked the ThermistorTable to use the actual values (x4) from my Gen6 default FW, but I am having several problems. * With the latest RepSnapper I don't get reliable temperature readings (e.g. swby jim_blag - Firmware - experimental, borrowed, and future
Setting retract to 0 (and the additional restart value to 0) will disable retract. It will be interesting to see if your longer belt-mod has helped this out. I've been distracted by skinning tests and the associated Skeinforge plug-in, plus a two-week business trip, so haven't had much time to look at this. However, while I was in China I stopped by the Seed Studio office and picked up their opeby jim_blag - General Mendel Topics
I created a simple application to map the flatness of the bed. I'm just finishing of tweaking it before I publish it, I'll put it up on this Wiki page once it's done. It really helped me get a level surface. Bed Mapping Regards, Jamesby jim_blag - General
I would suggest tidying up the holes as best you can with a scalpel. Then push the nuts in as far as you can. Then using a shorter bolt and some washers, tighten the bolt until it pulls the nut in to the recess. Then remove the bolt and continue assembly as normal. JBby jim_blag - General
I've updated the Wiki to reflect the various versions and the shipping dates. JBby jim_blag - General