Homeroasters - Home Roasting Coffee Community » ALL ABOUT ROASTERS » ROASTING SOFTWARE APPS
Who is here? 1 guest(s)
 Print Thread
Artisan Fan Slider Calibration
sahstim001
Top  #1 Print Post
Posted on 03/12/2023 12:00 AM
I'm trying to calibrate a slider in Artisan to only allow useful fan speeds. My DC fan isn't too happy below 50% PWM. What I'd like to do is have a "deadzone", where 0%=off, 1%=50%, and 100%=100%. Essentially, jump from completely off to 50%.

I can see how using offset=50 and factor=0.5 I can get 0%=50% and 100%=100%, but then it's not possible to turn off the fan.

Is there a way to do what I'm looking for?
 
renatoa
Top  #2 Print Post
Posted on 03/12/2023 3:31 AM
What about adding a button for 0% ?
 
sahstim001
Top  #3 Print Post
Posted on 03/12/2023 7:42 AM

Quote

renatoa wrote:

What about adding a button for 0% ?


That might work as an alternative. I'd prefer if there was a solution on the slider just to keep the controls all in one place, but if not the button would be an acceptable solution.

Is what I'm looking for just not possible?
 
renatoa
Top  #4 Print Post
Posted on 03/12/2023 8:33 AM
How should look a hypothetical user interface element, to suit your needs ?
So you want a slider with the first half hidden/compressed, having active the second half, from 50 to 100, but also the zero choice... how do you want to access the zero value via the slider, if a button is not so ok ? pull the cursor out of slider boundaries ? Tick a checkbox? Or via a keyboard shortcut ?
Asking because I want to figure how you see the modus operandi of such scenario.

As a programmer, in a custom application I know how to design such control as you want, in multiple ways, but Artisan is not a design environment, just an application you use as is.
 
sahstim001
Top  #5 Print Post
Posted on 03/12/2023 9:43 AM
To control it all from the slider, this is how it would function from a programming perspective:

if slider = 0
then fan = 0
else fan = ( slider x 0.5 ) + 50

I understand artisan may not be capable of this, but I'm still learning what it can do so I wasn't sure.
 
renatoa
Top  #6 Print Post
Posted on 03/12/2023 11:22 AM
I didn't meant programming as code, but as user interface.
Not only Artisan but in any other known application, how do you see this interaction done?
 
sahstim001
Top  #7 Print Post
Posted on 03/12/2023 12:36 PM

Quote

renatoa wrote:

I didn't meant programming as code, but as user interface.
Not only Artisan but in any other known application, how do you see this interaction done?


The interface would be just the slider. No buttons. The fan would suddenly drop all the way to zero when the slider is at the bottom.

It would be analogous to a light dimmer where the slider clicks when it reaches the bottom.
Edited by sahstim001 on 03/12/2023 1:30 PM
 
renatoa
Top  #8 Print Post
Posted on 03/13/2023 4:26 AM
Excellent analogy with the dimmer... but... the catch is in the "clicks" part.
In real world a slider is a potentiometer, which usually don't do clicks at one of the ends. As no slider clicks, in any programming environment known by me.
However, in real world there are special pots who do clicks, by adding a switch on top of the pot... the black part in the foreground of the pot, see attached image.
The rotation range of such pot is reduced by some 45 degrees angle, to save that range for switch actuation. Click !
So the switch is an addition... not integral part of the pot/slider.
So should be in Artisan too, a button for fan off.
The hard part is that you want them both handled by same knob, as the real world dimmer Shock
We can't have all... Grin
renatoa attached the following image:
image_2023-03-13_112039774.png
 
randytsuch
Top  #9 Print Post
Posted on 03/13/2023 7:27 AM
You may want to ask on the artisan github discussion page
https://github.co...iscussions
 
sahstim001
Top  #10 Print Post
Posted on 03/13/2023 9:47 AM

Quote

renatoa wrote:

Excellent analogy with the dimmer... but... the catch is in the "clicks" part.
So the switch is an addition... not integral part of the pot/slider.
So should be in Artisan too, a button for fan off.
The hard part is that you want them both handled by same knob, as the real world dimmer Shock
We. can't have all... Grin


Yes, that's why I sent the program logic. The "if" statement would be the "click". But if artisan cannot have a program like this embedded in the slider then it is what it is.
 
sahstim001
Top  #11 Print Post
Posted on 03/13/2023 9:47 AM

Quote

randytsuch wrote:

You may want to ask on the artisan github discussion page
https://github.co...iscussions


I'll have a look over there. Thanks!
 
sahstim001
Top  #12 Print Post
Posted on 03/13/2023 8:17 PM
Here's another idea... Could this be done on the Arduino side? I'm using a TC4+ with aArtisanQ_PID. Could this be coded into the Arduino sketch? I'm sure it could, right?

EDIT:
Is that what this section of code would do? If I edit the MIN to 50? It seems that 0 will still be available, based on the comment text.
sahstim001 attached the following image:
screenshot_2.jpg
Edited by sahstim001 on 03/13/2023 8:30 PM
 
renatoa
Top  #13 Print Post
Posted on 03/14/2023 5:16 AM
Actually this is a brilliant idea, if you perform a small change in the code section handling IO3 command, that will make TC4 behave exactly how you want.
In this moment, if you send to TC4 a IO3 command with any parameter the MIN/MAX limits from user.h are ignored, which actually this IS a bug, I hope @greencardican is reading here Grin
The MIN/MAX limits are used only for IO3;UP and IO3;DOWN commands, should be added also for IO3;xxx.
This is what you can do to make the slider behave as you want.

On TC4 side: change MIN_IO3 to 50, then copy this line: https://github.co...r.cpp#L366
... from IO3;DOWN command, to IO3;ddd command, in this place:
https://github.co...r.cpp#L378
... just above the outIO3(); statement, to add same protection for the IO3;value command, as for IO3;DOWN.
Protection that in actual code is lacking, warning again: someone can send any value as parameter of IO3 command, and will be executed without limits!
Then reload TC4 code with the changes above.

Artisan side: program a slider with the 49-100 limits.
When you hit the slider bottom, i.e. 49 value, the actual command sent to fan will be zero, i.e. cut-off. Job done !
Edited by renatoa on 03/15/2023 3:17 AM
 
sahstim001
Top  #14 Print Post
Posted on 03/14/2023 11:52 PM
Nice! I'll check it out and post the results here.

Secondary question while I'm at it... I see another piece of code a bit further down on user.h to define HTR_CUTOFF_FAN_VAL. It appears this is a safety against having the heater on without the fan running. Is this piece of code working?
 
renatoa
Top  #15 Print Post
Posted on 03/15/2023 6:57 AM
Yes, it's working, and is mandatory for machines of fluid bed type, or any other where leaving the heater without a minimal airflow led to overheating and burning.
 
sahstim001
Top  #16 Print Post
Posted on 03/15/2023 6:33 PM

Quote

renatoa wrote:

This is what you can do to make the slider behave as you want.

On TC4 side: change MIN_IO3 to 50, then copy this line: https://github.co...r.cpp#L366
... from IO3;DOWN command, to IO3;ddd command, in this place:
https://github.co...r.cpp#L378
... just above the outIO3(); statement, to add same protection for the IO3;value command, as for IO3;DOWN.


Hmmm, I must be using a different version of aArtisanQ_PID than you reference... I'm using version 6.3. It looks like that code you reference is 1.10.

I can't find that piece of code on the new version. Any idea where it is? Thanks so much for your help!
 
renatoa
Top  #17 Print Post
Posted on 03/16/2023 2:57 AM
Search cmndreader.cpp, io3Cmnd section, 25 lines from section start is DOWN command statement that performs the MIN_IO3 check.

Code Download source  

      if( levelIO3 < MIN_IO3 & levelIO3 != 0 ) levelIO3 = 0; // turn IO3 off if trying to go below minimum.


Copy that line 10 lines below, between these two:
Code Download source  

        levelIO3 = atoi( pars->paramStr(1) );

          outIO3();
 
sahstim001
Top  #18 Print Post
Posted on 03/16/2023 7:50 AM
Done! It works exactly as intended. Thank you so much for your patient help!
 
greencardigan
Top  #19 Print Post
Posted on 03/27/2023 5:17 PM

Quote

renatoa wrote:

In this moment, if you send to TC4 a IO3 command with any parameter the MIN/MAX limits from user.h are ignored, which actually this IS a bug, I hope @greencardican is reading here Grin
The MIN/MAX limits are used only for IO3;UP and IO3;DOWN commands, should be added also for IO3;xxx.


greenman

I can't think of any reason why the min max check would have been excluded from the io3;xxx command, so a bug it is.
 
Jump to Forum: