Skip to main content

Fixing heated bed

Today I set about fixing the issue with my heated bed.
Using a multimeter to test the thermistor that came pre-installed showed it was dead so I snipped it out and soldered in a replacement.
In Pronterface I could see that it was connected, but it was reading -15C. The room is cool but not that cool.
The new thermistor is "100K ohm NTC 3950 1% 1.8mm" and after a bit of googling I found it was a type 11.
I edited my "configuration.h" file and set "#define TEMP_SENSOR_BED 11". After uploading Marlin; Pronterface was now reading a temperature of 16C.
I was able to change the bed temperature from the LCD to 20C and watched as it warmed up. I checked it was warm (carefully with my hand) and then increased it to 60C. 
So another job done.
Next will be to fix the connector on the hotend thermistor and get that working:
For now though, it's starting to look good:




Comments

Popular posts from this blog

Discord Gateway for MQTT

I have created a new organisation  on Github today as a place to add automation scripts and the first one I will add is a gateway for Discord. This core of this script was originally created when I needed to send crash alerts from an application I had written to my phone so that could act upon them quickly. This proved useful and I added it to additional scripts and applications, but found that it was a bit limited if I wanted the alert to be logged elsewhere so I updated my apps and scripts to send to MQTT. Once my alerts were in MQTT I could pick them up from NodeRed and perform various actions; but I missed having them arrive in Discord, so last night I created an MQTT-2-DISCORD module that includes  support for multiple discord channels. Installation is fairly simple and I have documented the process in the README.md file associated with the repository. After installation, visit Discord and obtain a webhook for the channel you want to recieve messages into. You can name the webhoo

LSP templates

I took a step back with my LSP and decided that what I really need is a template based system for building responses. Previously I had started creating the JSON on the fly but realised that the jsonrpc specification has what it called interfaces which are basically templates, so I wrote a Type that allows you to add templates and variables and then it joins them all together for you. It works well but I might find a better way at some later time. After getting the template system working and removing some debug messages that I think might be inadvertently picked up as responses. For reference, the LSP receives an "initialise" message from the client that contains a lot of data. In my case it was over 4k in size. The LSP then returns an "initialized" message and receives confirmation from the client in the form of an "initialized" notification. The "initialize" and "initialized" messages are very similar. Both contain "jsonrpc"

Wednesday morning!

I've not posted in a while.  I guess I'm not really used to telling the world about my life... must get better at that! Since my last post,  I have upgraded the disk and RAM on my laptop and installed Linux Mint 19.3 and found it handles my external monitor much better than the previous release.  While restoring my data and having a clear out I stumbled on a couple of unfinished projects that I really should complete, but more about that later.