Search the Community
Showing results for tags 'UniCan'.
-
In Examples there is UniCAN example "UniCAN for CanBus between masters" and it does work. But there is MI 0 what stores UniCAN Send Status, problem happens when it turns 1 "network is busy". After that, no communication. Only way to restore communication is PLC OFF and ON cycle. I wonder maybe there is some little less destructive way to understand when communications can be restored ? Maybe use some SB's or SI's ?
-
Hey all, Can someone point me in the right direction how to make a Unistream PLC send/receive more than 64 bytes in one scan cycle from/to a Vision Standard PLC (eg. V120-22-T2C)? Setup: - V120 equipped with 24 Analog In & 12 Analog OUT - 7" Unistream PLC without I/O - Both connected through UniCAN I know a Vision PLC is able to send/receive up to 512 MI's in one PLC scan cycle through UniCAN. And has no problem sending/receiving multiple messages to/from the same Node ID or multiple Node ID's. In my setup, I want to receive the status of the I/O of the V120 along with some other variables into the Unistream PLC. 24 analog inputs & 12 analog outputs already sums to a total of 36 MI's or 72 bytes to pass to the Unistream. But the Unilogic software gives me only the possibility to create just 1 configuration per Node ID and the tags for receiving/sending can only be as large as 64 bytes. Otherwise, a compile error will occur.. What is the preferred, correct way to accomplish this in the Unistream without having to use a EX-RC1? Grtz, SRO
-
Does the EX-RC1 support the same functions, such as drum sequencer, as the vision series?
- 3 replies
-
- ex-rc1
- Drum sequence
-
(and 2 more)
Tagged with:
-
Hello, While programming UniCan Network I noticed that it is possible to erase all the data of other PLC. For instance, PLC with ID1 can send (random) data to PLC with ID2 and always change MI from 0 to 8000. This way all ID2 will be filled with unknown data and so PLC program will malfunction. This is security issue if anyone will get the access to UniCan cable. My suggestion is to make receiving buffer and do not allow changing PLC data directly. The concept could be similar to UDP data packet structure: Sender, Destination, Data. Of course, many users will have to rewrite their PLC programs, but I believe it would be great improvement. To have compatibility few last MI can be dedicated to network for those who want it. Thank you.
- 1 reply
-
- UniCan
- Vulnerability
-
(and 2 more)
Tagged with:
-
DEAR SIRS DOES ANYONE HAVE SOME SAMPLE PROGRAME TO CONECT MORE THAN ONE UNICAN EX RC1 MODULES IN UNICAN NET. I USUALLY USE ONLY ONE EX RC1 + IO EXPANSION MODULES IN PROJECTS. I HAVE MUCH TRUBLES TO CONECT SECOND EXRC1 MODULE. FOR A ONE MODULE I NEVER HAVE DIFICULTIES FOR 1 EX-RC1 UNIT THAT SOFTWEAR HAS BEEN CONFIGURATED FROM UNITRONIC UNICAN SAMPLE AND WORK SUPER. FOR A SECOND EXPANSION A HAVE MUCH DIFICULTIES , DIP SWITCES HAS BENN CONTOLLED WIRES ARE OK BUT BUS COMM FLASSHES ALL THE TIME. USE MI 2024 SOFTWEARE TRIED COUPLE TIMES AND NO SUCSESS. PS. PLC VISON 1040 .......ID1 UNICAN ....... ID2 MODULE1 EXRC1 CANOPEN ..... ID3 YAKSAWA V1000 FREQ CONV. UNICAN2 ....... ID4 MODULE1 EXRC1 DOES ANYONE HAVE ANY SUGGGESTION. KIND REGARDS GREGOR . EX-RC1-SKUPNI ID1.vlp EX-RC1-SKUPNI2 ID4.vlp