tashinz

MrPLC Member
  • Content count

    394
  • Joined

  • Last visited

Posts posted by tashinz


  1. As I can remember, NS12 and NSJ12 have the same NS operator panel features. I am suppriesed that NSJ is cheaper. ... As I can see from our price list NSJ12 cost about 500€ more than corresponding NS12 (with/without ethernet). Maybe you have bad info?

  2. yes, good idea, only the @VBSCRIPT / @ENDSCRIPT wraps existing CX-S script. maybe it is better to insert something like @VBSCRIPT insert VB Script code here... @ENDSCRIPT and existing CX-S script to be outside of this. also, when first script editor is opened, the default is VB Script but no @VBSCRIPT / @ENDSCRIPT.

  3. Hm... this happen to me a few times. but I realized why. since we bought cx-s 2.0 upgrade and I installed that on Vista machine without prior installing cx-s 1.3, that message kept appearing. after I install first cx-s 1.3 and then cx-s 2.0 never saw this message again, both clicking on the .scs in explorer or by open project.

  4. I have just tried to do the same thing - no error displayed. Also have cx-s 2.01 on vista ultimate. the script, on the push button object is: display("ALARMS") and cx-supervisor script radio button is checked. as I said, the script interpreter reports no error - after clicking OK everything is ok. I start the runtime, click the button and it works, the page ALARMS is open. Hm, what could be the problem Pim? WAIT... here is the problem. if I write script display("ALARMS") and THEN check the radio button CX-Supervisor script I get following script: @VBSCRIPT display("ALARMS") @ENDSCRIPT then in runtime I get the error message like you have. when I delete the @VBSCRIPT and @ENDSCRIPT there is no error in runtime. obviously they put VB Script to be default but the CX-Supervisor Script radio button invokes @VBSCRIPT and @ENDSCRIPT which marks start and the end of VB Script. probably a little bug. if you FIRST check CX-Supervisor Script radio button AND THEN write the script it will work.

  5. sure i went to work, but you're right Pim, very tired I am. was commissioning in Bosnia these days, heating plant. and since the heating season started today, everything was urgent of course. moving on to the next project allready. and so forth, till the day I retire in about 30 long years.

  6. I have an application with 5 cx-s 1.33 runtime instances on one computer. tried to avoid that but customer wanted it that way. anyway...it works perfectly and this apps are quite big i must say, works on ethernet. this shouldn't be disabled, both in runtime and developer. what's the use of it anyway?

  7. they should implement some kind of object properties, like in cx-designer. so, e.g. one can change position, domensions, color, point assignment of the object etc. this could also allow group editing (again like in cx-designer). access to the object through workspace window is not sufficient.

  8. Hey, don't know why didn't i test, but when i paste the point name to the address toolbar - where the actual plc address is located - it is recognized. cool. also: no option for rotate object (nor functional nor fixed) by a custom angle. just 90°. they should put it.

  9. when choosing a point name instead of actual plc address, address setting dialogue appears with list of points. this window can not be resized at all and it is very hard to read point's comment which is very important. i loose my nerves this way and stick to plc address asignment. also when resized, window should remember its position. also, when there is already an option to use symbols instead of plc address, they should allow to see object reference to a symbol not just address. this should be done for address toolbar as well as for the object's property window.

  10. another suggestion: toggle button object does not have a lamp function. i use this object as a momentary button (toggle while pressed option selected) for turning off/on devices. pulse is sent to plc where the KEEP instruction turns on/off physical output. normally in NS panel i would use lamp function of the push button to see the state of physical output. in CX-S I can not do that. they should put this feature. or someone has an existing solution ?

  11. yep, the same is here. wouldn't know why. also, when I pull out the usb hardlock during runtime, communications still work. it stops after restart runtime. is this ok? two suggestions: 1. it would be great if the external communication can be enabled without hardlock for simulator. no? simulator is used for testing only, don't see the reason why cx-supervisor couldn't be connected to simulator plc during development without hardlock. 2. copying points from cx-p into cx-s is great but after that i need to bulk edit all copied points from I/O to just input. that option does not exist in multiple edit dialoge. they should put all point attributes to be bulk edited. this way i have to copy first to excel, edit, then copy it back to cx-s. this way copying from cx-p does not have any sense.