They're never shipped 'blank'. If you did have only the bootloader present, otwincfg would automatically ask you for a file to load.
Each unit is checked out in terminal mode prior to final assembly, with the sensor readings, RX performance, and TX levels checked. After final assembly they're powered up again to check for the proper LED start sequence (which also indicates that the firmware is starting OK) to make sure nothing got shorted out by the case. What you might be seeing is a comm error, maybe a bad USB adapter or something. It's possible for the firmware to become corrupted and not work until it's reloaded, but it should still show a build number. Scott Gerry Graff wrote: > > > > I sort of ran into the same thing. If the computer sees it, and the > configuration program opens, if you do not see a Firmware number at the > top of the configuration, then run update firmware. In other words, > with mine, the unit came "loaded" blank, and I had to use the update > firmware to get to a starting point to program the unit. After that, > all was fine. I haven't seen this documented elsewhere. > > > > Gerry > W5LCY > > On Jun 30, 2009, at 8:51 AM, kc0nro wrote: > >> >> >> All, >> Just got my OTm2 last night and am still trying to get connected to >> the booger and configure it... >> >> I have tried every thing I can think of. otwincfg and hyper >> terminal...many different baud rates, flow control, etc. I can't seem >> to get the PC talking to the unit. >> >> FYI, I am using a gender changer on the end of my serial cable to hook >> to the OTm2's serial port. >> >> Anyone have any ideas? >> >> Many thanks, >> >> JOHN >> > >
