Skip to main content

TouchShield Slide Controller images

Posted in

Joao and I have been working hard on the TTS controller. Its time to show some progress. The images are a bit on the dark side because I want to show the TTS screen.

All buttons are working, including the action when they are touched as was shown in Joaos' video.

The following image shows the splash screen of the application. My controller is based on the TTS (of course). I also use an ExtenderShield from Liquidware so that I have more space for shields. I use an DFRobot input shield and a APC 220 wireless transmitter. That way the controller and the OpenMoco engine can find each other wireless. This wireless setup is very cheap. A cable and plugs will not be that much cheaper :-).

I have made a driver for the joystick that gives the value of the axis in percentages of their maximum output. This driver also works with my accelerometer. Tilting the unit gives the same idea as using the joystick. I just have ordered a real time clock that I will incorporate too. That way the engine can be controlled at specific time intervals for example.

The whole user interface is based on a small C++ class library that we have created. It currently holds an icon button class, text field class, toggle button class, background class, functionality to create canvases, basic persistence, page flow functionality. All user interface items can have callback functions that handle actions when the UI item is pressed (really selected). I have also included a screen saver into the core of the class library because OLED screens tend to burn in so fast.

Here is the splash screen again, bit zoomed in.

Here is the home page. You see that the background of the bitmaps are not always corresponding with the overall background. @threeaxis: Can you fix this in the images? That would be great!

I have implemented a text field UI class too. Here you see some samples of it. It's shows the basic version with a background (in any color) with text. One with a basic border and one with a 3D border. All of these images can be made selectable. The border will change color when a text field is pressed. Pressing a text field can show the button pad where the value of the field can be modified. This image also shows the toggle button that was discussed on this forum a while ago. Toggle button class is fully functional.

The last image for today shows the fully functional button pad. It can now handle both long and double values. I am currently working on date values too.

That is really awesome guys!

milapse's picture

That is really awesome guys! I'm still sitting here trying to absorb it all... =)

Wow! this looks really great.

Wow! this looks really great. I can't wait to try it out.

I love it! Especially like

I love it! Especially like the wireless option, much better range than bluetooth =)

!c

Looks great, can't wait to

Looks great, can't wait to see it controlling a system.

I forgot to mention that its

I forgot to mention that its powered by a LiquidWare lithium pack. The complete controller as I want to use it is not the cheapest one. But you just choose what you want or need.

Chris: the wireless option is working perfectly. There is no software or anything that you use on the Arduino. Just install it! I had two Arduinos talking to each other within 30 minutes. There is a configuration tool that you can download (Windows only). I used that to set the speed to 19200 baud (default is 9600). A break out option on the OpenMoco Arduino board would be nice to have :-).

We are a bit far from a working system. There is still a major issue with the TTS core since we cannot upload more than 33 images. Joao is working on that (I believe he uploaded 48 images last week). We also need a good serial library for Arduino <-> TTS and Arduino <-> OpenMoco engine communication.

And last but not least. I think that the wire frame of the UI is not finished either. Some help on the design of that would be appreciated.

hey cronix, those BGs were

hey cronix,

those BGs were fixed awhile back, but i believe it was only fixed on the on the processing version shutterdrone was working on? from the looks of it your using the first round of the bmps. in the newest round they were combined (off and on state), fixed BGs, and added text. that happened some time back but i think that might have just been on the wave before we had transitioned fully to the forum?

take a look at shutterdrone's most recent upload:
http://openmoco.svn.sourceforge.net/viewvc/openmoco/OpenMocoInterfaces/GUI/processing/trunk/om_if/data/
notice m_es_m.bmp has the fixes mentioned above. are you still using the version that had on and off as separate files?

Hi Threeaxis, I am definitely

Hi Threeaxis,

I am definitely using different images. So that explains the background issues. I already thought that you mentioned these were fixed (somewhere at this forum.

I am using separate files. I need separate files. Are these files still available? Can you provide them? Why not fix the long names along the way too? The filenames are already much shorter than the originals, but some are still a bit too long.

not a problem at all. i can

not a problem at all. i can cut those up. as for the file names, it'd be great if you guys could take the script approach previously mentioned? i'd love it if on my end i could keep those human readable just to make it easier from a organizational stand point.

Deal. You provide the images.

Deal. You provide the images. I provide the rename script.