Transmitter Interface

[NZ0I]

While I wait for Dual-Band Transmitter boards to arrive from OSH Park, I'm continuing to work on the browser user interface. The approach will be similar for both the transmitters and the receivers: both will be controllable using any wifi device that runs a browser.

I'm not an HTML or Javascript programmer, so my efforts at creating a user interface screen are simplistic, and not particularly elegant. But it does pretty much work thus far, and seems to function on all the OS's and browsers I've tried: Chrome, Safari, Firefox and Microsoft Edge. But it has NOT been tested yet on an Android device. If you have an Android device to test it on, please let me know if it seems to be working or not. You can test it by opening a browser on your Android phone or tablet, and entering the following URL:

http://openardf.org/test/test.html

To compare your Android touch screen experience with how it is supposed to work, navigate to the above URL using your PC and try clicking on some of the buttons and dragging the sliders left and right using mouse actions. Just reply to this email with any results.

The transmitter interface is fairly simple. There are only nine (9) settings required to fully define a transmitter and its behavior (unless I've overlooked something):

1) Behave as the Master or a Clone

2) Accurate time (not part of the interface yet)

3) Event type: Classic, Sprint, or Fox-O

4) Fox ID: MOE, MOI, MOS,... etc.

5) Start date and time for the event

6) Finish date and time for the event

7) Band: 2m or 80m

8) Fox frequency

9) Homing beacon frequency

Given all of the information above a transmitter should be able to function completely on its own: turning itself on/off at the right times, sending its transmissions at just the right instant and on the right frequency. Once configured, a spare transmitter can be quickly programmed to replace any of the transmitters in the field by simply changing its fox ID (#4 above) which determines its transmit timing and behavior.

There is still lots of work to be done. And lots of room for improvement on the user interface. If you have any interest in working with HTML and Javascript to improve the user interface please let me know!

Happy New Year!

Charles

[Gerald Boyd]

Happy new year to the group!!

Tired it on both a iPad and iPhone and it works good. Don’t have an Android device.

Building up the receiver digital attenuator circuit, plan to start testing tonight.

Jerry

Sent from my iPad

--
You received this message because you are subscribed to the Google Groups "Receiver Development Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to receiver-development...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/receiver-development-platform/33e649fa-330f-4d4c-b5f1-415ed9c47daa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ron Nelson]

Charles, 

Happy New Year!

I tried the browser user interface under Android v 4.4.4 using an Android Maxx smart phone and everything appears to work.

Cheers,

Ron NR5ON

--
You received this message because you are subscribed to the Google Groups "Receiver Development Platform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to receiver-development-platform+unsub...@googlegroups.com.

[Charles Scharlau]

Thank you Ron. And Happy New Year!

More changes will be coming to the interface. Not only did I forget to include the operator's callsign among the settings, but it lacks support for bounds checking of the frequency settings, and WebSockets support. I will let the list know when changes have been uploaded, and would appreciate your help again just a little later in 2018.

73,

Charles

[NZ0I]

The transmitter's HTML browser interface has been updated. Not much HTML changed, but a lot of Javascript was added. The page now prevents the user from entering most illegal values, and flags (using red text) problem situations, like having the foxes and homing beacon frequencies too close together, or outside the recommended frequency ranges. The only entry that doesn't get thoroughly scrubbed is the callsign: it will accept anything with 3 letters or more, and that contains at least one number and one alphabet letter.

http://openardf.org/test/test.html

As before, I would appreciate reports of any testing done on any browser and any OS. But I am especially interested to get feedback from those using Android devices, since I have no way to test those.

Thank you!

73,

Charles

NZ0I