Go to Post Good thing that this is FIRST and not FIRD (For inspiration & Recognition of Dancing) ... :) - Jason Morrella [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 01-03-2009, 11:10
sabruce01 sabruce01 is offline
Registered User
FRC #2389
 
Join Date: Jan 2008
Location: Drumright, Oklahoma
Posts: 22
sabruce01 will become famous soon enough
"No Comms"

Has anyone experienced this during competition? I know in OKC there were a few that had problems. Our team lost communications 5 of the 8 qualification rounds. Our bot would simply quit in the playing field. I spoke with nearly everyone there and got nowhere. Everything they told us to check had already been replaced in the pit. Auto would be fine, then about 1/2 way through tele, we would loose communication. During our last elimination round we didn't even have an auto which caused us to be eliminated. There is no way we were loosing power to the receiver. We troubleshot that to death and could not get it to fail. But that always seemed to be the default answer I got when asking around.

Any suggestions??? Anybody experience the same?
Reply With Quote
  #2   Spotlight this post!  
Unread 01-03-2009, 11:12
big1boom big1boom is offline
Chains=Fun
FRC #2022 (Titan Robotics)
Team Role: Alumni
 
Join Date: Jan 2009
Rookie Year: 2007
Location: Aurora
Posts: 267
big1boom is a glorious beacon of lightbig1boom is a glorious beacon of lightbig1boom is a glorious beacon of lightbig1boom is a glorious beacon of lightbig1boom is a glorious beacon of lightbig1boom is a glorious beacon of light
Re: "No Comms"

Sounds like the problem a few teams were having with the Drivers Station. The Ethernet ports on the DS seem to break easily, so once one breaks, make sure to tape over it. We had Port 2 break.
__________________
Reply With Quote
  #3   Spotlight this post!  
Unread 01-03-2009, 11:41
#1packerfan92's Avatar
#1packerfan92 #1packerfan92 is offline
Registered User
AKA: Colin
FRC #2495 (The Hamilton Hornets)
Team Role: Marketing
 
Join Date: Jan 2008
Rookie Year: 2007
Location: Hamilton NJ
Posts: 12
#1packerfan92 is an unknown quantity at this point
Re: "No Comms"

this happened to our team at the NJ regional. We beilieve it was the server on the fields fault because it happened to numorus teams on each alliance over the three days
__________________
TEAM 2495
Reply With Quote
  #4   Spotlight this post!  
Unread 01-03-2009, 11:47
GBIT's Avatar
GBIT GBIT is offline
Lexantologist/Team Lead
AKA: Jared
FRC #0811 (Cardinals)
Team Role: Mechanical
 
Join Date: Jan 2006
Rookie Year: 2005
Location: Worcester, MA
Posts: 252
GBIT is just really niceGBIT is just really niceGBIT is just really niceGBIT is just really niceGBIT is just really nice
Send a message via AIM to GBIT
Re: "No Comms"

At GSR they re-ran about 12 matches and were down with comms problems for most of the morning thursday.... Our robot lost about 3 times cause of comms issues....

HERE IS HOW THEY FIXED IT!!!

1. Plug in your DS and wait for it to fully load....
2 THEN turn on your robot and wait for it to get comms

Also make sure that your gateway isn't tucked inside your robot somewhere that caused half of our problems.

Also at GSR they ended up sprinkling water in the driver's box to help cut down on static...

So be careful of placement of your gateway and such and you should be fine..

Oh and one more thing:
With the new DS update given at the competition it actually says "no comm" not "no comms"... Just saying
__________________
-Mentor-
-WPI '13-
-Former Team Lead-
-Past Driver-

Reply With Quote
  #5   Spotlight this post!  
Unread 01-03-2009, 12:10
MrForbes's Avatar
MrForbes MrForbes is offline
Registered User
AKA: Jim
FRC #1726 (N.E.R.D.S.)
Team Role: Mentor
 
Join Date: Feb 2006
Rookie Year: 2006
Location: Sierra Vista AZ
Posts: 5,953
MrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond repute
Re: "No Comms"

Quote:
Originally Posted by GBIT View Post

Also make sure that your gateway isn't tucked inside your robot somewhere that caused half of our problems.
I was wondering if this would be a problem. Also does the orientation of the gateway seem to make any difference? we had some problems during testing before ship, and ended up putting the thing on a top surface of the robot.

Quote:
With the new DS update given at the competition
Is that "new" update the one that has been on the FIRST site since Feb 10th or so?

http://usfirst.org/community/frc/content.aspx?id=10934

we found it the day before crating up the robot, it kind of messed up our plans for autnomous control.
Reply With Quote
  #6   Spotlight this post!  
Unread 01-03-2009, 12:22
Dmentor's Avatar
Dmentor Dmentor is offline
Registered User
AKA: Daniel Bray
FRC #1895 (Lambda Corps)
Team Role: Mentor
 
Join Date: Mar 2007
Rookie Year: 2007
Location: Manassas, VA
Posts: 85
Dmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant futureDmentor has a brilliant future
Re: "No Comms"

Quote:
Originally Posted by GBIT View Post
1. Plug in your DS and wait for it to fully load....
2 THEN turn on your robot and wait for it to get comms
In pit testing via tether on Thursday morning, we would often see the described problem if we started the cRIO before the DS. We got in the habit of always starting up the DS first when testing in the pits and didn't have any more problems until we started practicing on the field... In several of our matches the robot worked without problems, in the others however we would encounter odd failures associated with the digital IO controls that are relayed through the DS. We would bring the robot back to the pit and go through our checklist only to discover no problems. After a while of head-scratching, we connected the data points by guessing that there might be a startup order dependency that the driver team wasn't aware of. Once we determined this we were able to recreate the odd behavior (DS digitial IO failures) in the pit via tether. Our driver team implemented the startup procedure above using hand signals to ensure that we would always be able to run reliably. We were pretty scared until we discovered this though since debugging unpredictable behavior is tricky.

On a related note (perhaps obvious to most folks) but since the practice sessions have two portions, we needed to reset the cRIO between the portions in order to ensure proper software initialization of states. Otherwise we ended up with the system carrying over states from the first portion into the second.

FYI. We are using the Labview basic framework so I'm not sure how much different the Labview advanced framework or C++ implementations would be.
__________________
Dan was here.


2014 VA Semi-Finalist (2363, 1533), Johnson & Johnson Gracious Professionalism Award
2013 Johnson & Johnson Gracious Professionalism Award, Woodie Flowers Finalist - James Gillespie
2012 Chesapeake Finalist (358, 714), Johnson & Johnson Gracious Professionalism Award
2011 VA Semi-Finalist (122, 1111), Johnson & Johnson Gracious Professionalism Award
2010 DC Semi-Finalist (2912, 449), Dean's List Finalist - Chris Dorick, Xerox Creativity Award
2009 VA Semi-Finalist (612, 1908)
2009 DC Semi-Finalist (1712, 176), Imagery Award
2007 CMP Newton Semi-Finalist (68, 111)
2007 VA Rookie All-Star Award, Regional Semi-Finalist (343, 612), Highest Rookie Seed Award (#2), Website Award
Reply With Quote
  #7   Spotlight this post!  
Unread 01-03-2009, 12:25
GGCO's Avatar
GGCO GGCO is offline
Registered User
AKA: Grant
FRC #3357
Team Role: Alumni
 
Join Date: Jan 2008
Rookie Year: 2004
Location: Michigan
Posts: 406
GGCO is a splendid one to beholdGGCO is a splendid one to beholdGGCO is a splendid one to beholdGGCO is a splendid one to beholdGGCO is a splendid one to beholdGGCO is a splendid one to beholdGGCO is a splendid one to beholdGGCO is a splendid one to behold
Send a message via AIM to GGCO
Re: "No Comms"

Might be that annoying VxWorks bug showing it's ugly head again...

That happened to a few teams at Traverse City. Make sure you have all of the latest updates for your hardware and software.
__________________
"Great spirits have always encountered violent opposition from mediocre minds" - Albert Einstein
The FIRST Alliance
COMETS Robotics
Website

Reply With Quote
  #8   Spotlight this post!  
Unread 01-03-2009, 12:26
billbo911's Avatar
billbo911 billbo911 is offline
I prefer you give a perfect effort.
AKA: That's "Mr. Bill"
FRC #2073 (EagleForce)
Team Role: Mentor
 
Join Date: Mar 2005
Rookie Year: 2005
Location: Elk Grove, Ca.
Posts: 2,349
billbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond repute
Re: "No Comms"

Quote:
Originally Posted by squirrel View Post
Is that "new" update the one that has been on the FIRST site since Feb 10th or so?

http://usfirst.org/community/frc/content.aspx?id=10934

we found it the day before crating up the robot, it kind of messed up our plans for autnomous control.
Jim,
Can you please expand on, or explain, this comment. I'm not sure I understand how updating the DS impacts Autonomous. Inquiring minds want to know.
__________________
CalGames 2009 Autonomous Champion Award winner
Sacramento 2010 Creativity in Design winner, Sacramento 2010 Quarter finalist
2011 Sacramento Finalist, 2011 Madtown Engineering Inspiration Award.
2012 Sacramento Semi-Finals, 2012 Sacramento Innovation in Control Award, 2012 SVR Judges Award.
2012 CalGames Autonomous Challenge Award winner ($$$).
2014 2X Rockwell Automation: Innovation in Control Award (CVR and SAC). Curie Division Gracious Professionalism Award.
2014 Capital City Classic Winner AND Runner Up. Madtown Throwdown: Runner up.
2015 Innovation in Control Award, Sacramento.
2016 Chezy Champs Finalist, 2016 MTTD Finalist
Reply With Quote
  #9   Spotlight this post!  
Unread 01-03-2009, 12:43
Daniel_LaFleur's Avatar
Daniel_LaFleur Daniel_LaFleur is offline
Mad Scientist
AKA: Me
FRC #2040 (DERT)
Team Role: Engineer
 
Join Date: Apr 2005
Rookie Year: 2003
Location: Peoria, IL
Posts: 1,957
Daniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond repute
Send a message via MSN to Daniel_LaFleur
Re: "No Comms"

Quote:
Originally Posted by sabruce01 View Post
Has anyone experienced this during competition? I know in OKC there were a few that had problems. Our team lost communications 5 of the 8 qualification rounds. Our bot would simply quit in the playing field. I spoke with nearly everyone there and got nowhere. Everything they told us to check had already been replaced in the pit. Auto would be fine, then about 1/2 way through tele, we would loose communication. During our last elimination round we didn't even have an auto which caused us to be eliminated. There is no way we were loosing power to the receiver. We troubleshot that to death and could not get it to fail. But that always seemed to be the default answer I got when asking around.

Any suggestions??? Anybody experience the same?
We did not, but a lot of teams at GSR did. Here's what we did, that may have contributed to our seeming immunity to the comm issues:

1> Mounted the Wi-Fi on the robot away from all high EM fields (motors) and Faraday cages (steel). Orientation does not seem to be an issue but location is important.
2> Kept good care of our ethernet connectors (both on the DS and on the robot). We inspected them for bad spring pins, made sure we inserted the connector straight, and made sure no debris got into them.
3> Grounded the DS chassis as requested by FIRST.
4> always had our DS fully booted before booting the robot.
5> all electronics are mounted on non-conductive surfaces.

After some observations, I believe that #5 above is the culprit for most teams. Our robot (with it's propellers and wheels) generates a tremendus amount of static when on the regolith. We saw at least 2 machines have a 'No Comm' failure after an impact with our robot. My recomendation to all teams is to ensure that the robot chassis is isolated from all electronics.
__________________
___________________
"We are not now that strength which in old days moved earth and heaven; that which we are, we are;
One equal temper of heroic hearts, Made weak by time and fate, but strong in will
To strive, to seek, to find, and not to yield. "
- Tennyson, Ulysses

Last edited by Daniel_LaFleur : 01-03-2009 at 12:47.
Reply With Quote
  #10   Spotlight this post!  
Unread 01-03-2009, 12:45
BradMello's Avatar
BradMello BradMello is offline
Broken Arrow
FRC #0078 (Rhode Rage & AIR Strike)
Team Role: Driver
 
Join Date: Jan 2007
Rookie Year: 2007
Location: Bristol, Rhode Island
Posts: 134
BradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant futureBradMello has a brilliant future
Send a message via AIM to BradMello
Re: "No Comms"

Quote:
Originally Posted by GBIT View Post
At GSR they re-ran about 12 matches and were down with comms problems for most of the morning thursday.... Our robot lost about 3 times cause of comms issues....

HERE IS HOW THEY FIXED IT!!!

1. Plug in your DS and wait for it to fully load....
2 THEN turn on your robot and wait for it to get comms

Also make sure that your gateway isn't tucked inside your robot somewhere that caused half of our problems.

Also at GSR they ended up sprinkling water in the driver's box to help cut down on static...
Yeah, at GSR a good amount of qualifying matches ended up being replayed becuase of this problem. They came to the conclusion that it was static electricity and put conductive tape on the metal grate which the moon rocks rolled into in the corners of the field, and it seemed to work. They also sprayed water on the carpet in the corners of the field. After they did that I can't recall one match where anyone lost comms.

Nothing like being behind the glass and seeing Dean Kamen on the field spraying water on the carpet between matches
Reply With Quote
  #11   Spotlight this post!  
Unread 01-03-2009, 12:47
David Brinza's Avatar
David Brinza David Brinza is offline
Lead Mentor, Lead Robot Inspector
FRC #0980 (ThunderBots)
Team Role: Mentor
 
Join Date: Feb 2003
Rookie Year: 2003
Location: Glendale, CA
Posts: 1,378
David Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond repute
Re: "No Comms"

"No Comms" is not a DS problem - it's a failure of the link between the robot and the field wireless access point. Unless ALL of the robots lose their links in a match, the problem lies within the robot.

Here are some likely causes of the problem: unplugged or intermittent power/ethernet connections, burying the adapter in the robot, problem with the wireless adapter +12V supply from the PD module and mounting the wireless adapter such that the security button gets pushed as the robot is bumped.]

If you momentary lose the wireless adapter, it can take up to 45 sec for the robot to get synch'd with the field - very painful!
__________________
"There's never enough time to do it right, but always time to do it over."
2003 AZ: Semifinals, Motorola Quality; SoCal: Q-finals, Xerox Creativity; IRI: Q-finals
2004 AZ: Semifinals, GM Industrial Design; SoCal: Winners, Leadership in Controls; Championship: Galileo #2 seed, Q-finals; IRI: Champions
2005 AZ: #1 Seed, Xerox Creativity; SoCal: Finalist, RadioShack Controls; SVR: Winners, Delphi "Driving Tomorrow's Technologies"; Championship: Archimedes Semifinals; IRI: Finalist
2007 LA: Finalist; San Diego: Q-finals; CalGames: Finalist || 2008 San Diego: Q-finals; LA: Winners; CalGames: Finalist || 2009 LA: Semifinals; Las Vegas: Q-finals; IRI: #1 Seed, Finalist
2010 AZ: Motorola Quality; LA: Finalist || 2011 SD: Q-finals; LA: Q-finals || 2013 LA: Xerox Creativity, WFFA, Dean's List Finalist || 2014 IE: Q-finals, LA: Finalist, Dean's List Finalist
2016 Ventura: Q-finals, WFFA, Engineering Inspiration

Last edited by David Brinza : 02-03-2009 at 04:23. Reason: emphasis on the wireless power supply
Reply With Quote
  #12   Spotlight this post!  
Unread 01-03-2009, 13:35
pitzoid's Avatar
pitzoid pitzoid is offline
Registered User
AKA: BOB
no team (4FX Design)
Team Role: Engineer
 
Join Date: Apr 2008
Rookie Year: 1998
Location: Tampa, FL
Posts: 105
pitzoid is a glorious beacon of lightpitzoid is a glorious beacon of lightpitzoid is a glorious beacon of lightpitzoid is a glorious beacon of lightpitzoid is a glorious beacon of lightpitzoid is a glorious beacon of light
Re: "No Comms"

The ultimate conclusion is still being investigated, but I'll tell you what I know:

Robots spin wheels on FRP, plastic on plastic with a metal frame to attract the charge. robots build charge, like helicopter, get near field border, being its metal, grounded, you get EMP. DS seem susceptable to EMP.

So for all you people who saw a robot hit a field end and DSes reset and you thought it was because the physical impact knocked a connection, doesn't seem to be the case, it was the EMP discharge. This would happen anytime a robot had been running around in the middle of the field for a few minutes and then got near a field border.

All the FMS equipment is sheilded for this, I check my engineering logs on fields like BAE, no issues I could find. I run QOS on all the switches, sat and watched the field end switches for a while at BAE while matches were running, no issues I could see.

A suggestion to help. If you have your DS mounted in a control case. run a ground wire from the DS mode FIRST already mandated to a grounding connection that contacts the drivers table when you set your drivers station on the table, this will help to establish a faraday cage around your DS internal circuitry. If your DS sits directly on the table, it should ground.

We're still looking into whether the EMP being caught by the DS to SCCE ethernet cord and traveling the cord to the DS is resetting it. It looks like it doesn't affect the SCCE switches as they are industrial switches sheilded for this and I can't find issues in their logs.

The link up issues seems to be this (still being investigated):

When the WGA bridge starts up in security mode, if it doesn't see its SSID within a certain amount of time, it times out. So the general rule with this should be, DO NOT turn on your robot till you see your team number on a team station. Reason - this means the scorekeeper already activated the network configuration for your match, i.e. FMS is or has written your SSID to the Access Point, and by the time your WGA bridge boots up, your SSID will be present and it will be able to connect without timing out. This is why it seems once things got rolling, things went more smooth, but when trying to restart in the morning or after lunch where things would get out of "sync" there were issues.

These are all my theories currently
YMMV

Will keep investigating problems.
__________________
BotBash BOB Pitzer
Harvest CROO Robotics and 4FX Design

Last edited by pitzoid : 01-03-2009 at 13:39.
Reply With Quote
  #13   Spotlight this post!  
Unread 01-03-2009, 13:36
dragonrulr288's Avatar
dragonrulr288 dragonrulr288 is offline
Registered User
AKA: Abby
FRC #0216 (ROBODAWGS OTL)
Team Role: Student
 
Join Date: Jan 2009
Rookie Year: 2009
Location: MI
Posts: 121
dragonrulr288 is a jewel in the roughdragonrulr288 is a jewel in the roughdragonrulr288 is a jewel in the rough
Re: "No Comms"

AT Traverse City, the RObodawgs and Robodawgs O.T.L. Expierienced lots of this!
__________________
288 Robodawgs 216
Reply With Quote
  #14   Spotlight this post!  
Unread 01-03-2009, 13:47
GBIT's Avatar
GBIT GBIT is offline
Lexantologist/Team Lead
AKA: Jared
FRC #0811 (Cardinals)
Team Role: Mechanical
 
Join Date: Jan 2006
Rookie Year: 2005
Location: Worcester, MA
Posts: 252
GBIT is just really niceGBIT is just really niceGBIT is just really niceGBIT is just really niceGBIT is just really nice
Send a message via AIM to GBIT
Re: "No Comms"

Quote:
Originally Posted by David Brinza View Post
"No Comms" is not a DS problem - it's a failure of the link between the robot and the field wireless access point. Unless ALL of the robots lose their links in a match, the problem lies within the robot.

Here are some likely causes of the problem: unplugged or intermittent power/ethernet connections, burying the adapter in the robot, problem with the wireless adapter +/-12V supply from the PD module and mounting the wireless adapter such that the security button gets pushed as the robot is bumped.]

If you momentary lose the wireless adapter, it can take up to 45 sec for the robot to get synch'd with the field - very painful!

There were instances at GSR i know cause it was our robot where ours and only ours died and they ended up replaying the match due to a field error not our robot....
__________________
-Mentor-
-WPI '13-
-Former Team Lead-
-Past Driver-

Reply With Quote
  #15   Spotlight this post!  
Unread 01-03-2009, 13:54
MrForbes's Avatar
MrForbes MrForbes is offline
Registered User
AKA: Jim
FRC #1726 (N.E.R.D.S.)
Team Role: Mentor
 
Join Date: Feb 2006
Rookie Year: 2006
Location: Sierra Vista AZ
Posts: 5,953
MrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond reputeMrForbes has a reputation beyond repute
Re: "No Comms"

Quote:
Originally Posted by billbo911 View Post
Jim,
Can you please expand on, or explain, this comment. I'm not sure I understand how updating the DS impacts Autonomous. Inquiring minds want to know.
The older version of the DS software would "see" DS digital inputs in autonomous mode, the newer version does not. We had a set of switches connected to the DS to control autnomous, but now those switches need to be moved to the robot, and the program changed. There was no time to do that before ship.

We also did not withhold our control system to work on programming...based on our experience of making some simple changes in one place, and several other things not working as a result, all during build season. We put a mostly working robot in the crate, hopefully we'll make all our practice matches, and fix the programming problems one at a time as time allows at the competitions.
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Analog inputs not "working" — I only detect "noise" keehun Programming 11 31-12-2008 19:01
Championship Event - Where the "Random" Match Sorting Really "Shines" Travis Hoffman Championship Event 57 19-04-2007 08:06
New NEMO White Papers! "Creating a Killer Packet" and "25 Ways to Sponsor" Jessica Boucher Team Organization 0 10-08-2005 10:55
"Thunderbirds" Vs. "Team America" Which one will rule the box office? Elgin Clock Chit-Chat 3 07-09-2004 19:53
how tall is the ramp when in "up" and "balanced" position??? archiver 2001 1 24-06-2002 00:54


All times are GMT -5. The time now is 18:35.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi