Jump to content

Andy Balholm

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Andy Balholm

  • Rank
  1. I assume that Remote Operator uses the PCOM protocol. Is there any documentation of how it communicates with the OPLC beyond the low-level information in the documentation of the protocol? For example, how does it upload the PLC's screen layout?
  2. My problem was that all the columns in the first table were defined as "part of project", so that table really didn't exist.
  3. I want to read and write the data tables on a PLC using the PCOM binary protocol. There are three data tables. When I read data starting at address 0, I get the data from the table that is listed second in the Data Tables window in VisiLogic. Is there any way to tell from within VisiLogic which table is stored first on the PLC?
  4. There are 474 files to change. So I wrote a Perl script to do it. The new names are not very user-friendly, like "01af095f.js", but it seems to work—on a regular Apache web server, that is. I haven't tried it on a real PLC yet.
  5. SproutCore uses files with paths like /static/sproutcore/bootstrap/en/dd9de322ad13a3d1b5f705b175e9e87edb7de740/javascript-packed.js I'm not sure how to adapt it to 8.3 filenames. Is the 8.3 limit a limitation of the webserver itself, or does it come from how the PLC reads the SD card? Is the source code of the webserver available?
  6. I am building a web interface for a PLC using the SproutCore JavaScript framework. At this point, I can make it work with a separate web server, but it would be much more efficient to host the interface on the PLC itself. The enhanced web server sounds good, but it has too many restrictions on filenames. SproutCore isn't designed to work with DOS-style 8-character file names, and it needs files to be arranged in a certain directory structure. If I had a web server application that could support longer file names and arbitrary subdirectories, I think it would work. Any ideas?
  • Create New...