New version 1.48.2 to test before final release

Here you'll find the updated available
Post Reply
User avatar
PeterN
Posts: 366
Joined: Mon Feb 08, 2021 7:56 pm
Location: Krefeld, Germany
Has thanked: 171 times
Been thanked: 203 times
Contact:

Re: New version 1.48.2 to test before final release

Post by PeterN »

[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 5:04 pm
[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 2:53 pm
[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 2:18 pm Hi bugs
Not very sure ... but camera setup(7) should initialize with 800*600
Right ... it should initialize with camera.setup(x) ... but it returns a "1" and doesn't wake up the camera nor set the resolution :-)

I have an other issue with camera.picture("filename") as this seems to save always a picture with 320*240
I had the same issue on Sunday and could change the camera resultion by using a direct command: http://module_ip/cam_setpar?framesize=value
As I don´t want to change it by software, this was a sufficient solution for me.
Rainer
Hi Rainer,
Thanks ... came to the same point right now :-) and found some issues that might be interesting for ciccioCB

I found the following issues in conjunction with version 1.48.22 and an ESP32Cam

# wlog camera.setup(x) returns 1 but does not do anything with the resolution. I used camera.params("framesize", x) instead.
Am I right to expect camera.stop to remove the driver from memory which can not be reverted by camera.setup(x)

# WLOG camera.params("framesize", 0) sets resolution to 96x96 but returns 0 instead of 1; the same with other resolutions

# There seem to be 3 new resolutions/framesizes which are currently not in the table in the help file . This may create some irritating results with old annex-code that relies on the old table and now runs in the version 1.48.22 environment.

Code: [Local Link Removed for Guests]

0  96x96   <-new
1 160x120
2 176x144
3 240x176
4 240x240  <-new
5 320x240
6 400x296
7 480x320  <-new
8 640x480
9 800x600
10 1024x768
11 1280x720 
12 1280x1024
13 1600x1200
# camera.picture("filename") saves a picture - but does not do that with the resolution that has been set before with camera.params("framesize", x)

The browser cache is sometimes a cause for that kind of problems - I tried to avoid this.
Perhaps someone can test that as well - before I make alerts without need :-)
TNX
Peter
bugs
Posts: 142
Joined: Mon Feb 08, 2021 10:10 pm
Location: Scotland
Has thanked: 44 times
Been thanked: 50 times

Re: New version 1.48.2 to test before final release

Post by bugs »

# camera.picture("filename") saves a picture - but does not do that with the resolution that has been set before with camera.params("framesize", x)
I noticed that but I don't really understand many of the camera commands. I think the snapshot was always one resolution below the setting - but memory is not fresh...
User avatar
PeterN
Posts: 366
Joined: Mon Feb 08, 2021 7:56 pm
Location: Krefeld, Germany
Has thanked: 171 times
Been thanked: 203 times
Contact:

Re: New version 1.48.2 to test before final release

Post by PeterN »

[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 5:42 pm
# camera.picture("filename") saves a picture - but does not do that with the resolution that has been set before with camera.params("framesize", x)
I noticed that but I don't really understand many of the camera commands. I think the snapshot was always one resolution below the setting - but memory is not fresh...
Yes - and this seems to have gotten worse, as the frame size table is now bigger :-(
User avatar
PeterN
Posts: 366
Joined: Mon Feb 08, 2021 7:56 pm
Location: Krefeld, Germany
Has thanked: 171 times
Been thanked: 203 times
Contact:

Re: New version 1.48.2 to test before final release

Post by PeterN »

But I'm glad that apparently some people here do work with the CAM version :-)
This should also be good feedback for ciccioCB ;-)
User avatar
cicciocb
Site Admin
Posts: 1899
Joined: Mon Feb 03, 2020 1:15 pm
Location: Toulouse
Has thanked: 407 times
Been thanked: 1269 times
Contact:

Re: New version 1.48.2 to test before final release

Post by cicciocb »

[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 5:53 pm But I'm glad that apparently some people here do work with the CAM version :-)
This should also be good feedback for ciccioCB ;-)
Yes, there is a little bit of activity to be done on the CAM.
It seems that there are at least 3 people using it .. :D

I think that several things changed on the camera with the recent SDK releases, in particular the resolution table changed.
Is in the TODO list ....
User avatar
PeterN
Posts: 366
Joined: Mon Feb 08, 2021 7:56 pm
Location: Krefeld, Germany
Has thanked: 171 times
Been thanked: 203 times
Contact:

Re: New version 1.48.2 to test before final release

Post by PeterN »

I can contribute two more "silent users" behind me :-)
User avatar
cicciocb
Site Admin
Posts: 1899
Joined: Mon Feb 03, 2020 1:15 pm
Location: Toulouse
Has thanked: 407 times
Been thanked: 1269 times
Contact:

Re: New version 1.48.2 to test before final release

Post by cicciocb »

[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 29, 2022 3:49 pm
Screen work properly, but the touch is not sensivtive, as I only have one Touch LCD on hand, so no way to tell if it is only my touch sensor problem!?!?
Anyone have try to screen touch?
Thanks!TFT.jpg

I need to say again. Annex RDS is very easy to use, total settup time on prototype within 1 hour. When power up the unit, Annex icon say hello to me with QR Code "192.168.4.1" :D :D :D
Unfortunately the resistive touch is not the ideal and depends on what you receive as some displays works well but some are very bad.
You can try this simple painter program to check your touchscreen

Code: [Local Link Removed for Guests]

gui.init 20, 0
col1 = gui.button 0, 0, 50, 40, "RED"
gui.setcolor col1, tft.color(black), tft.color(red), tft.color(yellow)
col2 = gui.button 0, 40, 50, 40, "GREEN"
gui.setcolor col2, tft.color(black), tft.color(green), tft.color(yellow)
col3 = gui.button 0, 80, 50, 40, "BLUE"
gui.setcolor col3, tft.color(black), tft.color(blue), tft.color(yellow)
col4 = gui.button 0, 120, 50, 40, "WHITE"
gui.setcolor col4, tft.color(black), tft.color(white), tft.color(yellow)
col5 = gui.button 0, 160, 50, 40, "BLACK"
gui.setcolor col5, tft.color(white), tft.color(black), tft.color(yellow)
clr = gui.button 0, 205, 50, 35, "CLEAR"
gui.setcolor clr, tft.color(white), tft.color(olive), tft.color(yellow)
gui.setevent col1, 1, changeColor
gui.setevent col2, 1, changeColor
gui.setevent col3, 1, changeColor
gui.setevent col4, 1, changeColor
gui.setevent col5, 1, changeColor

gui.setevent clr, 1, clearAll
color = tft.color(white)

gui.autorefresh 50, 1

for z = 1 to 10000000
  touch.read
  if touch.z = 1 then
    tft.circle touch.x, touch.y, 1, color , 1
  end if
  'pause 1
next z
end

changeColor:
select case gui.target
  case col1
    color = tft.color(red)
  case col2
    color = tft.color(green)
  case col3
    color = tft.color(blue)
  case col4
    color = tft.color(white)   
  case col5
    color = tft.color(black)              
end select
return

clearAll:
tft.fill 0
gui.redraw
return

image.png
You do not have the required permissions to view the files attached to this post.
Palm Liu
Posts: 41
Joined: Fri Jun 25, 2021 3:50 am
Has thanked: 10 times
Been thanked: 17 times

Re: New version 1.48.2 to test before final release

Post by Palm Liu »

In order to test the touch sensor of LCD module, I drive it by WeMos D1 Mini, then the touch work properly, may be my LOLIN D32 has some problem (as I got several reset / WIFI lost on LOLIN).

My code is :

Code: [Local Link Removed for Guests]

OPTION.CPUFREQ 160
  SPI.SETUP 40000000 
  TFT.INIT 16, 4, 1
  TFT.FILL 0
  TOUCH.SETUP 15
  
  XLAST = TOUCH.X
  YLAST = TOUCH.Y
  WHILE 1
    DO
      X = TOUCH.X
      Y = TOUCH.Y
      XX = TOUCH.X
      YY = TOUCH.Y
    LOOP UNTIL X = XX AND Y = YY
    IF XLAST <> X OR YLAST <> Y THEN
      XLAST = X
      YLAST = Y
      X = 319-INT((X+6)*320/346)+5
      Y = 239-INT((Y+8)*240/262)-2
      TFT.CIRCLE X, Y, 2, rnd(65535), 1
      IF X < 10 AND Y < 10 THEN
        TFT.FILL 0
      ENDIF
    ENDIF
  WEND
You do not have the required permissions to view the files attached to this post.
Palm Liu
Posts: 41
Joined: Fri Jun 25, 2021 3:50 am
Has thanked: 10 times
Been thanked: 17 times

Re: New version 1.48.2 to test before final release

Post by Palm Liu »

"Annex pocket computer" working in progress!!!

3.2" size LCD module is enogh to show editor content
You do not have the required permissions to view the files attached to this post.
AndyGadget
Posts: 222
Joined: Mon Feb 15, 2021 1:44 pm
Has thanked: 120 times
Been thanked: 132 times

Re: New version 1.48.2 to test before final release

Post by AndyGadget »

I'm another occasional ESP-CAM user. I've used one during the summer for time lapse photography but I've just updated one of my modules to the latest to put on the end of a stick and shove down a drain to investigate a blockage. (Thankfully it's a road drain, not *that* sort of drain.)
Necessity is the mother of many strange bastards :D
Post Reply