osp300 : communication between program & user, through interface :)

[deadlykitten]

... soon

Similar Threads:

• mb66vb osp300 : faster tools measuring and program assignment
• User interface signals Macro
• Has anyone done a touchy user interface for the lathe yet?
• Get Gooey: The new Haas user interface?
• Plot toolbar and user interface

[deadlykitten]

hello this is the simplest aproach that i could think of :

there is comunication between program ( under the cnc control ) and ( computer) application

- cnc_program creates file1 with random content
- cptr_application detects the existance of file1, and displays the interface
- user selects something on the interface
- cptr_application is creating file2 with content2b, where content2b reflects the answer
- cnc_program is reading content2b from file2, and will do something based on user selection on interface

i hope is clear so far

[deadlykitten]

- cnc_program creates file1 with random content
- cptr_application detects the existance of file1, and displays the interface
... computer application is not visible, but always active in background; it is searching for file1 at specific time intervals
... once file1 is detected, aplication interface becomes visible
- user selects something on the interface
- cptr_application is creating file2 with content2b, where content2b reflects the answer
... after this step, aplication interface dissapears; it is no longer possible to focus it
- cnc_program is reading content2b from file2, and will do something based on user selection on interface
... after creation of file1, cnc_program will enter a loop, and stay there until content2b from file2 is detected
... there is a delay between interface pop-up and user reply, and in this delay a lot of loops will occur
... this means that the control may trigger an error if file2 is not there
... to handle this case, file2 must be present before interface pop-up

[deadlykitten]

- cnc_program creates file2 with content content2a
- cnc_program creates file1 with random content
- cptr_application detects the existance of file1, and displays the interface
... computer application is not visible, but always active in background; it is searching for file1 at specific time intervals
... once file1 is detected, aplication interface becomes visible
- user selects something on the interface
- cptr_application is creating file2 with content2b, where content2b reflects the answer
... content 2b is different than content 2a; thus content 2a is neutral
... after this step, aplication interface dissapears; it is no longer possible to focus it
- cnc_program is reading content2b from file2, and will do something based on user selection on interface
... after creation of file1, cnc_program will enter a loop, and stay there until content2b from file2 is detected
... there is a delay between interface pop-up and user reply, and in this delay a lot of loops will occur
... this means that the control may trigger an error if file2 is not there
... to handle this case, file2 must be present before interface pop-up
... cnc_program will exit the loop when content of file2 is different than content 2a

---

for things to work so far, it is critical that these 2 actions :
... cptr_application creating file2
... cnc_program reading file2
...... are not hapening simultaneously

actually, it is critical that there is no intersection in time between their execution window

[deadlykitten]

- cnc_program creates file2 with content content2a
- cnc_program creates file1 with random content
- cptr_application detects the existance of file1, and displays the interface
... computer application is not visible, but always active in background; it is searching for file1 at specific time intervals
... once file1 is detected, aplication interface becomes visible
- user selects something on the interface
- cptr_application is creating file2 with content2b, where content2b reflects the answer
... content 2b is different than content 2a; thus content 2a is neutral
... after this step, aplication interface dissapears; it is no longer possible to focus it
- cnc_program is reading content2b from file2, and will do something based on user selection on interface
... after creation of file1, cnc_program will enter a loop, and stay there until content2b from file2 is detected
... this loop contains the folowing actions :
...... creation of file1
...... dwell / tempo long enough for the cptr_aplication to create file2
...... reading of file2
... there is a delay between interface pop-up and user reply, and in this delay a lot of loops will occur
... this means that the control may trigger an error if file2 is not there
... to handle this case, file2 must be present before interface pop-up
... cnc_program will exit the loop when content of file2 is different than content 2a

[deadlykitten]

- cnc_program creates file2 with content content2a
- cnc_program creates file1 with random content
- cptr_application detects the existance of file1, and displays the interface
... computer application is not visible, but always active in background; it is searching for file1 at specific time intervals
... once file1 is detected, aplication interface becomes visible
- user selects something on the interface
- cptr_application is creating file2 with content2b, where content2b reflects the answer
... above action does not occur imediatly after user interaction with interface
... cptr_aplication will enter a loop, detecting the creation of file 1
... once detection occurs, file2 is saved on the hdd during the dwell created by the cnc_program
... content 2b is different than content 2a; thus content 2a is neutral
... after this step, aplication interface dissapears; it is no longer possible to focus it
- cnc_program is reading content2b from file2, and will do something based on user selection on interface
... after creation of file1, cnc_program will enter a loop, and stay there until content2b from file2 is detected
... this loop contains the folowing actions :
...... creation of file1
...... dwell / tempo long enough for the cptr_aplication to create file2
...... reading of file2
... there is a delay between interface pop-up and user reply, and in this delay a lot of loops will occur
... this means that the control may trigger an error if file2 is not there
... to handle this case, file2 must be present before interface pop-up
... cnc_program will exit the loop when content of file2 is different than content 2a

[deadlykitten]

- cnc_program creates file2 with content content2a
- cnc_program creates file1 with random content
- cptr_application detects the existance of file1, and displays the interface
... computer application is not visible, but always active in background; it is searching for file1 at specific time intervals
... once file1 is detected, aplication interface becomes visible
- user selects something on the interface
- cptr_application is creating file2 with content2b, where content2b reflects the answer
... above action does not occur imediatly after user interaction with interface
... cptr_aplication will enter a loop, detecting the creation of file 1
... once detection occurs, file2 is saved on the hdd during the dwell created by the cnc_program
... content 2b is different than content 2a; thus content 2a is neutral
... after this step, aplication interface dissapears; it is no longer possible to focus it
- cnc_program is reading content2b from file2, and will do something based on user selection on interface
... after creation of file1, cnc_program will enter a loop, and stay there until content2b from file2 is detected
... this loop contains the folowing actions :
...... creation of file1
...... dwell / tempo long enough for the cptr_aplication to create file2
...... reading of file2
... there is a delay between interface pop-up and user reply, and in this delay a lot of loops will occur
... this means that the control may trigger an error if file2 is not there
... to handle this case, file2 must be present before interface pop-up
... cnc_program will exit the loop when content of file2 is different than content 2a
- after cnc_program exits the loop, will create file3, thus it is telling that he no longer needs file2
- cptr_aplication detects the creation of file 3, and deletes all comunication files : file1, file2, file3

[deadlykitten]

so lets warm welcome the newest resource file :

OCOMM

    FWRITC com-2.txt;A
    PUT '0'
    WRITE C
    CLOSE C

    NLOOP FWRITC com-1.txt;A
          PUT ' '
          WRITE C
          CLOSE C

          G04 F0.125
          V32=VDIN[1001]

          FOPENA com-2.txt
          READ A
          GET V32,1
          CLOSE A

    IF [ V32 EQ 0 ] NLOOP ( passive answer waiting )

    FWRITC com-3.txt;A
    PUT ' '
    WRITE C
    CLOSE C

RTS

a new path is opened

[deadlykitten]

hello again / full infos, on this thing, consists of :
... general idea, how things chain, etc ( presented at the begining of this thread )
... materialization of this idea, for the :
...... cnc program ( shared as a soubroutine* in previous post )
...... computer aplication ( will be shared soon as pseudocode )

this should be enough, so anyone to have a list with the requirements to build a similar thing

---

(*) code for ocomm, thus O_name + RTS, technically speaking, is a soubroutine ... but i dont regard it this way i like to call it a procedure, or more precise, a resource, because its content is not particular like a direct machinining code, but general

i keep its content inside res-ocomm-v1.ssb

here is a sample about using it :

    N1 hey whats up ? you got it so far ?
    N2 CALL OCOMM ( returns user selection, on interface, inside common variable V32 )
    N3 do something based on V32

this sample looks simple and it works as it should

[deadlykitten]

there is an issue : comunication is based on files being written to the hdd, and this is too much only for this purpose

i wish to acces some system variables,or something, that is not stored on the hdd, but inside flash memory

API may allow acces to such variables, but this does not mean that their content is not saved on the hdd

i need volatile cnc control variables / please, maybe someone has a clue ?

it would be great to do it without API

[deadlykitten]

hey Kurmay, good to see you i found some links, i will check them out ... so far i really have no clue

i guess this is your playground

[deadlykitten]

hey kurmay, i have been thinking about it ... i have never used d300 win before, and after reading your reply, i googled it and download it

and a few days after, i have seen that it is actually installed on the cnc

please, i would apreciate a quick tutorial like maybe you will be using a screen recorder and show the functionalities of the d300win ? please?

but even so, lets say that i will find the list of all variables ... how do i know which ones are on flash memory, and which ones are on the hdd ?

so, in the end, is d300win a solution ?

[deadlykitten]

oau, there are variables

please kurmay, for what are you using this tool ? there is nothing about it inside digital or printed manuals ...

my only idea is to use it for the VDIN/VDOUT; is it possible ?

ps : is it an ikos ? kindly !