A bit of background first: the distinction between incoming and outgoing RFCOMM (Bluetooth stack protocol for virtual COMs) ports is necessary because it's always one of the communicating devices that initiates the connection (a bit similar to TCP sockets - where you have server and client).
- The outgoing COM port is used when the PC initiates the connection to the
remote device (opening the port initiates RFCOMM connection to the remote device).
- The incoming COM port is used when the remote device initiates the
connection.
Once the connection is opened it is bidirectional, regardless of the type.
That said, this Bluetooth module supports both master and slave mode (see manual chapter 2), that's why it advertises 2 RFCOMM/SPP ports, I guess. If you want PC to initiate the connection, use COM6, otherwise use COM7.
Why you see no echo in PuTTY? By default there's no local echo, and you actually shouldn't see any characters you type (unless you short UART_RX to UART_TX, or have some real device attached there to communicate with). The module itself is transparent (in the data mode, that is).
Also, baud rate etc. shouldn't really matter for Blueooth connection - note, that chapter 3.2 refers to configuring the device via physical serial port (UART_RX/TX pins, i.e. from the device side), while 3.3 describes configuring over virtual port (i.e. from the PC side). I somehow feel you're confusing the module sides ;)
This excerpt from the manual is quite important:
To connect to FireFly, browse for
services, you should see: “SPP”
profile with a virtual COM port. Open
this virtual COM port to create a
Bluetooth connection. Once connected,
the device will be in data mode
allowing data to flow in both
directions as if the serial port were
locally attached to the PC. The device
must be in command mode for
configuration and programming. To
enter command mode type “$$$” (three
dollar signs) from either the remote
Bluetooth connection or the local
serial port connection. You must enter
command mode within 60 seconds
(configurable by setting the config
timer).
Cool module, btw!
I have worked with this module before and found that it only appears in a scan if it is in "data" mode. To put the module into data mode you have to drive the mode pin low. However the datasheet neglects to tell you that the module wont actually switch into data mode until the reset pin is pulled. Try driving the mode pin low, pressing the reset button, and then doing a scan again. Something called "HC-..." should appear.
Best Answer
The HC-05 and HC-06 are identical, except the firmware they get shipped with. For whatever reason, the HC-06 has a simpler, slave only firmware. The HC-05 has a much more completed command set. There was some attempts to reflash or change the firmwares on these but the projects were a bit obscure. It's just cheaper and faster to get the HC-05 or a newer master capable bluetooth module.