Jump to content

Emil

Members
  • Posts

    455
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by Emil

  1. Hi Kostya, As you can see in the attached capture, you can define one high speed counter in IO-DI8-RO4. In attached spec you can see (bottom of page 6) that this is I7 of the local module (see hardware configuration for the real address in the system)and the max frequency is up to 5 kHz. Note: HSC is supported only by I7 of the module! There is only one HSI in this module. In hardware configuration of the project you need ot link register (MI) where you will receive the counts. The update will be at the beginning of each controller'scan. I hope this answers your question. IO-DI8-RO4, IO-DI8-RO4-L.pdf
  2. Dear Tester 2, You need ot know: - If your slave (Moxa supports TCP or UDP). I guess it's TCP, but anyway, check it. - What is the IP number of your I/O module; - What is the port number; - What are the addresses of the relays there (Slave address table). Having this information, you need ot set Vision FB Modbus IP to set coils with defined addresses. You can find working example about Modbus IP Master on VisiLogic > Help menu > Examples > ... > Project examples > Communication > Ethernet > Ethernet Modbus IP.
  3. Can yo explain what do you mean? Maybe you can explain in Russian?
  4. Hi May, Nice to hear from you! Just FYI - I'm starting now most of my trainings with the movie from your singing fontain. It's amazing!
  5. You're doing the right thing. Yes, each time you want to switch between versions, you need to perform Register via the Swapper...
  6. We are working on Profibus Slave optional card for V130/350, but the issue is not scheduled yet.
  7. Hi Greg, It's still Beta and it's not recommended for real applications. If you want to play with it and give us feedback what you found, how it's working and is it intuitive enough, this will be highly appreciated. But don't start yet a real project... You may stuck with this beta version for this project forever!
  8. Hi Damian, I'll never do "Star" topology with RS485 and, of course, will not recommend such thing to anyone. If someone wants to experiment on his own responsability, I cannot forbid him. But to recommend...
  9. RS485 is pure daisy chain! Don't even dream about "star". Don't even think about "stubs! The cable must be passed strictly from unit to unit. I recommend using our connector MJ10-22-CS66, which will let you connect two cable to one RJ11 connector with minimum stub (about 2 cm). Termination must be set on the ends of the cable. It doesn't matter what is the ID of the unit. If the units are aranged in the way you show in te scheme, there needs to be unit 1 and 9.
  10. Hi Tim, Sorry, but the way you perform commands - in both cases is wrong! You must use N.O. contact of Function in progress MB as condition to start communication. In VisiLogic, Help menu > Examples > V860 > Project examples > Communication > Modbus folder there are few working examples. You can take the example V120 - Modbus Master. Take a look on nets 3 & 4. You can exchange SB52 in net 3 with, let's say SB15 (positive transition contact of SB7). Please check this way and let me know the results!
  11. Please attach your project. I want to take a look on it. What is the PTO frequency when the signal from sensor comes? What is the ration pulse/lenght? Are you sure it's not a matter of mechanichal glitch?
  12. You're right - almost... You need ot "say" first what you expect to be "zero". And the only way I know for that is callibration. You need forst to perfomr callibration. My advice is to write callibration to Flash to keep it after power down. Having proper callibration and value "almost zero", you can try to perform "aquare zero".
  13. HSC Reload Interrupt is with higher priority. If it will come during execution of 1.25 ms, it will interrupt it. Please note, that usual time of execution of interrupt needs to be in range of several microseconds to few tens microseconds...
  14. You say you callibrate it with ethalons of 10 and 50 kg. What are the numbers you set there? 10 and 50; 100 and 500; ... What happened to the weighting system after callibrating and removing the load? BTW - did you try ot switch off the power afgter callibration? Can you link your application?
  15. Can you explain what exactly happens? Did Callibration passed successfully? What are your callibration points? Do you have set Filter and Rounding? Are you sure the command Acure Zero is set with proper conditions and is received by the module?
  16. Is this happens only with UniOPC server? Did you try with other OPC server?
  17. Dear Speed, Despite most of the modems use AT commands language. each modem has specific set fo commands, "slighly" different from others. That's why we don't support just any modem, but specific list. We don't know and never heard about the modem you stated. There is practically no chance it will work. You need to use one of the modems we support. I recommend you to work with Enfora and to use our GSM kit, which includes all accessories needed and will make connection fast and easy. Don't forget in your project you need to check "Use SMS" in SMS window, and NOT Use modem.
  18. Hi Pascal, You cannot make indirect addressing of DT, as DT is accesse4d by name, not by number/pointer. Idea - you can make one big table, where you can reserve place for each button. Let's say Button 1 will take in your big DT from row 0 to row 9, button 2 - from row 10 to row 19... and so on.. In this case, you even don't need to copy the table to another one. You can work with the main table - just operating the pointers, which is not so complicated. The disadvantage of this method is, that your final customer will need to operate the whole table, which can be a little more complicated for him. You can ease his life, making Excel template, which will give beter GUI.
  19. This is a future model. We hope until the end of the year it will be realized. Then, of course detailed information will be posted!
  20. TC is in fact connection between two types of alloy. According to the temperature in this point, the connection point generates mV. The wires are part of the sensor itself and need to be from the same two types of alloy. In the moment you connect TC cable to ordinary couper one, you perform another two TC in the point of connection. When you connect T/C cable to the pins of the controller, there is another temperature sensor built in, which measures te temperature of he connector and compensate the error. This is so called "Cold junction". I hope now you understand where the inacuracy comes and how to prevent it - you need ot use cable from the same type TC and special connectors - from the same type. You need to be sure the polarity of the cables match.
  21. In Fact - you can disable communication. The way is very "brutal". You can activate COM setttings - instead with SB2 condition - every scan. This will block the port and the only way ot communicate will be after stop the controller. BTW - the password in Jazz protects only System menu - not the whole Info mode. But only in System menu you are allowed to make any changes. Other menues are "view only.
  22. Please check the communication in Boot mode. Be sure VisiLogic is set ot 115200.
  23. Right, Damian! Just idea - you can make DT with Address of... and then a subroutine. This way with one DT and few nets in one sub you will perfomrm all requested logic.
  24. Definitelly NO! And, as I explained in my previous post, this is not the right way of writing programs and we will not "sponsor" it. In other hand, VisiLogic has a lot of advanced tools to ease programming. Please describe better your needs. I'm pretty sure we can find some other solution. Small tip - take a look at FB Events...
×
×
  • Create New...