[DFTF] Operator Interface...

[feverittm]

While we have tested both the gamepad and the joystick interfaces, we have normally stayed with the joysticks. We use tank mode driving which seems more natural with two joysticks. When we have tried using a gamepad we found the lack of range of stick motion vs game pad stick motion to be disturbing (there is more room for the driver to move the sticks), this might be different with omnidirectional type of drives. You will probably need to check which is easier for your drivers.

As per the First Touch IO module, we used this last year. While you can update and reprogram the device (more like a FPGA than anything) this is difficult since in order for the IO module to be recognized by the driver's station it must be built on the FIRST provided framework and at this point is difficult. It provides Analog (which we used last year as inputs from Potentiometers) and digital inputs, as well as digital outputs. There are supposedly other modes (like encoder input) available, but switches are the most used.

One thing not noted. Be very careful with your wireless signals. The best we have seen is to try and maintain wireless N across the drivers station link in order to eliminate the interference with WiFi signals/Access points. You do not want to see the dreaded 'No Robot Communication"!

[Joe Johnson]

Originally Posted by feverittm

<snip>

One thing not noted. Be very careful with your wireless signals. The best we have seen is to try and maintain wireless N across the drivers station link in order to eliminate the interference with WiFi signals/Access points. You do not want to see the dreaded 'No Robot Communication"!

Thanks for the input. But that last bit about "maintain wireless N..." is totally outside my understanding. I understand each word but I have no idea what is says.

Joe J.

[Greg McKaskle]

I think the phrase about wifi was advising to use an N-speed or an 802.11N network where possible -- specifically 5GHz N or dual band N. G will work in a pinch, but is lower bandwidth, tends to be busier and the band used 2.4GHz is congested. N also has better range.

Using N means having a laptop, router, bridge, and other elements that support it. If one of the elements is g, the communication path will revert to g speeds.

Greg McKaskle

[DonRotolo]

Originally Posted by Joe Johnson

What about the O part of IO?

There are a bunch of digital outputs available. No analog outputs. These sink enough current to drive small LEDs, and can certainly drive a transistor or other switch to manage larger loads.

I see no rules prohibiting either of those items from being used with the Operator Interface. And that would surely win the "cool as beans" award in my book.

Wireless N:
Greg covered it well.
WiFi wireless networking comes in several flavors, they are all called 802.11 after the IEEE section where they are defined, with the first being 802.11a, the next 802.11b, and so on. Current latest and greatest commercially is 802.11n.

[Chris Hibner]

Originally Posted by DonRotolo

There are a bunch of digital outputs available. No analog outputs. These sink enough current to drive small LEDs, and can certainly drive a transistor or other switch to manage larger loads.

I see no rules prohibiting either of those items from being used with the Operator Interface. And that would surely win the "cool as beans" award in my book.

We've done a lot with LEDs with the old IFI system (2008 and prior). We haven't done anything since then, but we're planning to this year. We haven't implemented it yet, but I can let everyone know how it goes.

I actually think we'll be making a lot of use of the Cypress board this year.