¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Crestron
  2. Topics

VC4 Limitations

 

Hi All,
received this OLH note for unsupported symbols in VC4 (I'm not a fan of the fact that you can actually load these onto the program, though...)

Does anyone yet know what we'll replace the following with?
- 3-series EISC (just use the standard EISC??)
- System Clock
- SNMP
- BacNET

I'm concerned because we're being kind of forced to consider VC4 because...supply chain... and I's starting to feel like a death by 1000 cuts learning curve as we start to convert over and them have continuous starts/stops as we have to *Find* all the ways that things don't work/need work-arounds...

TIA!
 

The inter system communication should be relatively easy to work around with a TCP server/client and XSIG

For SNMP and BacNet it might be possible to write a module but that doesn't concern me personally to much since I've never used these.

What makes me wonder is how to replace the system clock...?
 

For intersystem communication the EISC Server and VC-4 EISC Client sympbols should be used.?
 

On Wed, Oct 26, 2022 at 05:55 AM, dblpnt wrote:
For intersystem communication the EISC Server and VC-4 EISC Client sympbols should be used.
Do you basically use one the server in one program and the Client in the other?? If so, does it matter which side each is on?
 

System Clock symbol is used to change the system time.? The Clock Driver symbol still works fine.


On Tue, Oct 25, 2022 at 7:48 PM ckangis <chris@...> wrote:
Hi All,
received this OLH note for unsupported symbols in VC4 (I'm not a fan of the fact that you can actually load these onto the program, though...)

Does anyone yet know what we'll replace the following with?
- 3-series EISC (just use the standard EISC??)
- System Clock
- SNMP
- BacNET

I'm concerned because we're being kind of forced to consider VC4 because...supply chain... and I's starting to feel like a death by 1000 cuts learning curve as we start to convert over and them have continuous starts/stops as we have to *Find* all the ways that things don't work/need work-arounds...

TIA!

 

Do you basically use one the server in one program and the Client in the other? If so, does it matter which side each is on?
Yes, correct.
If you're doing intersystem from VC-4 room to another it doesn't matter where the server/client is, if you're doing it VC-4 and a control system the server symbol should be used on VC-4 side, on the client side you have the ability to enter the room ID.
 

Oooh, I mixed up clock driver and system clock obviously =D
Thanks for putting that right
 

If both programs are running on the same VC-4-PC-3, do I put 127.0.0.1 as the IPs for both the server and the client or is it, say, 127.0.0.2 for program 2, etc?

1 - 8 of 8