Got to be careful... don't want to pile up some accusations on this.
From what I see-
One has built-in CS, the other does not.
One has built-in NAT, the other does not.
One accepts AC or DC power, the other doesn't.
One has auto-roaming and auto-members, the other probably doesn't.
what I don't like about gr4:
- flood mode is nice for transparent lon to ip/ethernet
what I don't like about loytec:
- price is too high
Missed you there while editing the previous post ...More features. Price is going to be (and it's only slightly in most instances) higher. Add the cost of what it takes for GR4 to use a CS. Or, the added cost of Linksys (or similar) to provide NAT and then Loytec is less expensive. It's all built-in and you don't wonder (or care) about the job requirements because you are covered.
Loytec also has smart switch mode which seems very similar to this "flood mode".
And, one of the two has 1 port, 2 port, and 4 port models.
EDIT- What do you do if you are leveraging Tridium on IP852 without LNS? That CS in the Loytec router is what you have to do.
EDIT2- The G4 wireless is still a nice option. Since it is LON you can utilize a mix in an intranetwork and list one of the G4's as a member I would think.
Roaming members support
This menu item allows to track CN/IP devices when their IP address changes. This feature must be turned on if DHCP is used and the DHCP server can assign different IP addresses to the same device (same Neuron-ID). In combination with Auto-NAT L-IPs can also be operated behind NAT routers, which change their IP address between connection setups.
Auto members support
This menu item allows members to be automatically added to the channel. If turned on, CN/IP devices can register on the CN/IP channel without the device being explicitly added on the configuration server.
Since few days I try to communicate with a gateway LON / IP (GRouter4) with the driver OpenLDV xdriver. In fact I create a LON interface from the Windows control panel, then I configure the IP address, but when I run the final test I get the following error:
Windows Sockets API: WinSock 2.0 (Running)
xdriver Remote Network Interface: X.Default.ni
Target Device IP-1 Hostname: 192.168.0.17
Target Device IP Address-1: 192.168.0.17
Target Device TCP Port: 1628
Testing connectivity to Target Device: 192.168.0.17
192.168.0.17 (192.168.0.17): 2ms 2ms 1ms 1ms
Average Round-Trip Time: 1ms
xdriver Version: 4.00.102
Attempting to ESTABLISH xdriver connection with device ...
ERROR: Failed to ESTABLISH xdriver connection with device! (Error: 12: Open Failed)
ERROR: Failed to close connection with xdriver device! (Error: 3: Not Open)
FAILURE: xdriver diagnostics test failed.
Can anyone confirm that is incompatible with the GRouter4 OpenLDV.