Hi, all, it's me again. What? No, don't run away!
So, I've been asking a lot of questions about user interfaces on R30iBs lately. This is because I'm a Fanuc n00b, and been assigned to (along with everything else) come up with an "HMI" for a new Fanuc, for a customer who needs a really simple, never-touch-the-pendant interface. But it also needs to be cheap, and put together quickly, b/c this project has a very... "compressed"... timeline.
What we've settled on is using the iPendant Customization methods (no purchased options required), and create a "web" page on the robot that can be accessed from the pendant browswer, and presents some "buttons and lights" to the operator.
Now for the good news: using a very simple sample HTML file that someone at Fanuc was kind enough to provide, I've been able to achieve a minimal proof-of-concept page -- once I put the STM file (Fanuc's HTML file extension) into my virtual robot's FR, I was able to add it to my Browser Favorites. The page has buttons that can actuate DOs, and I was able to pull "live" values from Registers and display them.
What I need some help with is figuring out what I can and can't do without KAREL, and how (if?) I can modify the Ajax controls to get live control of aspects of the screen objects -- for example, if I want a button to change color, or blink, based on a Register value or a DO state, or how to post long messages when SRs are limited to 23 characters.
And, mostly, the "this stuff isn't in the manual" things that (hopefully) someone here learned when they had to climb this learning curve, and are (hopefully) willing to share.