Home› AMX User Forum› NetLinx Studio

Annoying Notifications Error with IP Control

d_gavind_gavin Posts: 21
in NetLinx Studio
Does anyone know what this Notifications Error means? And if so, how can you get rid of it?

Line 2 (16:13:17):: SetArrayCurrent - Error 3 Tk=0x1003

Cheers,

Dan

Comments

  • AuserAuser Posts: 506
    Ok, so line 2 (or thereabouts) in one of your source files is doing something to generate that error. It is possible that set_length_array is being used with a length greater than the size of the array judging by the error message, but that's just a guess.

    Check through the source files being used to compile the system and see if there are any array operations being performed on line 2 of one of them. Obviously you're stuck if the error is being thrown by a third party NetLinx module that you're using though.
  • ProgressiveCodeProgressiveCode Posts: 64
    Auser wrote: »
    Ok, so line 2 (or thereabouts) in one of your source files is doing something to generate that error. It is possible that set_length_array is being used with a length greater than the size of the array judging by the error message, but that's just a guess.

    Check through the source files being used to compile the system and see if there are any array operations being performed on line 2 of one of them. Obviously you're stuck if the error is being thrown by a third party NetLinx module that you're using though.

    I'm sorry, but you've sent the poster on a wild goose chase. If he followed your advice. Line 2 refers to the second line in the Diagnostics window he was looking at. For example:
    Line      1 (19:26:05)::  MatrixAudioS8: ERROR: The firmware version 1.200D used needs to be updated. Some features may not work properly!
Line      2 (19:26:35)::  MatrixAudioS8: ERROR: The firmware version 1.200D used needs to be updated. Some features may not work properly!
Line      3 (19:26:42)::  Memory Available = 34630368 <54928>
Line      4 (19:27:05)::  MatrixAudioS8: ERROR: The firmware version 1.200D used needs to be updated. Some features may not work properly!
Line      5 (19:27:35)::  MatrixAudioS8: ERROR: The firmware version 1.200D used needs to be updated. Some features may not work properly!
Line      6 (19:28:05)::  MatrixAudioS8: ERROR: The firmware version 1.200D used needs to be updated. Some features may not work properly!

    As another tangent, that module error message I included in my example above... I reported it as a bug to tech support about a year ago. The module AMX_Matrix_MiSeries_Comm_dr1_0_1 repeatedly reports this error message when used with a Matrix DAS-D0404. This is still the current version of the file, and the correct module to use for the device. The firmware version is different for the DAS series vs. the MI series, which I think is probably why the error message is being generated.
  • AuserAuser Posts: 506
    @ProgressiveCode: My bad, I missed the fact that he was using notifications (don't use em much myself).

    I was thinking of console/log messages in the formats:
    18: 07-27-2011 WED 12:46:32 Interpreter
     Ref Error  ^NINTEGERARRAY  Index to large Line=68

    and
    (0000026021) Ref Error  ^NINTEGERARRAY  Index to large Line=68
(0000026021) SetVariable - Error 1 Tk=0x0000

    There's likely a line preceding the notification entry which the OP posted indicating the affected source code line number such as:
    Line      1 (12:51:06)::  Ref Error  ^NINTEGERARRAY  Index to large Line=68
Line      2 (12:51:06)::  SetVariable - Error 1 Tk=0x0000

    (I can only help so much with the partial information provided, but I'm glad you picked up my mistake.)

    Incidentally, using set_length_array or set_length_string to set the current size of an integer array beyond its bounds generates neither compiler warning, error or runtime error so that's a bum steer too.

    @d_gavin:

    I know I've seen SetArrayCurrent runtime errors like the one you posted before, but I can't remember the cause.

    If you post your code or send it to me as a link in a PM I'll take a look and see if I can help.
  • DHawthorneDHawthorne Posts: 4,584
    It drives me crazy, but I've seen many pre-packaged modules generate errors that I can't track down myself or don't have the time/inclination to track down. As long as the module works, I grind my teeth and ignore it. It's very common on AMX-supplied modules from a year or so back, and I've seen it from third-party vendors as well (Escient comes immediately to mind). It's a matter of diminishing returns.
  • ProgressiveCodeProgressiveCode Posts: 64
    Auser wrote: »
    @ProgressiveCode: My bad, I missed the fact that he was using notifications (don't use em much myself)...
    ...There's likely a line preceding the notification entry which the OP posted indicating the affected source code line number such as:
    Line      1 (12:51:06)::  Ref Error  ^NINTEGERARRAY  Index to large Line=68
Line      2 (12:51:06)::  SetVariable - Error 1 Tk=0x0000

    Sorry, if I came off sounding like a douche. I do that sometimes. :) You are correct that the code line number should have appeared in the diagnostics line preceding what the OP copy/pasted in the post.
Sign In or Register to comment.