|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: remote port or service name
i want to get a picture from the camera by an onboard laptop, do some processing, and then send information out to the crio to read. So not dealing with any network. So is it still limited?
|
|
#2
|
|||||
|
|||||
|
Re: remote port or service name
You should just use WPILib to read the camera's stream on your laptop, this shouldn't be a problem for you, right. This will use TCP port 80 underneath. When you send data to the cRIO, I'd use UDP on any port, except 80, just pick one that isn't already in use (and yes, I know that TCP 80 and UDP 80 are technically different, but just avoid that port and make things simper, it's not like you're all that constrained).
|
|
#3
|
||||
|
||||
|
Re: remote port or service name
udp not tcp?
|
|
#4
|
|||||
|
|||||
|
Re: remote port or service name
If you're just sending data between two computers, you don't need the handshake because, if a packet is dropped, another one will be sent very shortly thereafter. It's the same reason the driver station/robot communication uses UDP, as well.
|
|
#5
|
||||
|
||||
|
Re: remote port or service name
oh ok so TCP is only for if you need to send data making sure that it arrives correctly with no error. For example, a messaging program, right? But since it will be updating information constantly, it doesn't matter if it gets there or not, because right after it a new one will come in. Is this right?
|
|
#6
|
|||||
|
|||||
|
Re: remote port or service name
That is correct.
|
|
#7
|
||||
|
||||
|
Re: remote port or service name
ok thank you so much. I think i understand it now. +1 for reputation
![]() |
|
#8
|
|||||
|
|||||
|
Re: remote port or service name
Wonderful, I'm always happy to help (and sometimes learn something new in the process). Don't hesitate to shoot any other questions my way, should they arise.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|