Jump to content

Pavel_setnicar

Members
  • Posts

    24
  • Joined

  • Last visited

Posts posted by Pavel_setnicar

  1. Yes , also encounterd the same in my app with SAMBA.

    For weeks it worked just great and then at some point output of the PID went 100% ad only autotune get rid off it.

    I did not check the PID status since I was not on site ,but costumer lost confidence in unitronics SAMBA.

    It is strange because it worked perfect for some time. Instalation is on wery remote site and I can not  get all information in time (hidroelectric power generator).

    If windup would occour , should i get this symptome?

  2. 19 hours ago, micapp said:

    nd this is what i find difficult to understand.  Normally I connect my two-wire sensor to + 24V and i.e. input CH1 (on picture), but this looks like the sensor shall connect +24V to CH1 and the low side to 0V ?

     

    image.png.f172fca92dde64a978be2af4158fc94e.png

    I think this is about analog OUTPUT , and it is corect .

  3. With a help of Daags instructions (I do not know where did he found them) I manage to get my samba 70 touchscreen  work again.

    Before i did not manage to enter calibration mode since " x value"  was always 799, only y changed correctly.

    Once in the calibration mode I simply touched  little squares and voila it works.

    It seems that in eeprom which stores calibration values some glitches caused corruption.

  4. Hi Joe!

    I work with samba SM35-J-T20 and encoder on HSC0 configured  as  high speed input reload.

    I have MI1 as counter target value and interrupt is working fine on number of counts in MI1 , but only on the value which is loaded on the power up reset.

    If I change MI1 during the program runs it makes no effect on the number of counts  on which interrupt is desired. It will change only on next power up reset.

    Is it normal ? Can't I change this parameter on the go , must I every time  restart samba  or what?

     

  5. I tried to change "time out setings" but no difference. 

    I think  "time out setings" are for the case when port is already opened but client does not respond in the given time frame.

    In my case I think Visilogic  does not sense that port is opened and it asumes that it is already opened by other program. I think this is because the created virtual port need some time to "load itself".

    As I understand Visilogic opens com port when you click any of : upload , download and monitor function.After it finishes with function it closes even if visilogic is stil runing. So even if Visilogic is runing and you do not use any of functions above you can use port for any other programm.  This opening and closing of port is my real problem.

    Anyway guys than you for respond , I will spend some more time on it and if I find a solutionI will share it with you cause i think wireless work is a luxury by itself and getting rid of some cables is always welcome.

     

  6. Hi there!

    I have the similar problem;

    Im using internal bluetooth module inside my laptop. I created virtual serial port in the laptop( COM10and COM11 ).

    I have some bluetooth   device which have serial DB9 connector and if I connect it with my virtual serial port it can be used as a serial connection without wires.

    If I put that DB9 connecto for example to another PC I can freely comunicate over serial bluetooth.

    I tryed to conect to V 570 but it doesnot work (well, it works sometimes maybe once in 20 trys.)  I think problem is when i hit "download " button on Visilogic screen virtual port need some time to open (aproximately 2 seconds) and seems that visilogic doesnot wait that long  and since it does not se port open it complains like on the screenshot atached.

    Is there any way to overcome this problem since I would realy like to ghet rid of some cables.

    complain.PNG

×
×
  • Create New...