Author Topic: Is there any restriction on the names assigned to non-volatile memory?  (Read 2300 times)

Offline tronelec

  • PLUS+1 Developer
  • ***
  • Posts: 20
  • Karma: +0/-1
I am developing an application that activates on/off valves sequentially, a pulse starts the sequence, write true to activate valve 1, cylinder 1 activates sensor 1 and turns off memory 1 (write false), I use the lowering button of the memory 1 so that memory 2 writes tru and activates valve 2 and so on until the entire sequence is executed. all memories have the same connection and configuration (bool). The problem occurs in memory 45, the name assigned to the first memory is MT1_B1 for routine 1, MT2 _B2 for routine 2, etc. The problem occurs to me in step MT45_B4. Is there any restriction on the names used for these components? Another possible problem is that I develop the application using an hwd file for mc012_110 (it is the hardware that I have available to run and monitor in servicetool), then I copy the routines and paste them into the program to use on the machine, which is a mc050_110, both files are compiled without errors, the drivers can be loaded into the controllers, both drivers can be monitored without problem using service tool, but on the field hardware (mc050) the routine is interrupted at step MT45_B4. Is there any restriction on the maximum number of memories and/or their names?

Offline tronelec

  • PLUS+1 Developer
  • ***
  • Posts: 20
  • Karma: +0/-1
 :oI solved the problem, but I don't understand why it worked, I just put a checkpoint in the routine and the sequence continued.

Does anyone know why the error occurred and why it was "resolved", I still don't understand.
Is it possible that the check points force the controller to read or pay attention to the routines?

Offline spittet

  • PLUS+1 Guru
  • *****
  • Posts: 118
  • Karma: +6/-1
Do you really need to store the state of the sequence in a NVmem? NVmem have a limited number of write cycles. If your sequence is actuated lot of times per day, you could end with a non functionning NVmem block and need to replace the controller.

I would prefer this sequence to be done with Set/Reset components. At Power-On, maybe you could do a kind of "homing" sequence that sets all the cylinder to the original position so the sequence always starts at a known good position.

Sam