Dane Sandilands, a Sydney based integrator who has cut his teeth working for the rich and infamous, introduced us to a strange and unique concept that actually improves your ability to output code at an alarming rate.

Starting with quiet ale at a saloon style restaurant called “Outback Jack’s”, when it came to ordering meals Dane opted for the 1 kg rump steak challenge.

Unbeknown to Sandilands, his 1 kg of medium cooked steak was served with a 1 kg side serving of potato wedges and an entire crop of vegetables.

With only 30 minutes to devour what looked to be the best part of a whole cow, Dane had to order an extra serving of sauce on the side and additional ale to wash it down with.

At the 29 minute mark Dane had managed to eat the majority of the cow but like any kid refused to eat his greens and left a large portion of potato wedges due to his low carbohydrate intake diet.

Dane commented, “Once you get past the dizzy spells and nausea, it is not too bad.”

Sandilands, a pioneer of this increased productivity method put it to the test the following day when he managed to accomplish the impossible and make it back to Sydney before the weekend was over.

One thing debated was the use of a land based toilet the following day as the off shore facilities where Dane was operating from may not have had the necessary plumbing requirements to achieve the desired flush.

Never the less, a full house for Dane and we are sure that his pioneering days are far from over.

The RTI K4 and the soon to be released T4 both have the ability to view web sites, providing a great platform for a user interface. Lack of Java support eliminates the possibility of utilising G3 Web Control.

There will be 3 mains steps involved to get RTI control and feedback. Firstly, the GUI must be created in HTML with a standard naming convention for your buttons. I used button__<0 or 1>.jpg where button one in the OFF state would be button_1_0.jpg and button_1_1.jpg when ON. Add a hyperlink to the image that points to the NetLinx master on port 81 with an extension to allow the master to recognise the button channel. It is also wise to add a series of chars to capture the end of the hyperlink. 3 pipes work fine. The link for button 1 would look like http://192.168.0.1:81/touchpanel/button?1|||

Next create a TCP server in your NetLinx code to monitor and respond to the requests from the GUI. Remember this must be on port 81. [ip_server_open( 0:3:0, 81, 1 ) ]. Using a data_event, the button presses can now be captured by looking for the hyperlinks under the GET HTTP header. Extract the button number between the button and the ||| and convert to a number. You now have the button channel to trigger whatever events you desire.

Finally, you have to create the feedback for either this button or any others it may have triggered. Buffer the html file of the GUI and then search for the button_ or whatever naming standard you chose. If you want to turn the button ON, change the proceeding 2 chars with _1 or to turn it off use _0. Save the buffer back to the GUI file. With the HTML updated with all feedback changes, send a HTTP header redirecting (302 Found) the RTI back from port 81 to the originating html file on the master. If the page fails to refresh with the new image then you can instead redirect to another html file which contains a simple JavaScript function that attaches a random extension to the redirect. ( window.location=”/touchpanel/index.html”+”?”+Math.random()*100; ) This will cause the html to be properly refreshed every time.