osp300 : prevent read ahead


Results 1 to 2 of 2

Thread: osp300 : prevent read ahead

  1. #1
    Member deadlykitten's Avatar
    Join Date
    Jun 2015
    Location
    Antarctica
    Posts
    4154
    Downloads
    0
    Uploads
    0

    Default osp300 : prevent read ahead

    hello boys & girls

    [ lathe ]

    ... VRSTT , VLMON , M331 , ...=VDIN[1001] ( or =VDIN[100#], but i have not tested it )
    ...... M331 is there exactly for this ( buffering prohibit )
    ...... VDIN[1001] is time based, so it makes sense to act this way
    ......... what i don't understand is why VRSTT and VLMON also delivers this behaviour does anybody has a clue ?

    and there may be other codes, like this :
    ... G136 M12
    ... rapid X Z M203 M05 M63
    ...... about these last 2, i have observed that they prevent read ahead, but i am not sure and i wont dig this, since 1st enumaration is more than enough

    [ mill ]

    ... same codes as on lathe, but without VLMON and M331 ( another "team vs team" )
    ... also there is a parameter setting : "nc optional para : program buffering : does / does not", which delivers global / permanent behaviour



    please, what are the situations when you need to prevent read ahead ? kindly

    Similar Threads:
    we are merely at the start of " Internet of Things / Industrial Revolution 4.0 " era : a mix of AI, plastics, human estrangement, powerful non-state actors ...


  2. #2
    Member deadlykitten's Avatar
    Join Date
    Jun 2015
    Location
    Antarctica
    Posts
    4154
    Downloads
    0
    Uploads
    0

    Default Re: osp300 : prevent read ahead

    hello after recent trials, i would like to share this updated enumeration :
    ... lathe : VLMON, M331 , VETF*, VSIO*
    ... mill : VWKA* , VWKB*, VINP*
    ... both : VRSTT, common_variable=VDIN[1001]

    as a conclusion, buffer prohibiting seems to be delivered by many variables

    i have runned trials, because i felt that not only VDIN should prohibit read-ahead, but also VINP* ... and it seems that there are many more



    even if a variable prohibits the buffer, this does not mean that it's value is updated when execution position reaches it

    N1 G01 in_position
    N2 compensation activated
    N3 moving in compensation
    N4 compensation deactivated
    N5 VSIO* > here : VSIO* wont reflect a position after compensation, but before N2 buffer will be prohibited, but machine wont move as desired

    [ buffer prohibit ] and [ variable content update moment ] should be regarded with caution

    if in doubts, i recomend VDIN kindly !

    we are merely at the start of " Internet of Things / Industrial Revolution 4.0 " era : a mix of AI, plastics, human estrangement, powerful non-state actors ...


Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


About CNCzone.com

    We are the largest and most active discussion forum for manufacturing industry. The site is 100% free to join and use, so join today!

Follow us on


Our Brands

osp300 : prevent read ahead

osp300 : prevent read ahead