Flowcode Support Board

Hi, EVERYONE

Good morning

I am dealing with a serious issue, and it has become increasingly blatant to me now.

I was working on a project well over a year now. Along the way I saw some couple of things happening, but I found ways around some of them.

Components are disappearing of panel / software messed up / software takes 10 seconds to close / software 10 seconds to simulate.
Theres no way to access the properties. I have no use for it as I have configured it already when it was there. I can access the macro inside it thou. First, I noticed that I wasn't seeing any Ultrasonic sensor readings on my display "Hardware". However, it was showing in simulation.

Secondly. If I copy the touchscreen keypad project from the original source "Example" it works. But if I copy that same project from another project it doesn't work. same as on HARDWARE TOO
Let's say I created (project "A" Keypad") and I want a second copy which is (project "B") It only shows half the keypad....
Customer Service
Those problems that are listed I started seeing them from last year, till earlier June of this year. I never see the need for me to go fast until there was a job offer for the Ai. Ai does most of the interaction on the board to the customers. Only thing I do is to print the information to the screen so persons can see what's going on etc... So, there's a need for me now to Update the board and make changes/ improvment.

HARDWARE Issue
I started to fill more information Inside the Esp 32 chip and was testing as I go along the way. (BUT THE PROBLEM WAS THERE I DIDNT SAW IT) however, I found out that my hardware Screen Started Jumping (Like Ghost Touch) without me touching it. I wasn't seeing it in the SOFTWARE as Yet,but it was there
In my main loop program, two touch descion box are there.
A) Simulation "software" If touch =? ======This Programs Only works in Simulation======= AS Test purpose
B) Hardware "Real world" If touch = 20 ======This Programs Only work in the Real world==== This WILL USED Permantly

If I used "A" on my hardware the Screen touches and branch to other screen sometimes.
I used "B" Only when I am adding new stuff to my program and if things get serious, then that's the time I used "B" on my hardware.

Then again, I mostly use "A" on my board "hardware" as TEST. So, I thought that was it acting up. So, I ignored it. In my Hardware after I pressed certain button then goes back to Screen 0 or screen 1 it keeps jumping. I can't figure out the issue as I am not seeing that in SOFTWARE. It's behaving like that, only seeing that in the hardware.

WHEN I COMPLETE ALL the customer Service Information inside my program. I accentually touch apart of the blank screen in software (WHERE NO BUTTON IS). That's the time when I NOTICE ITS A SOFTWARE ISSUE. I also recently want to update my Dail Keypad.


Recently I made a post regarding this link. how I wanted to improve my dialing keypad to work the correct way, as well as I want the GSM Module to start send/receive SMS Message to customers. so, they can get information to their phone.
https://flowcode.co.uk/forums/viewtopic ... 164#p25164

TOUCHSCREEEN DIAL KEYPAD
When I posted this project, it was working and compiling etc.
I have added the update to my board when (Martin mnfisher) had replied FIRST.


I removed that SMALL program from the board and was continuing with the MAIN project. Then Martin had replied again. When I was ready to upload back the "Esp32KeyPad" program back to my board to test it. the complier keeps failing. I don't know why and that was from last Saturday.
I also tried recompiling my MAIN project that one fails too. SOMETHING WAS WRONG. But another project was compiling.
My main program was disrupted completely. I had to discard it. When back to a lower version test it was compiling then I updated it.


I know I couldn't copy projects from other projects (As they won't work or work in some weird way) on my machine. I had some time on my hands. So, I decided to recreate the project from scratch using the same variables / connection etc. After I reach a certain portion, I started testing the screen by pressing the blank spot on it and (THERE WAS NO JUMPING FROM SCREEN TO SCREEN) then I finally reach back at the keypad regarding the SAME project above. Test the keypad. See it makes calls and hang up ...when I upload the keypad project to the board. The program works different from the software.... In software it works correctly. But in the hardware, it different....

CREATED NEW PROJECT Saturday 3. I don't not copy this project created everything using same variable


NEW PROJECT
SIMULATION
Bluetooth button Pressed---------"No Color"
Color button Pressed -------------"No color"
Dail Numb Button ---------When calls are place it works perfectly like the Original Program "

HARDWARE
Bluetooth button ---------"No Color"
Color button -------------"No color"
Dail Numb Button --------- when call is placed it jumps inside "Bluetooth button Screen" (That should not happen)

========================================================================================================


OLD PROJECT
LONG TIME PROJECT (1 Year)
ESP 32 Customer

SOFTWARE AND HARDWARE WORK THE SAME

Bluetooth button ---------"Shows Color"
Color button -------------"Shows color"
Dail Numb Button --------Works Okay


How can these problem be fixed?
Both programs are the same. But giving DIFFERENT RESULTS

Old Project RUN THE SIMULATION, TELL ME IF YOUR GETTING THAT "SCREEN JUMP" ON BLANK TOUCH.
I DONT HAVE ANOTHER LAPTOP CAN TEST


New Project

Regards

Jumping Jack

New Programm How these problems can be solved

Regards

Hello,

Sorry to hear you're having issues.

Please can we try and tackle this one problem at a time. You have posted a large report with screen shots and then separatley you have posted programs with no correlation between the two which makes it very difficult to try and dig in and help.

Let's try and focus on one specific program and the problems you're having there. Please post the program along with the description of the issue you're seeing.

And just to add to Ben's comment, it is easier for us to debug an issue when the project is as simple as possible. So ideally, it's best to create a small project that exhibits the specific issue rather that posting a larger project with a lot of unrelated code.

Of course, this is sometimes not possible and the problem only manifests itself when part of a larger project. But if it can be replicated in a simple project then it is so much easier for us to help.

Hi

The issue with disappearing component for anyone else that has experienced this was due to the second UART being inadvertently moved "off screen", something I've done myself if using a trackpad. Depending on where it is you may need to expand your panel, and scroll up/down, left/right to find, but if it shows in Project Explorer > Components it's still there and part of your chart.

Regards

If something has moved off screen or been scaled very small then the easy way to find it is to find the item in the drop down list at the top of the properties window.

Then select the component and go to the Position tab. Here you can directly set the XY position as well as the scale.

Hi

Good morning

I was working on a project over a year now. There's an "Ai module" attached to the board. The Ai does most of the work.
Since recently, I have updated the esp32 with information. From time to time, while I have been doing that, I have seen some strange things happening.

When I posted the example a few days ago. It would appear that I have entered a "Deep Rabbit Hole" I Didn't realized that. But the deeper I get the greater the bugs became; it started affecting the entire program.... I was doing less hardware testing. so, it creeped up on me unnoticed. The software wasn’t picking up any issues...It just showed normally as if everything is OKAY...
But when I test the hardware, it was misbehaving very BAD.... ITS hard to Debugs a hardware when the software is showing normal.



When you guys had asked for a smaller program than the one I uploaded. I reduced it to a smaller program and then from there. I wasn't getting any
(BLANK TOUCH ON SOFTWARE)
So am trying to work my way back up slowly. So far, I have reached a portion by testing each phase by phase. So, I have spot 2 bugs that the software didn't pick that up. Using the same exact program

I have also ruled out the Ai module. Trying to see if the Ai module has nothing to do with it as well. So far, it's working. I AM DOING OKAY.




PROGRAMS
When I saw the program misbehaving like that, I TRY creating a small new Program. To test If i am Getting any Blank Touch on Hardware. I wasnt getting any


This is what I shrink the (1 year) program to, and I am not getting any TOUCH ON BLANK SCREEN. Recent (Saturday was created) These 2 examples, are the same but when I upload them to my board they behave differently in terms of colors

The old project shows the COLORS
The new one doesn't show the COLORS

Regards