Automatic Control and User Interface for Central Tire Inflation System

[marvin7]

Yup! Happened to me lately, now your turn

[Eyberg]

OK
but this returns me values from Blynk Slider the correct place in the calculation program and then returning to Blynk lcd

[Eyberg]

How do I use this with LCD Advanced Mode

Formatting options
Let’s assume, your sensor sends number 12.6789 to Blynk application. Next formatting options supported:
/pin/ - displays the value without formatting (12.6789)
/pin./ - displays the value without decimal part (13)
/pin.#/ - displays the value with 1 decimal digit (12.7)
/pin.##/ - displays the value with two decimal places (12.68)

[Gunner]

@Eyberg

How do I use this with LCD Advanced Mode

Check out this link where I answer that question with a short example:

[Question] LCD Widget Connections

Hello, is it possible for the LCD widget display the same thing with the Physical LCD? Can you show some example to do it and how the connection?

[Eyberg]

@Gunner

Check out this link where I answer that question with a short example:

so this is not possible

[Gunner]

@Eyberg

so this is not possible

What is not possible…? Sorry guess I didn’t understand the original question.

[Eyberg]

@Gunner

What is not possible…? Sorry guess i didn’t understand the original question.

Is this possible with LCD Advanced Mode ?
displays the value with 1 decimal digit (12.7)

[marvin7]

the formatting strings (#.##) are for simple mode. In advanced mode all formatting is done in device’s code. There is no user interface element in app to do it in advanced mode, so it’s straightforward that it cannot be done this way. But formatting in device is as simple as using function
Str = String(float_value,decimal_points)

Analyze this piece of code:

String V_LCD_row0 = "IN: ";
if (Tc_in >= 0) V_LCD_row0 += " ";
V_LCD_row0 += String(Tc_in, 1);
V_LCD_row0 += rh_str;
V_LCD_row0 += String(Rh_in, 0);
V_LCD_row0 += "%";

String V_LCD_row1 = "OUT:";
if (Tc_out >= 0) V_LCD_row1 += " ";
V_LCD_row1 += String(Tc_out, 1);
V_LCD_row1 += rh_str;
V_LCD_row1 += String(Rh_out, 0);
V_LCD_row1 += "%";

Virtual_lcd.print(0, 0, V_LCD_row0);
Virtual_lcd.print(0, 1, V_LCD_row1);

Also strongly suggesting digging a little into basics at given Arduino reference page, where String() function is explained among other useful stuff

[Eyberg]

@marvin7
this comes to me slowly with me and is always more to learn and understand this

Has just been here for 10 days and is going on the course after 20 days, I am now satisfied what I’ve done with your help here

The next step is to write to explain; what’s what in the code, so to bring it together and finish this connect in offroad jeep to see functionality

But thanks for your help

[Gunner]

This sounds like a very big endeavor to start with, but I see that you are definitely working hard on it… However, I would recommend that on your first trip, you bring along a manual tire pump, just in case

[Eyberg]

it would still be great to get some help or good eyes to see how I fix this, you are so cool to see immediately what you can do[quote=“Eyberg, post:59, topic:12034”]
Found a solution to this problem Before

Eyberg:
setPoint = newSetPoint;

= missing or ?Now and works

Eyberg:
setPoint == newSetPoint;
[/quote]

[marvin7]

@Gunner

I would recommend that on your first trip, you bring along a manual tire pump, just in case

he, he… good point, @Gunner! But seriously speaking, if @Eyberg will make it to build on his own, then he will definitely will know what wires to short for emergency inflating!

[Gunner]

@marvin7

what wires to short for emergency inflating!

And more importantly… when to let go of said wires

[Eyberg]

@Gunner
@marvin7

you would love to come along for the ride on a glacier like this last year
You should see lines of approximately the tires are 38 "but these are manual equipment controlled by valves that are manual
https://www.youtube.com/watch?v=PyYJYC41QUc&t=8s

[marvin7]

Yeah… a free and open world, hard to find on mainland Europe… If one day I will be bored with spending summer on the beach, perhaps will choose Iceland to visit…(or emigrate )

Not always safe, though:

[Eyberg]

@marvin7

Not always safe, though:

It’s true

I disable this out and then it works
setPoint = newSetPoint;

[marvin7]

To be honest, I do not know what works and what not.
To summarise:

1. You plan to keep the pot for manual setting?
2. if not, then you don’t need the whole function, as the setPoint var can be set (only) by means of slider from APP, and this is done by VIRTUAL_WRITE function, presented in prev. post.
3. If Yes, then the whole thing will be a bit more complicated (but not that much) to keep in sync both settings (although the pot can be used then, it is not recommended)

So?

[Eyberg]

Ok ?

@marvin7

1. You plan to keep the pot for manual setting?
   No
2. if not, then you don’t need the whole function, as the setPoint var can be set (only) by means of slider from APP, and this is done by VIRTUAL_WRITE function, presented in prev. post.
   must have SetPoint because it controls psi set the deflation or inflation automatic
3. If Yes, then the whole thing will be a bit more complicated (but not that much) to keep in sync both settings (although the pot can be used then, it is not recommended)
   hopefully I can just use slider

[marvin7]

@Eyberg

SetPoint because it controls psi set the deflation or inflation automatic

Yes, I understand that, that is why I included it in the BLYNK_WRITE function. As for me, the rest of this function is not needed as it mainly stabilises the setPoint var to avoid fluctuations. you may need to include within BLYNK_WRITE the isSetPointChanged = true;
It might be needed in other part of the code (haven’t checked and overlooked that)

[Eyberg]

Hummm ?