586,470 active members*
3,403 visitors online*
Register for free
Login
Results 1 to 2 of 2
  1. #1
    Join Date
    Jan 2022
    Posts
    107

    Angry Expr.txt removed options??

    Why???

    Expression function '#OnInit' removed!

    Expression function '#Loop' removed!

    Expression function '#OnShutdown' removed!

    Cmd not found: 'Jog_Speed.Set'

    And why is none of my Expr.txt working anymore??????


    Why do you break all my scripts ????????????

    And where to hell are the explanations of the new functions???
    Should I guess how the following features are working??
    Thats all useless if the manual is 2 Years old and in G-Code i see "no description" everywhere.


    New: Expression commands 'serial_read', 'serial_readdata', 'serial_readbuffer'
    New: Expression command 'return'
    New: full support for serial and ModBus RTU
    Mod: Multiline expressions
    New: Full support for ExtIn board
    New: Support for "expression shortcuts"
    New: New LED options.
    Mod: Wireless handwheel macros - more features
    New: Parameters "buffer_new", "buffer_delete", "buffer_printstring", "buffer_printdata", "buffer_setstring", "buffer_setdata", "buffer_setdata16", "buffer_setdata32", "buffer_crc16", "buffer_crc32"
    New: Parameters "serial_list", "serial_info", "serial_open", "serial_config", "serial_close", "serial_write", "serial_writedata", "serial_writebuffer"
    New: CommandIDs jogStepSet and jogRoundSet
    New: Print of problematic lines in tool compensation
    New: Parameter "_hw_sim"
    New: parameter "_tool_spdfeedz_num"
    Mod: Parameters "_hw_extin1_num", "_hw_extin2_num", "_hw_extout1_num", "_hw_extout2_num"
    Mod: ExtIn and ExtOut implementation is upgraded

  2. #2
    Join Date
    Jan 2022
    Posts
    107

    Re: Expr.txt removed options??

    OK, the messages "Expression function '#OnInit' removed!" does not mean they don't exist. It means they are not executed because of errors in syntax of scripts.
    So "removed" is not the best choice for the text. Maybe "will not be executed due to errors" or "will be ignored due to errors" or something like that. So there will be no misunderstanding of that message.


    On the other side, i like the new posibility for multi line expressions. Makes live easier if they are large. But I recommend some kind of legacy support to not break everything at once.
    One option could be to detect if there are any ; in the script at all. So no ; means old single line script...

    For now that's too late, but maybe something for future changes. It is very important that at least, there is a special information in version history if there are breaking changes.

Similar Threads

  1. [TNGv2] - Expr.txt
    By PlanetCNC in forum PlanetCNC
    Replies: 14
    Last Post: 05-29-2023, 06:20 PM
  2. Expr.txt and issues with Inputs
    By mgravet in forum PlanetCNC
    Replies: 3
    Last Post: 05-30-2022, 11:22 AM
  3. Activate optional Pause in Expr.txt
    By awpross in forum PlanetCNC
    Replies: 3
    Last Post: 02-26-2022, 08:37 PM
  4. TNGv2 Expr.txt usage
    By theRat in forum PlanetCNC
    Replies: 12
    Last Post: 08-07-2020, 10:57 AM
  5. Removed BobCAM V2 and now V4 as also Removed
    By fidia in forum BobCad-Cam
    Replies: 1
    Last Post: 08-03-2015, 05:55 PM

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
  •