|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: MRS 2.0 Interface for VEX released
My first question is, what happens when you have more than one encoder? I guess that new feature of polling ports is convenient if you only have one of each type of sensor, but I can see that causing issues. Oh well, I hope it works out okay for those who decide to use it.
|
|
#2
|
|||
|
|||
|
Re: MRS 2.0 Interface for VEX released
The scanning only happens when you DON'T specify a manifest. If you configure a manifest, it will use it as is. This is really not a big change from the existing system other than that it will create a working service rather than a dummy that does not connect to anything real. (e.g. you could create digital input 1, analog input 1, digital output 1 as the defaults with the prior system. Now they will be created with something that is real or not create the service if it is not configured.... again if no manifest is available.)
At some point I plan to make using a manifest on an 'outer' servic to force the controller to update the controllers configuration to match the outer service. Of course in that direction, if you used two different services that each went and tried to claim IO port 5, then who wins the actual configuration is up in the air. Ed |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Release of MSRS interface for the VEX | Edmund Harfmann | Programming | 0 | 24-07-2007 20:14 |
| MSRS interface for the VEX controller | Edmund Harfmann | Programming | 12 | 29-06-2007 20:38 |
| pic: Mr. and Mrs. Matt and Angela Leese | Joe Ross | Extra Discussion | 8 | 11-10-2006 01:44 |
| Vex Announcement: FIRST Vex Challenge Extended for 2006-2007 | KathieK | FIRST Tech Challenge | 14 | 30-07-2006 23:42 |
| Material for Operator Interface | archiver | 2001 | 4 | 23-06-2002 23:03 |