Input Wanted! BRX HTTP features...

[Bolt]

We are launching new products this Fall, and API will be in the associated release.

Excellent!
Any possibility of sending bits and bytes to the PLC via an API?  Perhaps sandboxed like MC and MHR, et al?

[deep6ixed]

Been chewing on this web service idea, but i don't have access to DmD at the moment.  What can the json instructions do.

Been doing a lot of work with web app design and I wonder how much you could actually run client side via JS and have the DoMore serve the html static and a small JS file that handles all the major lifting from the browser.

Something along the lines of a static HTML / JS you'd upload into the cpu filesysyem and then the broswer would then update to and from cpu via JSON.

[BobO]

Been chewing on this web service idea, but i don't have access to DmD at the moment.  What can the json instructions do.

Been doing a lot of work with web app design and I wonder how much you could actually run client side via JS and have the DoMore serve the html static and a small JS file that handles all the major lifting from the browser.

Something along the lines of a static HTML / JS you'd upload into the cpu filesysyem and then the broswer would then update to and from cpu via JSON.

The JSON instructions are for building and parsing JSON records.

The API returns PLC data as JSON records, appropriate for JavaScript running on the client. Our current plan is to roll out the API and initial web server this fall, and then next year roll out an instructions for generating user web pages that will heavily use JS to drive client side stuff.

[BobO]

Excellent!
Any possibility of sending bits and bytes to the PLC via an API?  Perhaps sandboxed like MC and MHR, et al?

Not in the initial release, but it is something we want to do. One of our concerns was exposing everything via the API, but I like the sandbox idea. We will probably use some form of API key as well.

[Bolt]

Been chewing on this web service idea, but i don't have access to DmD at the moment.  What can the json instructions do.

Been doing a lot of work with web app design and I wonder how much you could actually run client side via JS and have the DoMore serve the html static and a small JS file that handles all the major lifting from the browser.

Something along the lines of a static HTML / JS you'd upload into the cpu filesysyem and then the broswer would then update to and from cpu via JSON.

There's always plcnut's method of web serving: https://forum.hosteng.com/index.php?topic=1117.0

[Bolt]

Excellent!
Any possibility of sending bits and bytes to the PLC via an API?  Perhaps sandboxed like MC and MHR, et al?

Not in the initial release, but it is something we want to do. One of our concerns was exposing everything via the API, but I like the sandbox idea. We will probably use some form of API key as well.

Please do!

[johnr]

Does that mean that the new POM would also be 10/100 Mbps?

[BobO]

Does that mean that the new POM would also be 10/100 Mbps?

It is.

[deep6ixed]

The JSON instructions are for building and parsing JSON records.

The API returns PLC data as JSON records, appropriate for JavaScript running on the client. Our current plan is to roll out the API and initial web server this fall, and then next year roll out an instructions for generating user web pages that will heavily use JS to drive client side stuff.

This sounds exciting.

[robert.beal]

Any update on being able to send bits and bytes to the PLC via the Web API? I can read from the API but I cannot change the values so I can interact with the plc code.

[BobO]

Any update on being able to send bits and bytes to the PLC via the Web API? I can read from the API but I cannot change the values so I can interact with the plc code.

We do plan to add it, but the primary concern is how to do it securely. Since (for now) the webserver isn't encrypted, we have concerns that even using an API key or something like that is still too exposed.

[robert.beal]

Thanks, hopefully soon we will get there.