Happy new year!
Under Compiler MikroeBasicPro for PIC the Tool generate ANCON by ADCON Line.
My CPU-Parameter are P18F8722.
In the Taskbar there are no Icon from Visual-TFT (Windows7)
Why can't write the location from my Compiler in the Settingeditor?
Best regards Helmut
ADCON (solved) and ICON Mistake
ADCON (solved) and ICON Mistake
- Attachments
-
- Adcon_+_ICON.png (62.45 KiB) Viewed 4295 times
Last edited by Helmut on 01 Jan 2011 21:43, edited 1 time in total.
Re: ADCON and ICON Mistake
Hello,
Take a look at the attachment mouse is pointing to it. Edit these few simple lines to suit P18F8722 and you will be well on your way.
http://www.mikroe.com/esupport/
Best Regards
Happy New Year to you too Helmut,Helmut wrote:Happy new year!
Actually, Visual TFT tool generates ADC initialization lines you input in the settings tab 'Touch Panel Connections'.Helmut wrote:Under Compiler MikroeBasicPro for PIC the Tool generate ANCON by ADCON Line.
My CPU-Parameter are P18F8722.
Take a look at the attachment mouse is pointing to it. Edit these few simple lines to suit P18F8722 and you will be well on your way.
I would suggest reinstalling the tool again, if that doesn't solve your problem contact us at our Support DeskHelmut wrote:In the Taskbar there are no Icon from Visual-TFT (Windows7)
http://www.mikroe.com/esupport/
Not quite understanding this one, can you please explain in more details?Helmut wrote:Why can't write the location from my Compiler in the Settingeditor?
Best Regards
- Attachments
-
- ScreenHunter_01 Jan. 01 20.00.jpg (76.56 KiB) Viewed 4274 times
LibStock
http://www.libstock.com/
mikroSDK
https://www.mikroe.com/mikrosdk
mikroBUS
https://www.mikroe.com/mikrobus
http://www.libstock.com/
mikroSDK
https://www.mikroe.com/mikrosdk
mikroBUS
https://www.mikroe.com/mikrobus
Re: ADCON and ICON Mistake
Thank you for the answer!
Adcon is solved I didn't see that...
i mean where can i told the Visualtool where is my BasicCompiler.
When i click on "Play" the TFT-Tool write: i didn't found, please reinstall MikroePro..
I installed the tool and the compiler on Harddisk i:\Visual.. and i:\MikroeBasicPro...
Big Tool, i'm happy to this.
I wish a little Board with Prozessor, SD-Card, or so, and Pin's to contacted to TFT-Protoboard
It's not possible to make the Ram-Place for Jpeg_Decoder and other great RAM use from this into Rom ?
Or can i have input how make little Ramplace: BMP, Jpeg what kind of Format is bedder, or other tipps ?
Best regards Helmut
Adcon is solved I didn't see that...
i mean where can i told the Visualtool where is my BasicCompiler.
When i click on "Play" the TFT-Tool write: i didn't found, please reinstall MikroePro..
I installed the tool and the compiler on Harddisk i:\Visual.. and i:\MikroeBasicPro...
Big Tool, i'm happy to this.
I wish a little Board with Prozessor, SD-Card, or so, and Pin's to contacted to TFT-Protoboard
It's not possible to make the Ram-Place for Jpeg_Decoder and other great RAM use from this into Rom ?
Or can i have input how make little Ramplace: BMP, Jpeg what kind of Format is bedder, or other tipps ?
Best regards Helmut
- Attachments
-
- RAM.png (4.15 KiB) Viewed 4246 times
Re: ADCON and ICON Mistake
We will inspect this issue further, did you install your compiler as Current User or for All Users?Helmut wrote: i mean where can i told the Visualtool where is my BasicCompiler.
When i click on "Play" the TFT-Tool write: i didn't found, please reinstall MikroePro..
I installed the tool and the compiler on Harddisk i:\Visual.. and i:\MikroeBasicPro...
I am guessing you got the Not enough RAM/ROM message. This means you will have to either use smaller pictures, or delete one or two objects from your Visual TFT project.Helmut wrote: It's not possible to make the Ram-Place for Jpeg_Decoder and other great RAM use from this into Rom ?
Or can i have input how make little Ramplace: BMP, Jpeg what kind of Format is bedder, or other tipps ?
Best regards Helmut
Choosing between BMP and JPEG is fairly simple, BMPs take up more space but are faster drawn on the screen, JPEGs take much less space but, due to its complex coding/encoding
procedures, it is slower to be drawn on the screen.
It is up to you to decide what you want more, greater drawing speed on the TFT screen or application that uses less space.
Best Regards
LibStock
http://www.libstock.com/
mikroSDK
https://www.mikroe.com/mikrosdk
mikroBUS
https://www.mikroe.com/mikrobus
http://www.libstock.com/
mikroSDK
https://www.mikroe.com/mikrosdk
mikroBUS
https://www.mikroe.com/mikrobus
Re: ADCON (solved) and ICON Mistake
I have one Picture, 13 Text Label and without IF then else or Case Statement only 108 Ram Bytes.
There is not too much, you must understood this question.
With j50 i have 78 Bytes, and i have no case or other...
Is it not possible to make the jpeg and other RAM-Space in the Rom-Space?
There is not too much, you must understood this question.
With j50 i have 78 Bytes, and i have no case or other...
Is it not possible to make the jpeg and other RAM-Space in the Rom-Space?
- Attachments
-
- Projekt.png (255.08 KiB) Viewed 4178 times
Re: ADCON (solved) and ICON Mistake
Hello,
if you take a look at the compilers Statistics->Variables you will see the "culprit"
JpegDecoder with more then 2000 size in bytes.
Procedures for decoding jpeg pictures and displaying them on the screen are quite complex and as a result take a lot of space.
Of course there is always a workaround
By looking at picture in your project i could suggest to edit it (MS Paint would be sufficient) and save it as 16 Color Bitmap
Place it in your project instead of the mentioned jpeg and save/generate code again.
Before building your project from compiler go to *your_project*_Driver file and in the
DrawImage procedure comment out line that contains TFT_Image_Jpeg so that compiler will not link it.
Build project and that should free up significant amount of RAM.
Best Regards
if you take a look at the compilers Statistics->Variables you will see the "culprit"
JpegDecoder with more then 2000 size in bytes.
Procedures for decoding jpeg pictures and displaying them on the screen are quite complex and as a result take a lot of space.
Of course there is always a workaround
By looking at picture in your project i could suggest to edit it (MS Paint would be sufficient) and save it as 16 Color Bitmap
Place it in your project instead of the mentioned jpeg and save/generate code again.
Before building your project from compiler go to *your_project*_Driver file and in the
DrawImage procedure comment out line that contains TFT_Image_Jpeg so that compiler will not link it.
Build project and that should free up significant amount of RAM.
Best Regards
LibStock
http://www.libstock.com/
mikroSDK
https://www.mikroe.com/mikrosdk
mikroBUS
https://www.mikroe.com/mikrobus
http://www.libstock.com/
mikroSDK
https://www.mikroe.com/mikrosdk
mikroBUS
https://www.mikroe.com/mikrobus
Re: ADCON (solved) and ICON Mistake
Thank you for the answer,
this option (Jpeg to 16-BMP) i tried it bevor i write this topic. The picture is black and white, after this.
But thank you for the tip with jpeg-decoder option!
I tried this in future.
Edit: It's very helpfull !!!
The more i work with it, the more fantastically, i find, is this software.
Best regards, Helmut
this option (Jpeg to 16-BMP) i tried it bevor i write this topic. The picture is black and white, after this.
But thank you for the tip with jpeg-decoder option!
I tried this in future.
Edit: It's very helpfull !!!
The more i work with it, the more fantastically, i find, is this software.
Best regards, Helmut
Re: ADCON (solved) and ICON Mistake
Hello,
we are glad you like it. It is always nice to give something back to the community,
so if you want you can post your projects on Projects Page of our website.
http://www.mikroe.com/eng/projects/index/
Best Regards
we are glad you like it. It is always nice to give something back to the community,
so if you want you can post your projects on Projects Page of our website.
http://www.mikroe.com/eng/projects/index/
Best Regards
LibStock
http://www.libstock.com/
mikroSDK
https://www.mikroe.com/mikrosdk
mikroBUS
https://www.mikroe.com/mikrobus
http://www.libstock.com/
mikroSDK
https://www.mikroe.com/mikrosdk
mikroBUS
https://www.mikroe.com/mikrobus