Forum Replies Created
-
AuthorPosts
-
Dierk
ParticipantHi,
as you already discovered, I stopped working on V-Control. In the past years, I was not able to earn enough money with it to pay my rent. After 28 years being self-employed, I started as an employee at Leyard in May 2019.
Maybe some day I continue, starting a new project or do something complete different. For the next years I focus on my new job at Leyard. I like it very much.If someone would like to continue with V-Control, please contact me. I can support then, but I am not doing the further development alone anymore (at least not in the next years).
Dierk
ParticipantHi Jens,
I am not sure if I understand “Set the TCP-Services on”
Do you mean Remote services?
In general, in a Linux system, all applications using a TCP port equal or lower 1024 need to run with root privileges. This is standard Linux behavior. If possible you should always use ports above 1024.“Now i tried connecting to an Aten0404ha HDMI Switcher via an exsys6032 device server.
I created a new device, assigned a new Channel to the IP and Port of the Com1,”There is no “Com1” on a Linux system. Usually RS232 Ports are at /dev/tty0 or /dev/ttyUSB or similar, depending on your RS232 interface. In cas of the exsys6032 there is no comport at all. There is a virtual device driver for windows. With this driver you can use it in the same way as a local RS232 Port. But for all other operating systems you have to open a TCP conection and use it as a Telnet client.
Because EXSYS does not support Linux, you have to use the windows tools to configure the device (IP Address, Port, RS232 settings), and then connect from V-Control via TCP.
-
This reply was modified 2 years, 3 months ago by
Dierk.
Dierk
ParticipantV-Control 4 has a lot of changes under the hood compared to v3. It is much more Event driven. There are also some script commands in V4 that are not available in V3. If you export a V4 device and import it in V3, then it works unless the driver does not use any of the new scripting commands. After import in V3, go to device editor and click compile. If there is no error, then the driver should work.
Dierk
ParticipantHi Anika,
Best solution is to make a new 4 project. Anyhow, it should be possible to create the sending and receiving devices in V-Control 3. Download V-Control 4, add the two devices there and then you can use them as template for the v3 devicesDierk
ParticipantHi Andreas,
thanks for letting us know. Good that you found a work around. Anyhow, this should not happen in V-Control. The result should be that you simply can not talk to the arena server. So could ypo please post your project. Maybe I can find the bug that causes this behavior then.
Dierk
ParticipantNice project, thank you very much for sharing.
Dierk
ParticipantOne solution could be to put the status in a global variables with coma separate values (maybe one var for ins and one var for outs)
If you have 100 vars the you can use a script that read a variable, fetch the ins and outs and push it to the matrix
So you have 100 presetsDierk
ParticipantIt is not possible to create a task from a script. Global variables are saved as far as I remember. But I’m out of office and can’t check this.
At the moment I can’t see any reason why you would create a task from an event, can you describe your use case in more detail?
Dierk
ParticipantHi Steve,
if you can poll the TC of the file, then you can set up a monitor command that is polling the, TC let’s say every 40 ms, and push this value into a Device Variable. Then you can use this device variable as TC reference in a timeline.
Dierk
ParticipantYou can set a Global var within an device event, and then call a task that reads this global var and perform an action depending on the content of that var. his can be done in scripts
Dierk
ParticipantOh sorry, with TermChar I mean a termination Character, but this is not the terminology used in V-Control. In V-Control this means the “Ack in Hex” field. In this field you have to enter one or more hex values that determine the end of the acknowledge.
Dierk
ParticipantIf you have 519 clips, then the length of the total response is very big. The standard frame size of an Ethernet packet is 1500 bytes. I assume that V-Control thinks the Acknowledge is complete before the whole Acknowledge is received.
To solve this you need something such as a termination character or sequence. I can imagine that chr(13) is not suitable because it might be multiple times in the Acknowledge.
You need to find a single character or a sequence of characters that marks the end of the transmission and define that as TermChar.
At Configure->Options in the System Tab, there is also a “Maximum Channel Buffer Size” value, set to 600 by default. If the length of the Acknowledge exceeds this size, then the Acknowledge will be dropped. So you might need to increase this value.
Dierk
Participanthere the driver
Attachments:
Dierk
ParticipantFirst: That a project was not able to open never happens to anyone as I know, except it was really created with an older or newer version.
Second: I have no problem to open the file with 4.1.5. I don’t know why you have this problem, it’s not reproduce-able for me.
Anyhow, I extracted the driver for you, so you should be able to use it.
Your driver is really big. I think you’re noticed that loading the driver in the device editor takes some time. Do you really need all these commands? Or is it just a workout to get some V-Control skills? -
This reply was modified 2 years, 3 months ago by
-
AuthorPosts