Question about multiple heightmaps

JamesM

I read that you can use G29 S3 to save different name heightmaps but it doesn't say if that command will also probe the bed to create the mesh heightmap.

I just switched one of my printers to the DC42 ir probe and it's working well but now I need to create different heightmaps due to how it senses different material beds like a textured PEI sheet. I got a new cast bed with high strength magnets embedded in it which didn't work well with my bltouch (yes, the plastic tipped one was still affected).

Thanks for any help/answers.

fcwilt

@jamesm

It's easy enough to create and load different height maps.

The question is are you ok with doing it "manually" via macros or would you like something more elegant and "automatic".

With firmware 3.3.0 you have access to variables which can make doing this easier.

Frederick

o_lampe

@jamesm
to me it seems, you have to probe the bed with S0 and then use S3 P"name.csv" to store it under a new name.
Question is, if a removable bed surface needs it's own heightmap (not just an offset) ; how can you make sure it's at the same place next print? (read: is the heightmap still valid?)

fcwilt

@o_lampe said in Question about multiple heightmaps:

Question is, if a removable bed surface needs it's own heightmap (not just an offset) ; how can you make sure it's at the same place next print?

Do you mean it is placed back in the printer at the same exact location each time?

If so I have the BuildTak system and have not found that to be a problem.

I try to put it back each time in the same place but it's not perfect.

Frederick

dc42

@o_lampe said in Question about multiple heightmaps:

to me it seems, you have to probe the bed with S0 and then use S3 P"name.csv" to store it under a new name.

Correct. Send G29 S0 to probe the bed and save it as heightmap.csv. Then either rename it within DWC, or save it again under a new name using e.g. G29 S3 P"myNewHeightMap.csv".

JamesM

@fcwilt I'm on 2.05 firmware and I plan on just putting the command in the start code in my slicer to choose which heightmap I load. I make different printer profiles based on nozzle size already so I'll just add extra ones based on the build sheet I'm using for each print.

I've been to chicken to upgrade to 3.x firmware and relearn all the config stuff..LOL.

JamesM

@dc42 @o_lampe Gotcha.

Positioning the removable build sheets is easy and I'm not worried about getting them lined up.

Thanks.

fcwilt

@jamesm said in Question about multiple heightmaps:

I've been to chicken to upgrade to 3.x firmware and relearn all the config stuff..LOL.

I put off upgrading but as I read about what was needed I went ahead.

It was easier than I thought with just a few changes needed.

I am VERY glad I did - I suggest you do the same - I would be glad to help.

Frederick

JamesM

@fcwilt Maybe I'll give it a shot tonight. If I want to downgrade back to 2.05 how difficult is it? Can I simply just have two different SD cards and swap it back or will uploading 2.05 through DWC do it?

DIY-O-Sphere

@jamesm said in Question about multiple heightmaps:

I've been to chicken to upgrade to 3.x firmware

Nowerdays the config tool is doing the job quite well.
Be a brave chicken...

DIY-O-Sphere

@jamesm
To update to RRF3.3 you first have to go to RRF3.0.
It's good to have the old files on the backup sd card and have a clean install.
If you have some patience until we have solved eventually problems, downgrade is not an option.

DIY-O-Sphere

@JamesM :

downgrade is not an option.

All joking aside, you can do this by uploading the zip file of the old version. Then restore the old files or in your case swap the card.

fcwilt

@jamesm said in Question about multiple heightmaps:

@fcwilt Maybe I'll give it a shot tonight. If I want to downgrade back to 2.05 how difficult is it? Can I simply just have two different SD cards and swap it back or will uploading 2.05 through DWC do it?

I was able to downgrade from one v3 release to another but I never tried to downgrade to a v2 release - I never wanted to - you won't either.

If you want to ZIP up all the files in your v2 system folder and post it here (add .txt to the existing .zip extension first) I will take a look. I might be able to quickly convert them for you.

Frederick

JamesM

@fcwilt I have made backups of the files already. I do that whenever I make changes and I zip them all using DWC and save them on my network drive. I'm actually making a full copy of the SD card right now to another SD card I have and then will start the upgrade process loading 3.0 and then 3.3 from what I read.

Then I need to set up my triple z files and whatnot after the upgrade.

Fingers crossed this goes smooth but I honestly don't think I'll see any benefit from 3.x since I don't plan on using any of the crazy new features. I'll do it anyway just to be current and then if it goes smoothly I can do it to my other 2 printers.

fcwilt

@jamesm

Good.

I think you be happy.

If you need help don't hesitate to ask.

Frederick

JamesM

@fcwilt Welp....how I did the config on the reprap configurator messed it up and now I can't connect. I picked a static ip address and after I uploaded everything and rebooted it now I can't connect. Time to bust out my laptop and connect to it via usb and try to get the wifi back on DHCP so I can connect.

New laptop too so I don't have YAT on it at the moment.

UGH.

fcwilt

@jamesm said in Question about multiple heightmaps:

@fcwilt Welp....how I did the config on the reprap configurator messed it up and now I can't connect. I picked a static ip address and after I uploaded everything and rebooted it now I can't connect. Time to bust out my laptop and connect to it via usb and try to get the wifi back on DHCP so I can connect.

New laptop too so I don't have YAT on it at the moment.

UGH.

Sorry to hear that. But if you know how to connect via USB you should be fine.

Did you use that tool to create a new configuration from scratch? Most of your old config was useable.

The biggest change I recall was having to create named pins (v2 had a fixed set names pins) using M950. The other commands that needed to reference to the pin then used a number that was assigned to the pin in M950.

There was a change in the way heater tuning was done but the process was the same.

I'm here.

Frederick

JamesM

@fcwilt I was just about to ask about that. I have a thermistor that I use to monitor chamber temps in my printer and wondered how the heck I set that up.

I'm using the thermistor that is normally for E1 for that.

My old line was M305 S"Chamber temp" P103 T100000 B3988 C0 X2

What I'm reading is that I now have to create a virtual heater first using M950 and this is where I'm getting confused.

Do I make a line like M950 H2 "Chamber temp" and then make my line M308 S2 P"e1temp" Y"thermistor" T100000 B3950 ???

fcwilt

@jamesm

Here is the part of a config.g file from one of my printers that deals with heaters:

; ****************************************************************************************************
; heaters
; ****************************************************************************************************

M308 S0 P"bedtemp" Y"thermistor" T100000 B4138             ; configure sensor 0 as thermistor
M950 H0 C"bedheat" T0 Q10                                  ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 A107.3 C136.0 D2.8 V12.0                  ; values A, C, D, V determined by running heater tuning
M140 H0                                                    ; map heated bed to heater 0
M143 H0 S115                                               ; set temperature limit for heater 0

M308 S1 P"e0temp" Y"thermistor" T500000 B4723 C1.196220e-7 ; configure sensor 1 as thermistor (SLICE)
M950 H1 C"e0heat" T1 Q250                                  ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 A362.4 C121.7 D4.4 V11.8                  ; values A, C, D, V determined by running heater tuning
M143 H1 S250                                               ; set temperature limit for heater 1

JamesM

@fcwilt I managed to get it working. Took me a bit to figure out what I screwed up for homing the y-axis but I had forgot to tell it home high in the configurator and had to change that setting and in the homey and homeall files.

Now to check everything on it to make sure it works ok and do a test print.

Thanks for your patience and willingness to help me.