BATC Forum

Whilst working on the most recent update, I decided that the time has probably come to rearrange the TouchScreen Menus.

I want to move the Portsdown from being a Computer that transmits DATV, to being a touchscreen-controlled DATV Transmitter. I am considering the following screens for Menu 1 and Menu 2.

So the top line of Menu one would select the video source: The Pi Camera, an external composite video source, the internal bouncing balls test card, the Contest Numbers or the screen image (currently the BATC logo, but with other possibilities in the future). The rest of Menu 1 is unchanged.

The top line of Menu 2 selects the video encoding: H264, MPEG-2, IPTS IN (either MPEG-2 or H264 from a PC) or no encoding at all to generate a carrier.

The next line of Menu 2 selects the output Mode: IQ for the filter-modulator board, Ugly (QPSKRF) mode for testing, Express to drive the DATV Express modulator through USB, BATC to stream to the BATC streamer or Vid Out to simply put the selected Video source on to the composite video output of the RPi to drive an analog (FM or AM) transmitter.

The 3rd line of Menu 2 would select the Audio input: Mic for a USB Audio dongle, auto, EasyCap for the line inputs on an EasyCap, Bleeps to generate test bleeps and No audio to not transmit an audio stream.

The Shudown and Reboot buttons on line 4 are self-explanatory; the PAL in and NTSC in buttons change the mode of the EasyCap to allow either sort of video input. Lastly there is a button to select a 3rd menu (more to come!).

This is all a mock-up at present - I have not written the code for it. PLEASE let me know if you like it, or if you have other suggestions to simplify the menus and make the Portsdown easier to use.

Dave, G8GKQ

Like it. Be nice to be able to enter a frequency or symbol rate manually via a touch keypad but suspect too difficult!

Hi Mike

Thanks. See serial 13 here: http://batc.org.uk/forum/viewtopic.php?f=103&t=5097

Dave

Hello Dave,
I am liking the concept / idea, am wondering if the first page should be mostly information and the most used function, Keep the TX, RX and Menu (Settings) Buttons.
Not sure about your "Normal" usage, but for me things such as FEC, Frequency and SR are rarely changed, compared with input methods, so could they be indicated on the first page but set in a deeper menu (a bit like the console menu, shows what the settings are then you drill into a menu to make the required changes.
Another thought that has popped into my head as I type this, if the front page was showing say FEC of 3/4, your press on that button and up pops a mini menu with the possible selections and then you return to the front page, this would be even more suitable to Freq and SR as the mini popup menu would have your pre-sets, plus could be the "Calculator" to enter your new desired freq/SR (either changing the pre-sets or direct entry). Some of the options would only need to toggle. Forgot to add the shutdown and reboot buttons, that could also be a single button that then pops up shutdown, reboot and cancel (in case of miss-press).
Invalid options could be greyed out, like H264/MPEG2 when IPTS In is selected.
This potentially frees up space on the display to add some of the information data needed (IP Address, Current Contest number etc)
I would be happy to help with some of the coding once a structure is decided on.
Regards,
Bevan

Hi Bevan

Thanks for your suggestions.

In my usage (which I admit is mainly portable and activity days), I tend to switch frequency, SR and FEC more often than output mode or encoding. However - it's very useful to know how other people use the TX.

I like the idea of "pop-up" menus. However, I hesitate because each pop-up menu needs to be coded as a new screen. So essentially, the front screen button displays the current value and selects a new screen when pressed. The next screen then closes when a new selection is made. Do-able but I would need to simplify the menu construction structure otherwise the coding will be a nightmare.

Up until now, I haven't managed to write 2 lines of text on a button. I have just worked out how to do it (although not implemented it yet) so thanks for the prompt!

I'll wait on a few more replies and then decide which direction to head in, but it's really useful to have your input and offer of help.

Dave

I think you might be able to get another row of buttons in - should have said this earlier.

Symbol rate could cycle through a range of options on each press which might be easier to code. So could frequency, FEC, & encoding.

Mike