Legacy Forum: Preserving Nearly 20 Years of Community History - A Time Capsule of Discussions, Memories, and Shared Experiences.

Technical Assistance..

Anything that doesn't fit our other forums goes here.
5 postsPage 1 of 1
5 postsPage 1 of 1

Technical Assistance..

Post by PaulP » Fri Feb 02, 2007 4:44 pm

Post by PaulP
Fri Feb 02, 2007 4:44 pm

Can someone confirm my thinking on this...

I intend to put one of these...

http://www.dpactech.com/docs/wireless_p ... module.pdf

in the Robot...

I know it will need 3.3V which can be achieved

I intend to run...

http://www.mks.zp.ua/vspdnet.php

on my p.c. so that H2H thinks its talking to a serial port...

Will this allow me to access my robot over my existing wireless network

(Belkin 802.11 b/g wireless router)

If anyone can see a pitfall or downside can they comment
Can someone confirm my thinking on this...

I intend to put one of these...

http://www.dpactech.com/docs/wireless_p ... module.pdf

in the Robot...

I know it will need 3.3V which can be achieved

I intend to run...

http://www.mks.zp.ua/vspdnet.php

on my p.c. so that H2H thinks its talking to a serial port...

Will this allow me to access my robot over my existing wireless network

(Belkin 802.11 b/g wireless router)

If anyone can see a pitfall or downside can they comment
PaulP
Savvy Roboteer
Savvy Roboteer
User avatar
Posts: 153
Joined: Fri Jan 19, 2007 1:00 am
Location: West Mids, United Kingdom

Post by inaki » Sun Feb 04, 2007 1:32 pm

Post by inaki
Sun Feb 04, 2007 1:32 pm

Apparently the software is intended to communicate two 'virtual serial ports'. So, in the PC side, where you have H2H, it would work, but you would need another serial virtual port on the robot side, which you wont have.

I believe you wont be able to communicate unless you devise a way to put some sort of virtual serial communication decoder in the robot side.

I would go for a simpler approach: use Bluetooth as a COM device in your PC an any BT-to-serial device in your robot. This has been done already with success by many users.
Apparently the software is intended to communicate two 'virtual serial ports'. So, in the PC side, where you have H2H, it would work, but you would need another serial virtual port on the robot side, which you wont have.

I believe you wont be able to communicate unless you devise a way to put some sort of virtual serial communication decoder in the robot side.

I would go for a simpler approach: use Bluetooth as a COM device in your PC an any BT-to-serial device in your robot. This has been done already with success by many users.
inaki
Savvy Roboteer
Savvy Roboteer
User avatar
Posts: 233
Joined: Sun Mar 06, 2005 1:00 am
Location: EH

Post by Bullit » Sun Feb 04, 2007 1:52 pm

Post by Bullit
Sun Feb 04, 2007 1:52 pm

Why not use a WiPort?
http://www.lantronix.com/device-networking/embedded-device-servers/wiport.html
I don't use one because in draws too much current but if you want wireless network and have the power to spare.
I agree with inaki Bluetooth works great and its fairly low power. The class 1 Bluetooth has greater range too.
Why not use a WiPort?
http://www.lantronix.com/device-networking/embedded-device-servers/wiport.html
I don't use one because in draws too much current but if you want wireless network and have the power to spare.
I agree with inaki Bluetooth works great and its fairly low power. The class 1 Bluetooth has greater range too.
Image
Bullit
Savvy Roboteer
Savvy Roboteer
User avatar
Posts: 291
Joined: Wed May 31, 2006 1:00 am
Location: Near robot

Post by PaulP » Sun Feb 04, 2007 4:35 pm

Post by PaulP
Sun Feb 04, 2007 4:35 pm

inaki wrote:Apparently the software is intended to communicate two 'virtual serial ports'. So, in the PC side, where you have H2H, it would work, but you would need another serial virtual port on the robot side, which you wont have.


The DPAC AirBorne unit has a serial out on it so I was intending to connect the serial direct to the Hi-Speed port on the robot.

Without a schematic its a bit difficult to describe but...

H2H3 >> Virtual COM >> Wireless LAN

Would get H2H on Wifi

Wireless LAN >> AirBourne Module >> Robot Hi-Speed Serial Input

Should get to the bot.

I think...

I was also considering the low speed port as well but Im not certain of its use. The Airborne Unit can support I believe up to 5 ports so theoretically it could handle all comms at 54g

I did consider Bluetooth but from other comments Ive read, The best rate acheivable is 115200 and there can be delays caused by the latency of bluetooth. A bit out of my depth on that subject but knowing how bad bluetooth is on my phones and pda links I tend to avoid it. Range would also be a critical factor (the walls in this house are made from some strange stuff) so the Class 1 option wouild be the only one viable.
inaki wrote:Apparently the software is intended to communicate two 'virtual serial ports'. So, in the PC side, where you have H2H, it would work, but you would need another serial virtual port on the robot side, which you wont have.


The DPAC AirBorne unit has a serial out on it so I was intending to connect the serial direct to the Hi-Speed port on the robot.

Without a schematic its a bit difficult to describe but...

H2H3 >> Virtual COM >> Wireless LAN

Would get H2H on Wifi

Wireless LAN >> AirBourne Module >> Robot Hi-Speed Serial Input

Should get to the bot.

I think...

I was also considering the low speed port as well but Im not certain of its use. The Airborne Unit can support I believe up to 5 ports so theoretically it could handle all comms at 54g

I did consider Bluetooth but from other comments Ive read, The best rate acheivable is 115200 and there can be delays caused by the latency of bluetooth. A bit out of my depth on that subject but knowing how bad bluetooth is on my phones and pda links I tend to avoid it. Range would also be a critical factor (the walls in this house are made from some strange stuff) so the Class 1 option wouild be the only one viable.
PaulP
Savvy Roboteer
Savvy Roboteer
User avatar
Posts: 153
Joined: Fri Jan 19, 2007 1:00 am
Location: West Mids, United Kingdom

Post by PaulP » Sun Feb 04, 2007 4:38 pm

Post by PaulP
Sun Feb 04, 2007 4:38 pm

Bullit wrote:Why not use a WiPort?
http://www.lantronix.com/device-networking/embedded-device-servers/wiport.html
I don't use one because in draws too much current but if you want wireless network and have the power to spare.
I agree with inaki Bluetooth works great and its fairly low power. The class 1 Bluetooth has greater range too.


The DPAC Unit is essentially the same, cost and packing are the only real difference between them, but as you have both indicated, power consumption and cost could be the deciding factor in the end.
Bullit wrote:Why not use a WiPort?
http://www.lantronix.com/device-networking/embedded-device-servers/wiport.html
I don't use one because in draws too much current but if you want wireless network and have the power to spare.
I agree with inaki Bluetooth works great and its fairly low power. The class 1 Bluetooth has greater range too.


The DPAC Unit is essentially the same, cost and packing are the only real difference between them, but as you have both indicated, power consumption and cost could be the deciding factor in the end.
PaulP
Savvy Roboteer
Savvy Roboteer
User avatar
Posts: 153
Joined: Fri Jan 19, 2007 1:00 am
Location: West Mids, United Kingdom


5 postsPage 1 of 1
5 postsPage 1 of 1