Vex v5 Brain upload images


#1

Hello fellow forum goers, today I was tasked with the job of making a logo on the vex v5 screen and i was wondering if there is a way to import an entire photo onto the v5 brain. Also is there anyway to display a video


#2

not yet.


#3

is it possible in pros


#4

I do not use pros.


#5

ok thanks anyway


#6

see if the DOOM port helps


#7

This thread https://vexforum.com/t/doom-on-the-v5/49909/1


#8

It’s possible in PROS. One way I’ve uploaded images is by using the LVGL picture converter, which converts your image into a C array and dumps it into an LVGL-compatible file (just make sure to use the old converter and change the include path). You can then display that image quite easily. Check the LVGL docs for more info.


#9

Thanks soo much this is such a big help, can it do videos too?


#10

I don’t believe it can, but there might be other alternatives you can consider.


#11

There was this
https://vexforum.com/t/happy-holidays/51337/1

and I’ve also written code to play animated gifs, it works quite well.


#12

Could u link the code please


#13

My understanding is that the APIs needed are not currently available in VCS. We’ll see what the next release of VCS holds - my priority would be wireless downloading of programs vs animated images :slight_smile:


#14

ok thanks for the reply


#15

Now the reality is we don’t know when next versions of any software package will be released.


#16

@vex lol


#17

it is a no win situation - seriously… the pendulum will swing in a different direction …

Right now - our teams are able to accomplish what they need to with VEX C++ in VCS. That might not be universally true for all teams.


#18

ye i guess that is true


#19

The fireplace demo was a messy hack that reads in about 25MB of images and displays them in a loop. The images were png images, and the png image support has a bug in the current vexos that is fixed in 1.0.6. It also uses C API’s that are not documented but have a C++ equivalent in the sdk that VCS will have when it ever gets updated (and I have no idea when that will be).

The animated gif program was based on some open source gif reading code, but it exposed a bug in the way VCS uses one of the standard library memory allocation functions, also fixed in the next sdk, meaning I can’t release it at this time. It also needed a larger heap to allow multiple animated gifs to be displayed, something beyond the scope of what students can easily do with VCS without knowledge of how linker scripts etc. work.

as far as vexos is concerned, this work is finished, we expect our partner developers to be supporting this with the release of vexos 1.0.6 as long as they don’t find issues that need us to revise the firmware.


#20

that is good to know! Thanks for all you do!