Jump to content

Relativity1

Members
  • Posts

    4
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Relativity1

  1. Hi LV Gurus, The Parse State Queue Arguments output is an awesome feature I have been using to update the status indicator. Is there a way for this feature to pass through escaped characters (e.g. \n ) so I can properly format the status "LCD" indicator. Currently when I send "Status >> Blah...blah... \n Blah..Blah" the Status LCD literally will display "Blah...blah... \n Blah..Blah" with the escape character printed and no new line. Thanks Guys!
  2. Hello LV Gurus, I have used JSM since release 1.0 (circa LV 2011). I understand the sub-diagram label feature was not yet implemented. Is there a reason why the JSM 2018 still not using sub-diagram labels (like below) since that has been standard in LV for many many years. Thanks guys! Sub-Diagram Labels enabled (lots of manual editing just to clean up those comments) Sub-Diagram Labels not enabled (current 2018 version):
  3. You forgot one important thing: an asterisk "*" in the Machine Access List. Also, very important, verify your TCP port address in the VIPM (Options >> LabVIEW tab). If you have multiple LabVIEW installations make sure each VI Server have unique ports. Good Luck! Relativity1
  4. Hello LV Gurus, I am creating a simple GUI to control a web (specifically RESTful web server) based DLI Web Power Switch Pro I have three problems: What is the "Base URL" Is it just the IP + port (e.g. http://192.168.0.100:80) or the whole URI including the path to the web server (e.g. http://192.168.0.100/restapi/relay/outlets/0/state/) Where and how do I insert the cross-site forgery ignore in the header (e.g. X-CSRF:x) with your REST API? The Default Header list does not include X-CSRF. Do you support Basic and/or Digest authentication? I get "Unauthorized" error messages using your PUT (or GET) methods returned in the Status String. I then proceeded to create a version of this GUI using cURL (via the System Exec node) to enable switch outlet 1 using "digest" authentication and it works: curl --digest -u admin:1234 -X PUT -H "X-CSRF: x" --data "value=true" "http://192.168.0.100/restapi/relay/outlets/0/state/" FYI: This is DLI guideline for using RESTful HTTP on their power switches Thanks in advance guys. You do wonders for us LabVIEW cogs! Relativity1
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.