Am Freitag 13 Oktober 2006 10:50 schrieb surfzoid surfzoid: > >And I thought that this is about doing OBEX over cable. So why are you > >playing > >around with IrDA? > > I'm very confuse about it, many time there is discus about IRDA com port > and com port over cable !! > My only experience about it, is from windoze and in fact there isn't any > différence for him, between com port via IRDA,USB ... com port is com port, > if you have a modem to this com port you can send AT command, my phone > modem is capable to receive AT and also obex/IRMC after with say to it by > AT +CPROT=0. > So that's why my very basic test tool, in very basic language work great > and don't care to know if the com port where i send AT +CPROT=0;wait;send > obex sequence to conect and so one, is a IRDA,USB,BLUETOOTH(i know the > security pair,litle different, but not for AT cmd),or really serial port.
Then let me explain it for you. OBEX originated at IrDA which has a protocol difference between using OBEX (called IrOBEX) and serial port emulation (called IrCOMM). Both are _native_ IrDA protocols! Bluetooth took over the concept of OBEX but rearranged the whole thing. Now, RFCOMM is a serial layer (_NOT_ yet the serial port emulation) and the serial port emulation is provided with an RFCOMM protocol. OBEX is now another such protocol that uses RFCOMM and a client can differn between different OBEX-Profiles (like Sync, Push and FTP) A serial cable (be is a real RS232 one or an USB->serial converter cable) is a different matter. Those can only use one mode at a time and thus cannot run OBEX in parallel like with IrDA and Bluetooth. This is why many vendors use a special AT command to switch to OBEX mode. Doing this with IrDA or Bluetooth does not make sense since those support OBEX natively. You can also take a look at the other side: the phone's firmware. Commands that work over real cable may not work over IrDA or Bluetooth serial port emulation. Or the other way round. Or they may work differently. Thus comparing what happens with AT+CPROT=0 on IrDA (or what doesn't) to what happens with it on cable may be totally bogus. There are some bad things about OBEX though: being supported does not mean that everything is supported. Let's take IrDA OBEX: it may only support OBEX-Push and not OBEX-FBS. But you should try anyway to use IrOBEX native, everything else is just communication overhead. Since you program under Windows, take a look at the Windows API reference about how to address IrOBEX without serial port emulation (if you open a virtual COM port, you are already the wrong way). If that works and you would like test with obexftp, use the -i switch and _not_ -t /dev/ircomm0. Pushing an object (try the tools from the apps directory of openobex) to the phone may give you a hint if at least that works. Pushing a file from the phone (most phones offer to send objects via IrDA or bluetooth) is also possible, use obexpushd to receive it. If that works, you can at least push objects manually in both directions. HS ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
