Section 8. Operation
• DHCP
• DNS
• FTP
• HTML
• HTTP
•
• Micro-serial server
• Modbus TCP/IP
• NTCIP
• NTP
• PakBus over TCP/IP
• Ping
• POP3
• SMTP
• SNMP
• Telnet
• Web API
• XML
• UDP
• IPv4
• IPv6
•
The most up-to-date information on implementing these protocols is contained in
CRBasic Editor Help.
Note Specific information concerning the use of digital-cellular modems
for TCP/IP can be found in Campbell Scientific manuals for those
modems. For information on available TCP/IP/PPP devices, refer to the
appendix Network Links
(p. 570) for model numbers. Detailed information
on use of TCP/IP/PPP devices is found in their respective manuals
(available at www.campbellsci.com) and CRBasic Editor Help.
8.10.1.1 FYIs — OS2; OS28
• TCP/IP info no longer in status table — get from datalogger settings.
• CR800 now adopts auto IP address of 169.254.67.85 (if available) if
DHCP server not available or static IP address is not set. This makes it
easier for PC to CR800 ad hoc connections.
• Added limited DNS server capability — CR800 intercepts / respond to
cr1000.com
• Added a default public/internet DNS server if none is assigned. This
should result in less "why isn't my EmailSend to email.server.com not
working?"
• Apologies to those who have figured out how to read our IPTrace
information — it has changed quite a bit.
• Network Time Protocol server not enabled by default. This requires
inclusion of NetworkTimeProtocol() instruction in the program.
8.10.1.2 DHCP
When connected to a server with a list of IP addresses available for assignment,
the CR800 will automatically request and obtain an IP address through the
To Next Page
Loading...
