Med_Support

Forum Replies Created

Viewing 33 posts - 199 through 231 (of 305 total)
1 2 3 … 6 7 8 9 10
  • Author
    Posts
  • July 23, 2013 at 2:27 pm in reply to: ERROR CHECK LOG! #12400
    Med_Support
    Moderator
    Gary Bamberger
    Re: ERROR CHECK LOG!
    July 23, 2013, 02:27:53 pm

    Hi Jenn,

    Thank you for posting the program and the error logs.  Let’s take a look at one of the error messages:

    07/20/2013  12:04:22 Range check error in box 5, array element O(6), program line 108

    The error message says that you are trying to access array element O(6), but the array is not large enough.  From your program here is the declaration for Array O:

    DIM G=119, H=19, O=5, X=50000, Y=50000

    O has been declared to be an array with elements 0-5.  Element 6 is beyond the size of the array.

    You need to increase the size of array O so that it can hold all of the data that could be generated while the program is running.

    The error log lists error messages up to element O(10) so you should increase it to at least 10 and probably bigger.

    I hope that this information helps.  Please let me know if you have any other questions or need more info.
    Gary

    July 23, 2013 at 2:01 pm in reply to: ERROR CHECK LOG! #12396
    Med_Support
    Moderator
    jenn_op
    Re: ERROR CHECK LOG!
    July 23, 2013, 02:01:45 pm
    log 20 (day 7)
7 20 2013
07/20/2013  11:51:26 Driver Code: 0    DIG704_GET_ISR_MODE- Completed Successfully
07/20/2013  11:51:26 Driver Code: 0    DIG704_SET_RESOLUTION- Completed Successfully
07/20/2013  11:51:26 Driver Code: 0    DIG704_REGISTER- Completed Successfully
07/20/2013  11:51:26 Driver Code: 0    DIG704_GETVERSION- Completed Successfully
07/20/2013  11:51:26 Driver version: 1.7 0
07/20/2013  11:51:27 Driver Code: 0    DIG704_GET_IOBASE- Completed Successfully
07/20/2013  11:51:27 Base address reported by driver = 768
07/20/2013  11:51:27 Driver Code: 0    DIG704_GET_IRQ- Completed Successfully
07/20/2013  11:51:27 IRQ reported by driver = 3
07/20/2013  11:51:27 Driver Code: 0    DIG704_IN_PORT- Completed Successfully
07/20/2013  11:51:27 Driver Code: 0    DIG704_START_TIMER- Completed Successfully
07/20/2013  11:51:27 System Loaded
07/20/2013  11:57:45 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  4 SUBJ EI1 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/20/2013  11:57:45  Box  4 loaded.  Subj: EI1  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
07/20/2013  11:57:45 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  4 EI1FI120ES1.
07/20/2013  11:57:45  FILENAME BOX 4 EI1FI120ES1.
07/20/2013  11:57:45  FILENAME BOX 4 EI1FI120ES1.
07/20/2013  11:57:45 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/20/2013  11:57:46  DELAY 250
07/20/2013  11:57:46 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  5 SUBJ EI2 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/20/2013  11:57:46  Box  5 loaded.  Subj: EI2  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
07/20/2013  11:57:46 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  5 EI2FI120ES1.
07/20/2013  11:57:46  FILENAME BOX 5 EI2FI120ES1.
07/20/2013  11:57:46  FILENAME BOX 5 EI2FI120ES1.
07/20/2013  11:57:46 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/20/2013  11:57:46  DELAY 250
07/20/2013  11:57:46 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  6 SUBJ EI3 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/20/2013  11:57:46  Box  6 loaded.  Subj: EI3  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
07/20/2013  11:57:46 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  6 EI3FI120ES1.
07/20/2013  11:57:46  FILENAME BOX 6 EI3FI120ES1.
07/20/2013  11:57:46  FILENAME BOX 6 EI3FI120ES1.
07/20/2013  11:57:46 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/20/2013  11:57:46  DELAY 250
07/20/2013  11:57:46 (FI120-INTRUSIVO-ES1.MAC)START BOXES  4 5 6
07/20/2013  11:57:46  START BOXES 4 5 6
07/20/2013  11:57:46 PLAYMACRO C:\MED-PC IV\MACRO\FI120-INTRUSIVO-ES1.MAC
07/20/2013  11:58:04 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  4 SUBJ EI1 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/20/2013  11:58:04 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  4 EI1FI120ES1.
07/20/2013  11:58:04  FILENAME BOX 4 EI1FI120ES1.
07/20/2013  11:58:04  FILENAME BOX 4 EI1FI120ES1.
07/20/2013  11:58:04 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/20/2013  11:58:05  DELAY 250
07/20/2013  11:58:05 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  5 SUBJ EI2 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/20/2013  11:58:05 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  5 EI2FI120ES1.
07/20/2013  11:58:05  FILENAME BOX 5 EI2FI120ES1.
07/20/2013  11:58:05  FILENAME BOX 5 EI2FI120ES1.
07/20/2013  11:58:05 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/20/2013  11:58:05  DELAY 250
07/20/2013  11:58:05 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  6 SUBJ EI3 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/20/2013  11:58:05 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  6 EI3FI120ES1.
07/20/2013  11:58:05  FILENAME BOX 6 EI3FI120ES1.
07/20/2013  11:58:05  FILENAME BOX 6 EI3FI120ES1.
07/20/2013  11:58:05 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/20/2013  11:58:05  DELAY 250
07/20/2013  11:58:05 (FI120-INTRUSIVO-ES1.MAC)START BOXES  4 5 6
07/20/2013  11:58:05  START BOXES 4 5 6
07/20/2013  11:58:05 PLAYMACRO C:\MED-PC IV\MACRO\FI120-INTRUSIVO-ES1.MAC
07/20/2013  11:58:40 MODIFY_IDENTIFIERS BOX 4 SUBJECT EI1  EXPERIMENT 0  GROUP 0 
07/20/2013  11:58:40 FILENAME BOX 4 EI1FI120ES1.6(2)
07/20/2013  11:58:48 MODIFY_IDENTIFIERS BOX 5 SUBJECT EI2  EXPERIMENT 0  GROUP 0 
07/20/2013  11:58:48 FILENAME BOX 5 EI2FI120ES1.6(2)
07/20/2013  11:58:56 MODIFY_IDENTIFIERS BOX 6 SUBJECT EI3  EXPERIMENT 0  GROUP 0 
07/20/2013  11:58:56 FILENAME BOX 6 EI3FI120ES1.6(2)
07/20/2013  11:59:02 MODIFY_IDENTIFIERS BOX 6 SUBJECT EI3  EXPERIMENT 0 GROUP 0
07/20/2013  11:59:02 FILENAME BOX 6 EI3FI120ES1.6(2)
07/20/2013  12:04:22 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:22 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:23 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:23 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:23 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:23 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:24 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:24 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:24 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:24 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:25 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:26 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:26 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:26 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:26 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:26 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:26 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:27 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:27 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:27 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:27 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:27 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:27 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:28 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:28 Range check error in box 4, array element O(6), program line 108
07/20/2013  12:04:28 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:28 Range check error in box 5, array element O(6), program line 108
07/20/2013  12:04:28 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:04:28 Range check error in box 6, array element O(6), program line 108
07/20/2013  12:06:44 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:44 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:44 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:44 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:44 Range check error in box 6, array element O(8), program line 108
07/20/2013  12:06:44 Range check error in box 6, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 6, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 6, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:45 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 6, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 6, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 6, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 6, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:46 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:47 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:47 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:47 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:47 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:47 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:47 Range check error in box 4, array element O(8), program line 108
07/20/2013  12:06:47 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:47 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:48 Range check error in box 5, array element O(8), program line 108
07/20/2013  12:06:48 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:06:48 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:06:48 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:06:49 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:06:49 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:06:49 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:06:49 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:09:03 Range check error in box 4, array element O(10), program line 108
 07/20/2013  12:09:03 Range check error in box 4, array element O(10), program line 108
 07/20/2013  12:09:03 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:03 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:04 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:04 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:05 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:05 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:06 Range check error in box 4, array element O(10), program line 108
 07/20/2013  12:09:06 Range check error in box 4, array element O(10), program line 108
 07/20/2013  12:09:06 Range check error in box 6, array element O(10), program line 108
 07/20/2013  12:09:06 Range check error in box 6, array element O(10), program line 108
 07/20/2013  12:09:06 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:06 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:06 Range check error in box 4, array element O(10), program line 108
 07/20/2013  12:09:06 Range check error in box 4, array element O(10), program line 108
 07/20/2013  12:09:07 Range check error in box 6, array element O(10), program line 108
 07/20/2013  12:09:07 Range check error in box 6, array element O(10), program line 108
 07/20/2013  12:09:07 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:09:07 Range check error in box 5, array element O(10), program line 108
 07/20/2013  12:26:23 LOG_OPTIONS KEYBOARD ON MACROS ON ERRORS ON BOXES ON
 07/20/2013  12:36:32 STOPKILL BOXES 4 5 6
 07/20/2013  12:36:40 System Shutdown
 07/20/2013  12:36:59 Driver Code: 0    DIG704_GET_ISR_MODE- Completed Successfully
 07/20/2013  12:36:59 Driver Code: 0    DIG704_SET_RESOLUTION- Completed Successfully
 07/20/2013  12:36:59 Driver Code: 0    DIG704_REGISTER- Completed Successfully
 07/20/2013  12:36:59 Driver Code: 0    DIG704_GETVERSION- Completed Successfully
 07/20/2013  12:36:59 Driver version: 1.7 0
 07/20/2013  12:36:59 Driver Code: 0    DIG704_GET_IOBASE- Completed Successfully
 07/20/2013  12:36:59 Base address reported by driver = 768
 07/20/2013  12:36:59 Driver Code: 0    DIG704_GET_IRQ- Completed Successfully
 07/20/2013  12:36:59 IRQ reported by driver = 3
 07/20/2013  12:36:59 Driver Code: 0    DIG704_IN_PORT- Completed Successfully
 07/20/2013  12:36:59 Driver Code: 0    DIG704_START_TIMER- Completed Successfully
 07/20/2013  12:36:59 System Loaded
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  4 SUBJ EI1 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
 07/20/2013  12:37:48  Box  4 loaded.  Subj: EI1  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  4 EI1FI120ES1.
 07/20/2013  12:37:48  FILENAME BOX 4 EI1FI120ES1.
 07/20/2013  12:37:48  FILENAME BOX 4 EI1FI120ES1.
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
 07/20/2013  12:37:48  DELAY 250
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  5 SUBJ EI2 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
 07/20/2013  12:37:48  Box  5 loaded.  Subj: EI2  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  5 EI2FI120ES1.
 07/20/2013  12:37:48  FILENAME BOX 5 EI2FI120ES1.
 07/20/2013  12:37:48  FILENAME BOX 5 EI2FI120ES1.
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
 07/20/2013  12:37:48  DELAY 250
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  6 SUBJ EI3 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
 07/20/2013  12:37:48  Box  6 loaded.  Subj: EI3  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  6 EI3FI120ES1.
 07/20/2013  12:37:48  FILENAME BOX 6 EI3FI120ES1.
 07/20/2013  12:37:48  FILENAME BOX 6 EI3FI120ES1.
 07/20/2013  12:37:48 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
 07/20/2013  12:37:49  DELAY 250
 07/20/2013  12:37:49 (FI120-INTRUSIVO-ES1.MAC)START BOXES  4 5 6
 07/20/2013  12:37:49  START BOXES 4 5 6
 07/20/2013  12:37:49 PLAYMACRO C:\MED-PC IV\MACRO\FI120-INTRUSIVO-ES1.MAC
 07/20/2013  12:44:24 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:24 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:24 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:24 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:25 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:25 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:25 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:25 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:26 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:26 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:26 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:26 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:27 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:27 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:27 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:27 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:27 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:27 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:28 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:28 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:29 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:29 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:29 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:29 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:30 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:30 Range check error in box 5, array element O(6), program line 108
 07/20/2013  12:44:31 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:31 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:32 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:32 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:32 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:32 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:34 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:34 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:34 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:34 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:34 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:34 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:34 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:34 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:35 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:35 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:35 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:35 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:36 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:36 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:36 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:36 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:36 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:36 Range check error in box 4, array element O(6), program line 108
 07/20/2013  12:44:37 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:37 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:38 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:38 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:38 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:44:38 Range check error in box 6, array element O(6), program line 108
 07/20/2013  12:45:54 LOG_OPTIONS KEYBOARD ON MACROS ON ERRORS ON BOXES ON
 07/20/2013  12:46:45 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:45 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:46 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:46 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:46 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:46 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:47 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:47 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:47 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:47 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:48 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:48 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:49 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:49 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:50 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:50 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:51 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:51 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:51 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:51 Range check error in box 5, array element O(8), program line 108
 07/20/2013  12:46:51 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:51 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:52 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:52 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:53 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:46:53 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:46:53 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:53 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:53 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:53 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:54 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:54 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:54 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:46:54 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:46:55 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:46:55 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:46:55 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:55 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:56 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:46:56 Range check error in box 6, array element O(8), program line 108
 07/20/2013  12:46:56 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:56 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:56 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:46:56 Range check error in box 4, array element O(8), program line 108
 07/20/2013  12:49:16 LOG_OPTIONS KEYBOARD ON MACROS ON ERRORS ON BOXES ON
 07/20/2013  12:54:11 STOPKILL BOXES 4 5 6
 07/20/2013  12:54:13 System Shutdown
    July 23, 2013 at 2:00 pm in reply to: ERROR CHECK LOG! #12394
    Med_Support
    Moderator
    jenn_op
    Re: ERROR CHECK LOG!
    July 23, 2013, 02:00:34 pm
    \OUTPUTS
 ^HL=5
 ^FEEDER=4
 ^VENT=6
 ^WN=7
 ^LUZ=3
 ^TONO=1

\DIMENSIONES
 DIM G=119, H=19, O=5, X=50000, Y=50000

S.S.1,
 S1,
 #START: ON ^HL; ON ^WN ---> S3

S2,
 #Z1:---> S3

S3,
 1": ADD A; SHOW 1, FI, A; IF A>= 120 [@SI,@NO]
 @SI:SET A=0 --->S4
 @NO:--->S3

S4,
 #R2: ADD B;SHOW 2, Rs-FI,B; Z2;Z3--->S2



S.S.2,
 S1,
 #Z1:---> S2

#START: ---> S2

S2,
 114": ON ^TONO; ADD N; SHOW 6, INICIO ESTIMULO, N; Z5 ---> S3

S3,
 6": OFF ^TONO ---> S1

s4,
 #R2: ADD Q; SHOW 8, Rs EN EL ESTIMULO, Q; Z6--->SX



S.S.3,
 S1,
 #Z2:--->S2

S2,
 1": ADD D; SHOW 3, T-ACCESO, D; IF D >=20 [@YES,@NOT]
 @YES:SET D=0; Z1--->S1
 @NOT:--->S2

S.S.4,
 S1,
 #Z2:ON ^TONO --->S2
 #Z1:OFF ^TONO---> S1
 S2,
 1": OFF ^TONO --->S3
 #Z1:OFF ^TONO---> S1
 S3,
 1": ON ^TONO --->S2
 #Z1:OFF ^TONO---> S1



S.S.5,
 S1,
 #Z1:--->S2

S2,
 #R2: SET G(A)=G(A)+1;ADD B; SHOW 2, Rs-FI,B; Z3 --->SX
 #Z2: --->S1

S.S.6,
 S1,
 #Z5:--->S2

S2,
 #R2:SET O(N)=O(N)+1;ADD Q; SHOW 7, RS EN EL ESTIMULO, Q; Z6 --->SX
 #Z2: --->S1

S.S.7,
 S1,
 #Z2:--->S2

S2,
 #R2: SET H(D)=H(D)+1;ADD E;SHOW 9, Rs-Acceso,E; ON ^FEEDER;Z4 --->S3
 #Z1: OFF ^FEEDER --->S1

S3,
 0.1": OFF ^FEEDER; ADD C; SHOW 4, COMIDAS, C ---> S2
 #Z1: OFF ^FEEDER ---> S1



S.S.8,
 S1,
 #START:--->S2

S2,
 1": ADD F;SHOW 5, TIEMPO, F; IF F >= 7200 [@SIPI,@NOPI]
 @SIPI: --->STOPABORTFLUSH
 @NOPI: --->S2



S.S.9 ,\ REAL TIME
 s1,
 #start: set x(z)=-987.987;set y(z)=-987.987---> s2
 s2,
 #z1: ADD J; set x(z)=1;set y(z)=I; set z=z+1;set x(z)=-987.987;set y(z)=-987.987---> sx
 #z2: ADD K; set x(z)=2;set y(z)=I; set z=z+1;set x(z)=-987.987;set y(z)=-987.987---> sx
 #z3: ADD L; set x(z)=3;set y(z)=I; set z=z+1;set x(z)=-987.987;set y(z)=-987.987---> sx
 #z4: ADD M; set x(z)=4;set y(z)=I; set z=z+1;set x(z)=-987.987;set y(z)=-987.987---> sx
 #z5: ADD N; set x(z)=5;set y(z)=I; set z=z+1;set x(z)=-987.987;set y(z)=-987.987---> sx
 #z6: ADD Q; set x(z)=6;set y(z)=I; set z=z+1;set x(z)=-987.987;set y(z)=-987.987---> sx
 .1": add I --->sx

     

    July 23, 2013 at 1:53 pm in reply to: ERROR CHECK LOG! #12392
    Med_Support
    Moderator
    jenn_op
    Re: ERROR CHECK LOG!
    July 23, 2013, 01:53:48 pm
    log 19 (day 6):
7 19 2013
07/19/2013  11:39:53 Driver Code: 0    DIG704_GET_ISR_MODE- Completed Successfully
07/19/2013  11:39:53 Driver Code: 0    DIG704_SET_RESOLUTION- Completed Successfully
07/19/2013  11:39:53 Driver Code: 0    DIG704_REGISTER- Completed Successfully
07/19/2013  11:39:53 Driver Code: 0    DIG704_GETVERSION- Completed Successfully
07/19/2013  11:39:53 Driver version: 1.7 0
07/19/2013  11:39:53 Driver Code: 0    DIG704_GET_IOBASE- Completed Successfully
07/19/2013  11:39:53 Base address reported by driver = 768
07/19/2013  11:39:53 Driver Code: 0    DIG704_GET_IRQ- Completed Successfully
07/19/2013  11:39:53 IRQ reported by driver = 3
07/19/2013  11:39:53 Driver Code: 0    DIG704_IN_PORT- Completed Successfully
07/19/2013  11:39:54 Driver Code: 0    DIG704_START_TIMER- Completed Successfully
07/19/2013  11:39:54 System Loaded
07/19/2013  11:53:23 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  4 SUBJ EI1 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/19/2013  11:53:24  Box  4 loaded.  Subj: EI1  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  4 EI1FI120ES1.
07/19/2013  11:53:24  FILENAME BOX 4 EI1FI120ES1.
07/19/2013  11:53:24  FILENAME BOX 4 EI1FI120ES1.
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/19/2013  11:53:24  DELAY 250
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  5 SUBJ EI2 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/19/2013  11:53:24  Box  5 loaded.  Subj: EI2  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  5 EI2FI120ES1.
07/19/2013  11:53:24  FILENAME BOX 5 EI2FI120ES1.
07/19/2013  11:53:24  FILENAME BOX 5 EI2FI120ES1.
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/19/2013  11:53:24  DELAY 250
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC) LOAD BOX  6 SUBJ EI3 EXPT 0 GROUP 0 PROGRAM FI120-ES1-INTER
07/19/2013  11:53:24  Box  6 loaded.  Subj: EI3  Expt: 0  Grp: 0  Pgm: FI120-ES1-INTER
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC)FILENAME BOX  6 EI3FI120ES1.
07/19/2013  11:53:24  FILENAME BOX 6 EI3FI120ES1.
07/19/2013  11:53:24  FILENAME BOX 6 EI3FI120ES1.
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC)DELAY 250
07/19/2013  11:53:24  DELAY 250
07/19/2013  11:53:24 (FI120-INTRUSIVO-ES1.MAC)START BOXES  4 5 6
07/19/2013  11:53:24  START BOXES 4 5 6
07/19/2013  11:53:24 PLAYMACRO C:\MED-PC IV\MACRO\FI120-INTRUSIVO-ES1.MAC
07/19/2013  11:53:44 MODIFY_IDENTIFIERS BOX 4 SUBJECT EI1  EXPERIMENT 0  GROUP 0 
07/19/2013  11:53:44 FILENAME BOX 4 EI1FI120ES1.6(6)
07/19/2013  11:53:49 MODIFY_IDENTIFIERS BOX 5 SUBJECT EI2  EXPERIMENT 0  GROUP 0 
07/19/2013  11:53:49 FILENAME BOX 5 EI2FI120ES1.6(6)
07/19/2013  11:53:57 MODIFY_IDENTIFIERS BOX 6 SUBJECT EI3  EXPERIMENT 0  GROUP 0 
07/19/2013  11:53:57 FILENAME BOX 6 EI3FI120ES1.6(6)
07/19/2013  11:54:01 MODIFY_IDENTIFIERS BOX 5 SUBJECT EI2  EXPERIMENT 0 GROUP 0
07/19/2013  11:54:01 FILENAME BOX 5 EI2FI120ES1.6(6)
07/19/2013  11:59:59 Range check error in box 5, array element O(6), program line 108
07/19/2013  11:59:59 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:00 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:00 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:01 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:01 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:01 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:01 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:01 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:01 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:02 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:02 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:03 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:03 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:03 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:03 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:03 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:03 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:04 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:05 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:05 Range check error in box 6, array element O(6), program line 108
07/19/2013  12:00:05 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:05 Range check error in box 5, array element O(6), program line 108
07/19/2013  12:00:06 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:06 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:06 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:06 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:06 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:06 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:08 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:00:08 Range check error in box 4, array element O(6), program line 108
07/19/2013  12:02:20 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:20 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:21 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:21 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:21 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:21 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:21 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:21 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:22 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:22 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:22 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:22 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:22 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:22 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:23 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:23 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:23 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:23 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:24 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:24 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:24 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:24 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:24 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:24 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:25 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 6, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 5, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:26 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:28 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:02:28 Range check error in box 4, array element O(8), program line 108
07/19/2013  12:04:41 Range check error in box 5, array element O(10), program line 108
07/19/2013  12:04:41 Range check error in box 5, array element O(10), program line 108
07/19/2013  12:04:42 Range check error in box 6, array element O(10), program line 108
07/19/2013  12:04:42 Range check error in box 6, array element O(10), program line 108
07/19/2013  12:04:42 Range check error in box 5, array element O(10), program line 108
07/19/2013  12:04:42 Range check error in box 5, array element O(10), program line 108
07/19/2013  12:52:54 LOG_OPTIONS KEYBOARD ON MACROS ON ERRORS ON BOXES ON
07/19/2013  13:53:26 BOX: STOPABORTFLUSH BOXES 4
07/19/2013  13:53:26 BOX: STOPABORTFLUSH BOXES 5
07/19/2013  13:53:26 BOX: STOPABORTFLUSH BOXES 6
07/19/2013  14:02:24 System Shutdown
    July 22, 2013 at 3:57 pm in reply to: ERROR CHECK LOG! #12389
    Med_Support
    Moderator
    Gary Bamberger
    Re: ERROR CHECK LOG!
    July 22, 2013, 03:57:58 pm

    Hello Jenn,

    Please email me a copy of the program that you are running and the log file(s) from the day(s) the error happened. You can find the log file(s) in the C:\MED-PC IV\Logfiles folder. If the problem happend on July 20th, then I would want the LOG20 file. If the problem happened on July 21st, then I would want the LOG21 file. Etc.

    Once I have a copy of the program and the log files I should be able to figure out what happened.

    Gary

    May 22, 2013 at 12:57 pm in reply to: shared code doesnt work #12586
    Med_Support
    Moderator
    Gary Bamberger

    Glad to hear that it is now working.

    Gary

    May 22, 2013 at 11:55 am in reply to: shared code doesnt work #12584
    Med_Support
    Moderator
    andersem

    It works! Thanks so much for the help. I did not realize that the acclimation period was written into the code and was not patient enough to let it run for five minutes. Thanks for your help again!

     

    Eden

    May 22, 2013 at 9:30 am in reply to: shared code doesnt work #12582
    Med_Support
    Moderator
    andersem

    Gary, thanks for the help again. I had attached the program in the initial post. Thanks!

    May 21, 2013 at 2:17 pm in reply to: shared code doesnt work #12580
    Med_Support
    Moderator
    Gary Bamberger

    Hello,
    Unfortunately I don’t have enough information to be able to tell you what the exact problem is, but maybe I can give you a troubleshooting tip:

    After you START the program in MED-PC IV you can go to menu “View | State Sets.” This will list the State that each State Set is in. This may give you a clue as to where the program is stuck.

    In order to help any further I would need a copy of the program.
    Gary

    May 13, 2013 at 12:08 pm in reply to: VI -90seconds #13042
    Med_Support
    Moderator
    Gary Bamberger

    A typical Variable Interval procedure is the program waits for the interval to pass and then reinforces the first/next response.  If I understand you correctly what you are describing is a Variable Time procedure.  That is where you wait a variable amount time to pass and then dispense a pellet.  The lever is ignored.  There is no punishment or reward for pressing the lever.  In that case just remove the code for the Left Lever.

    ^Pellet     = 3
^HouseLight = 7

LIST Z = 60", 70", 80", 90", 100", 110", 120"

S.S.1,
S1,
#START: ON ^HouseLight; RANDD Y = Z ---> S2

S2,
Y#T: ON ^Pellet; ADD D ---> S4

S4,
0.05": OFF ^Pellet;
IF A >= 50 [@MaxPellets, @Cont]
@Max: Z32 ---> S1
@Cont: RANDD Y = Z ---> S2

S.S.2,
S1,
#START: ---> S2

S2,
25':  ---> STOPABORTFLUSH
#Z32: ---> STOPABORTFLUSH

    To the program the lever is just an output.  To get the lever to extend you just need to turn on the appropriate output (Ex: ON 1).  To get the lever to retract you turn off the output (Ex: OFF 1).

    If the pellet is not dispensing, then you need to either connect the pellet dispenser to output 3 or change the ^Pellet constant to match the output that your pellet is connected to.  The same would be true for extending the lever.

    Gary

    May 13, 2013 at 11:13 am in reply to: VI -90seconds #13040
    Med_Support
    Moderator
    andersem

    More questions for you Gary,

    If there is no correct lever, do I need the response on the left lever code? Can I delete S3 altogether and then the pellets will automatically come out regardless of a response on a lever (there were not automatically coming out on a VI 90 with this code, the house light went on but no pellets)? Also, what is the code to get the levers to come out or go in?

    Thanks again for your help!

    May 10, 2013 at 2:18 pm in reply to: VI -90seconds #13038
    Med_Support
    Moderator
    Gary Bamberger

    Z pulses are a way of communicating between State Sets. In this case when the maximum number of pellets have been delivered the Z32 pulse lets the other State Set know that this has happened and that the program should end.

    May 10, 2013 at 2:12 pm in reply to: VI -90seconds #13036
    Med_Support
    Moderator
    andersem

    WOW! Thanks so much! Likely will be posting again for the next step in the experiment. What do the Z pulses do?

    May 10, 2013 at 1:49 pm in reply to: VI -90seconds #13033
    Med_Support
    Moderator
    Gary Bamberger
    ^LeftLever  = 1
^Pellet     = 3
^HouseLight = 7
LIST Z = 60", 70", 80", 90", 100", 110", 120"
S.S.1,
S1,
#START: ON ^HouseLight; RANDD Y = Z ---> S2

S2,
Y#T: ---> S3

S3,
#R^LeftLever: ON ^Pellet; ADD D ---> S4

S4,
0.05": OFF ^Pellet;
IF A >= 50 [@MaxPellets, @Cont]
@Max: Z32 ---> S1
@Cont: RANDD Y = Z ---> S2
S.S.2,
S1,
#START: ---> S2

S2,
25':  ---> STOPABORTFLUSH
#Z32: ---> STOPABORTFLUSH
    May 9, 2013 at 1:16 pm in reply to: code to use sofcr? #13052
    Med_Support
    Moderator
    Gary Bamberger

    Hello Paulo,
    If I understand you correctly you want to have two trace pens in the upper window.  The first trace pen shows the response .10 and reinforcement .20 and the second trace pen shows punishments.  I don’t know the criteria for a punishment, but the following should work:

    \*****************************************************
\ ADD A STEP 1 ELEMENT TO ARRAY C FOR EACH PUNISHMENT
\*****************************************************
S.S.8,
S1,
#START: ---> S2

S2,     \ Wait for punishment signal
#Z1: IF I <= 10000 [@Cont, @ArrayFull]
@Cont: SET C(I) = T + 0.11, T = 0; ADD I;
IF I <= 10000 [@Cont, @ArrayFull]
@Cont: SET C(I) = -987.987 ---> SX
@Full: ---> S1
@Full: ---> S1

    So the .1 is the Step and the second number after the decimal point (1) is the Trace Pen to use.  0.11 adds a Step to Trace Pen 1.

    I hope that this helps.  Please let me know if I can help you in any other way.

    Best Regards,
    Gary

    April 26, 2013 at 12:04 pm in reply to: code to use sofcr? #13050
    Med_Support
    Moderator
    paulocmayer

    Dear Gary,

    Is there a way to have two different pens in the same curve using softcr?
    I am using a schedule of reinforcement + punishment on the same lever and I would like to see the moment these different events happened. I’ve tried using different codes ex: .1 for response; .2 for reinforcer (so far everything was ok on the curve); however to have the punishment shown I’ve tried using .3 .4 .5 .6 or .11 .12 .21 .22 and it didn’t work.

    Thank you
    Paulo

    April 23, 2013 at 11:22 am in reply to: Adding Smartcontrol card to superport cards #12471
    Med_Support
    Moderator
    ECallen

    Thanks, but on this system they are not all smartcontrol cards. I have two superport 913 input cards hooked up handling the input from the boxes infrared location sensors. They work fine. I am trying to add a third card which is Smartcontrol card to handle the outputs to the two boxes. That is the one I can’t configure to work.

    ….

    Nevermind, got it. We were using a 716D connection interface panel instead of 716B, which we need because it’s a smartcontrol card we are using for the output. Thanks to Travis for the help.

    April 23, 2013 at 10:10 am in reply to: Adding Smartcontrol card to superport cards #12469
    Med_Support
    Moderator
    Gary Bamberger

    Place Preference Systems almost always have DIG-716B SmartCtrl cards.

    How to configure SmartCtrl cards:

    Card #           Input Port           Output Offset           Offset Jumpers
    1                    780                     0                               None
    2                    781                     2                               A1
    3                    782                     4                               A2
    4                    783                     6                               A1, A2
    5                    784                     8                               A3
    6                    785                     10                             A1, A3
    7                    786                     12                             A2, A3
    8                    787                     14                             A1, A2, A3
    9                    788                     16                             A4
    10                  789                     18                             A1, A4
    11                  790                     20                             A2, A4
    12                  791                     22                             A1, A2, A4
    13                  792                     24                             A3, A4
    14                  793                     26                             A1, A3, A4
    15                  794                     28                             A2, A3, A4
    16                  795                     30                             A1, A2, A3, A4

    SmartCTL cards have an Input Offset Value that is hard coded to -1.
    SmartCTL Cards have an Output Port Value that is hard coded to 792.

    The Output Offset is important for creating your Hardware Configuration file.
    The Offset Jumpers configuration is used for changing the offset of the actual cards themselves.

     

    With two SmartCtrl cards you would have:

    Card #  Input Port  Output Offset  Offset Jumpers
    1        780            0             None
    2        781            2              A1
    * SmartCtrl cards have an Input Offset Value that is hard coded to -1
    * SmartCtrl Cards have an Output Port Value that is hard coded to 792

    So now run the MED-PC Hardware Configuration Utility.  Go to Define | Guided Sequence.  Select the last option “All cards are SmartCtrl cards.”  Enter the number of Boxes, Resolution, and that each card is a DIG-716B.
    Gary

    March 6, 2013 at 8:31 am in reply to: end program after trials #13055
    Med_Support
    Moderator
    Gary Bamberger

    So you want a certain number of trials and then the program will end.

    S.S.1,
S1,
#START: ON ^LeftLever; ADD T ---> S2

S2,
#R^LeftLever: OFF ^LeftLever; Z^Reward ---> S3
1': OFF ^LeftLever ---> S3

S3,
30": IF T >= 60 [@Done, @Cont]
@Done: ---> STOPABORTFLUSH
@Cont: ON ^LeftLever; ADD T ---> S2

    Hopefully this example demonstrates how you can accomplish what you need for your program.

    February 12, 2013 at 11:43 am in reply to: Trouble with video camera programming #13062
    Med_Support
    Moderator
    ECallen

    Thanks for the errors and advice, I’ll check the timing issue.

    …

    These changes worked great, appreciate the advice and appreciate the support of Med standing behind their product with quick help, pretty unusual these days.

    February 12, 2013 at 11:19 am in reply to: Trouble with video camera programming #13059
    Med_Support
    Moderator
    Gary Bamberger

    Hello,
    1) In S.S.2, S1 you have

    S.S.2,
S1,
#START:ON ^HOUSELIGHT; ~SET N=1--->S2

    There is a ~ that doesn’t belong.

    2) In S.S.2, S2 you have

    S2,
.1":~ConnectToVM('.', 'Box 1');
~ConnectToVM('.', 'Box 2');
~ConnectToVM('.', 'Box 3');
~ConnectToVM('.', 'Box 4');~ --->s3

    Your ~’s don’t match up evenly.  You need to change it to be:

    S2,
.1":~ConnectToVM('.', 'Box 1');
ConnectToVM('.', 'Box 2');
ConnectToVM('.', 'Box 3');
ConnectToVM('.', 'Box 4');~ --->s3

    3) S.S.2, S4 is the same problem as S2

    4) In S.S.2, S5 you have

    S5,
.1":~TONEON(MG,BOX);~SET T=0 --->s6

    You are missing a semicolon following the tilda

    S5,
.1":~TONEON(MG,BOX);~; SET T=0 --->s6

    5) In S.S.2, S6 you have

    S6,
10":~TONEOFF(MG,BOX);;~ADD N--->S7

    In this case you have the second semicolon, but it is in the wrong place

    S6,
10":~TONEOFF(MG,BOX);~; ADD N--->S7

    6) S.S.2, S7 is the same problem as S2 & S4

    7) S.S.2, S8 is the same problem as S2 & S4 & S7

    Once you correct the above problems the program will compile.
    I am a little concerned about how you are trying to control all four cameras from one program running in one Box.  You may find that you run into timing problems.  It would be better if you had one Box controlling one camera each.  Four separate programs in four Boxes.

    July 10, 2012 at 7:45 am in reply to: Overcounting #R responses #12415
    Med_Support
    Moderator
    Gary Bamberger
    Re: Overcounting #R responses
    July 10, 2012, 07:45:43 am

    You are using an internal resolution of 50ms in your program which is not very accurate. The fact that you are getting responses with 0.00s in between is not surprising. If the animal licks and then licks again 30ms later it will record a time difference of 0.00s.
    Are you certain that the animal is not licking 4000+ times. If the animal is very thirsty, then they are going to lick a lot.
    The hardware is designed to run at a 10ms resolution and in most cases can handle a 1ms resolution. Try making contact with the lickometer with your finger or breaking the photobeam if you have that type of input. Do you get more than one input when you make contact?

    June 4, 2012 at 8:59 am in reply to: counting both levers #13065
    Med_Support
    Moderator
    Gary Bamberger

    It is definitely possible to record the number of presses on both inputs. Hopefully the sample code below will help.

    ^LeftLever = 1
^RightLever = 2

S.S.1,
S1,
#R^LeftLever: ADD L; SHOW 1,Left Lever,L ---> SX
#R^RightLever: ADD R; SHOW 2,Right Lever,R ---> SX
    May 22, 2012 at 4:58 pm in reply to: variable input time #13072
    Med_Support
    Moderator
    labrat

    Thank you! That worked beautifully:)

    May 17, 2012 at 8:41 am in reply to: variable input time #13069
    Med_Support
    Moderator
    Gary Bamberger

    The best way is to create a LIST and then draw from it randomly

    LIST Z = 60", 65", 70", 75", 80", 85", 90"

S.S.1,
S1,
#START: ---> S2
S2,
#R^LeftLever: RANDD Y = Z;
OFF ^LeftLight, ^LeftLever ---> S3

S3,
Y#T: ON ^LeftLight, ^LeftLever ---> S2
    March 20, 2012 at 9:28 am in reply to: code to use sofcr? #13046
    Med_Support
    Moderator
    Gary Bamberger
    \***************************************************
\     INCREMENT TIME T FOR IRT AND EVENT ARRAY
\***************************************************
S.S.6,
S1,
#START: ---> S2

S2,     \ Increment T every 10 ms
0.01": ADD T ---> SX

 

\**************************************************************
\ ADD A STEP 0 ELEMENT TO ARRAY C FOR EACH LEFT LEVER RESPONSE
\**************************************************************
S.S.7,
S1,
#START: ---> S2

S2,
#R^LeftLever: IF I <= 10000 [@Cont, @ArrayFull]
@Cont: SET C(I) = T + 0.10, T = 0; ADD I;
IF I <= 10000 [@Cont, @ArrayFull]
@Cont: SET C(I) = -987.987 ---> SX
@Full: ---> S1
@Full: ---> S1

 

\***************************************************************
\ ADD A STEP 1 ELEMENT TO ARRAY C FOR EACH RIGHT LEVER RESPONSE
\***************************************************************
S.S.8,
S1,
#START: ---> S2

S2,
#R^RightLever: IF I <= 10000 [@Cont, @ArrayFull]
@Cont: SET C(I) = T + 0.11, T = 0; ADD I;
IF I <= 10000 [@Cont, @ArrayFull]
@Cont: SET C(I) = -987.987 ---> SX
@Full: ---> S1
@Full: ---> S1

     

    You will notice that there is two differences between S.S.7 and S.S.8:

    1) S.S.7 is looking for an input on the LeftLever
    S.S.8 is looking for an input on the RightLever

    2) S.S.7 uses the SoftCR code 0.10
    S.S.8 uses the SoftCR code 0.11

     

    The number before the decimal point is the Time Component.  It is keeping track of how much time has passed since the previous data element was recorded.

    The first number after the decimal point is the Control Code that you wish to mark.  In this case the Control Code is .1 which is a Step/Response.

    The second number after the decimal point is the Trace Line that you wish to use.  There are 10 Trace Lines (0 through 9).

    All SoftCR Control Codes work this way.

    .1 = Step
    .2 = Pip
    .3 = Reset Trace Pen
    .5 = Lower Event Pen
    .6 = Raise Event Pen

    Trace Pens are in the upper window and Event Pens are in the lower window.

     

    Please feel free to let me know if you have any other questions or need more info.

    October 24, 2011 at 4:40 pm in reply to: any way to get the state of a lever? #13081
    Med_Support
    Moderator
    mikediamond45

    yep, changing it to level mode & modifying the code worked, thx.

    October 24, 2011 at 2:30 pm in reply to: any way to get the state of a lever? #13077
    Med_Support
    Moderator
    Gary Bamberger

    The following code sample should help:

    \***************************************************
\ BEAM BREAK DEFINED - 20ms BREAK, 20ms RELEASE
\***************************************************
S.S.2, \ Beam Break Defined - 20ms Break, 20ms Release.
S1, \ Inputs in Level Mode generate an input "count" on each
\ interrupt. With a 10 ms system resolution 2 counts
\ will be reached in 20 ms. The Z3 pulse is used to
\ signal a completed Beam Break. The second statement resets
\ the counter every 20 ms so that a partial Beam Break of
\ less than 20 ms will not constitute a Response.
#R1: ADD Y; IF Y >= 2 [@BeamBreak, @NoBeamBreak]
@Break: Z3; SET Y = 0 ---> S2
@NoBreak: ---> SX
0.02": SET Y = 0 ---> S1

S2, \ As long as the Beam is broken the second statement
\ causes a re-entry to this State. This resets the
\ the internal 20 ms timer so it never times out. When
\ the Beam is released for 20 ms the timer times out
\ and a Z4 pulse signals the release.
0.02": Z4 ---> S1
#R1: ---> S2

    The code was for input beams, but it will also work for levers in level mode. All you need to do is time the length between each Z-pulse. If it is greater than 5s, issue the reward.
    Gary

    October 4, 2011 at 3:00 pm in reply to: Error message using Trans IV #13084
    Med_Support
    Moderator
    Gary Bamberger

    There are two problems here:
    1) There is a bug in one or more of the programs and it doesn’t necessarily have to be the program that you currently have open and are working on. If Trans IV sees that a program is out of date it will try to compile that program as well.
    2) Trans IV is not catching the bug in the program properly and giving you a useful error message in order to find and fix the problem.

    Here is what you need to do:
    1) Exclude all programs from compilation and then try adding them back in one at a time. When the error message reappears you know which program is causing the problem.
    2) Edit the program with the problem and comment out all but one of the most simplest State Sets.
    3) Recompile the program and make sure that the error message doesn’t reappear.
    4) Start uncommenting the State Sets one at a time until the error message reappears.
    5) Now you know which State Set is causing the problem. There may be more than one State Set with the same type of problem.
    6) You can narrow down where the problem is in the State Set even further by commenting out each State and then uncommenting them one at a time until the problem occurs. Again there may be more than one State with a similar problem.

    Once you know which State(s) is causing the problem you can then focus on just that portion of the code and hopefully fix the problem.

    Be aware that once Trans IV gives you this error message you have to exit the program and restart it to clear that error message. Even if you found and fixed the problem, the error message will still reappear until you exit and restart Trans IV.

    If you have any trouble with following my directions or just can’t find the problem in the code, feel free to email me the program and I will be happy to try and find it for you.
    Best Regards,
    Gary

    October 4, 2011 at 2:13 pm in reply to: Error message using Trans IV #12418
    Med_Support
    Moderator
    Gary Bamberger
    RE: Error message using Trans IV
    October 04, 2011, 02:13:29 pm

    There are two problems here:
    1) There is a bug in one or more of the programs and it doesn’t necessarily have to be the program that you currently have open and are working on. If Trans IV sees that a program is out of date it will try to compile that program as well.
    2) Trans IV is not catching the bug in the program properly and giving you a useful error message in order to find and fix the problem.

    Here is what you need to do:
    1) Exclude all programs from compilation and then try adding them back in one at a time. When the error message reappears you know which program is causing the problem.
    2) Edit the program with the problem and comment out all but one of the most simplest State Sets.
    3) Recompile the program and make sure that the error message doesn’t reappear.
    4) Start uncommenting the State Sets one at a time until the error message reappears.
    5) Now you know which State Set is causing the problem. There may be more than one State Set with the same type of problem.
    6) You can narrow down where the problem is in the State Set even further by commenting out each State and then uncommenting them one at a time until the problem occurs. Again there may be more than one State with a similar problem.

    Once you know which State(s) is causing the problem you can then focus on just that portion of the code and hopefully fix the problem.

    Be aware that once Trans IV gives you this error message you have to exit the program and restart it to clear that error message. Even if you found and fixed the problem, the error message will still reappear until you exit and restart Trans IV.

    If you have any trouble with following my directions or just can’t find the problem in the code, feel free to email me the program and I will be happy to try and find it for you.
    Best Regards,
    Gary

    July 13, 2011 at 8:16 am in reply to: is it possible to code two inputs to happens concomitant? #13102
    Med_Support
    Moderator
    Gary Bamberger

    Thank you for letting me know and I’m glad that it is working for you.
    Gary

    July 12, 2011 at 12:28 pm in reply to: Programming a a conjunctive FT10.39” FR1 schedule #13109
    Med_Support
    Moderator
    lianedahas

    Thank you, Gary, now it is working.

    July 12, 2011 at 12:27 pm in reply to: is it possible to code two inputs to happens concomitant? #13100
    Med_Support
    Moderator
    lianedahas

    Gary,
    I think I was having problems in copying your code. Now, the code was translate without problems. Unfortunately, I am not able to use my lab this week, but when I test it, I will tell you what happens.
    Thanks a lot,
    Liane

    …

    Gary, now I was able to try it, and your code is doing very well!
    Thank you,
    Liane

  • Author
    Posts
Viewing 33 posts - 199 through 231 (of 305 total)
1 2 3 … 6 7 8 9 10