Parallax Forums
  HomeLog InRegisterCommunity CalendarSearch the ForumHelp
   
Parallax Forums > Public Forums > Propeller Chip > Anybody tried using viewport thru bluetooth  Forum Quick Jump
 
New Topic Post Reply Printable Version
[ << Previous Thread | Next Thread >> ] | Show Newest Post First ]

ChuckT
Registered Member

Email Address Not AvailablePersonal Homepage Not AvailablePrivate Messaging Not AvailableAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Jan 2008
Total Posts : 12
 
   Posted 10/31/2009 10:05 PM (GMT -8)    Quote This PostAlert An Admin About This Post.
I have my bluetoth runnin at 115K to a termal emulator. but when I try to connect it to Viewport it just says no configuration found.
I used the Std terminal config and share lines. I modified conduit to use th eBlue pinouts.
Anyone get this working or have ideas.
Any help is
Back to Top
 

microcontrolled
My head is SPINing.



Email Address Not AvailablePersonal Homepage Not AvailablePrivate Messaging Not AvailableAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Oct 2008
Total Posts : 867
 
   Posted 11/1/2009 3:55 AM (GMT -8)    Quote This PostAlert An Admin About This Post.
Well, as with all wireless connections, there cannot sim0ply be a straight hookup. I am not familier with bluetooth but I believes it requires a "handshake" code to be sent initially.. Aolso make sure it is running at the same baud rate as the bluetooth is otherwise error will incur.


Computers are microcontrolled.
Robots are microcontrolled.
I am microcontrolled.
 
But you can call me micro.
 
Want to experiment with the SX or just put together a cool project?
Want cheap wholesale electronic parts?
Back to Top
 

Mike Green
Registered Member



Email Address Not AvailablePersonal Homepage Not AvailablePrivate Messaging Not AvailableAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Oct 2004
Total Posts : 13558
 
   Posted 11/1/2009 6:15 AM (GMT -8)    Quote This PostAlert An Admin About This Post.
1) ViewPort, like the program download process, makes use of the way the DTR control line is connected to the Reset pin of the Propeller. It has to be able to force the Propeller to reset.

2) The Baud setting (115200) applies only to the connection from the Bluetooth device to the Propeller or the Bluetooth device to the PC. The actual throughput of the wireless link and the instantaneous transfer rate is often very different since the Bluetooth device buffers the data and may have to repeatedly send a packet of data to ensure accurate delivery. The Propeller's identification and download protocol is too sensitive to timing to tolerate this and I assume that ViewPort is similarly sensitive to the instantaneous transfer rate.
Back to Top
 

ChuckT
Registered Member

Email Address Not AvailablePersonal Homepage Not AvailablePrivate Messaging Not AvailableAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Jan 2008
Total Posts : 12
 
   Posted 11/1/2009 3:41 PM (GMT -8)    Quote This PostAlert An Admin About This Post.
Thanks for the ideas, I initialized the bluetooth thru my normal duplex connection modified for bluetooth. I configured and tested it for 115K (STD terminal operations). Then I stop my std com cog and start the viewport share process. The Prop fails to send anything. I'm not sure if I didn't get the old process stopped or if the viewport share process needs more work than just changing the pins. Mike, good point even if I can get something going out the viewport may have problems.
Back to Top
 

Mike Green
Registered Member



Email Address Not AvailablePersonal Homepage Not AvailablePrivate Messaging Not AvailableAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Oct 2004
Total Posts : 13558
 
   Posted 11/1/2009 4:50 PM (GMT -8)    Quote This PostAlert An Admin About This Post.
Again, remember that the Baud set for the Bluetooth adapter has nothing to do with the actual transfer rate over the Bluetooth wireless connection. That depends on the amount of noise around (affecting retries) and the overhead used for the Bluetooth protocol internally.
Back to Top
 

Hanno
Registered Member

Email Address Not AvailablePersonal Homepage Not AvailablePrivate Messaging Not AvailableAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined May 2007
Total Posts : 447
 
   Posted 11/1/2009 6:48 PM (GMT -8)    Quote This PostAlert An Admin About This Post.
Hi Chuck,
(Thanks Mike for the good advice). Programming and resetting the Propeller via bluetooth is probably difficult due to timing issues and the need to reset the Propeller. However, you should be able to write the program to eeprom using a wired link, and then later working with ViewPort. The conduit code detects the baud rate by looking at the start bit's length. The conduit will start out by continually transmitting the configuration string with some binary data. You should be able to see this in a normal terminal. ViewPort looks for the configuration data and then instructs the conduit to send data. Can you provide more info about what works and what's not working?
Hanno


Co-author of the official Propeller Guide- available at Amazon
Developer of ViewPort, the premier visual debugger for the Propeller (read the review here, thread here),
12Blocks, the block-based programming environment (thread here)
and PropScope, the multi-function USB oscilloscope/function generator/logic analyzer

Back to Top
 

ChuckT
Registered Member

Email Address Not AvailablePersonal Homepage Not AvailablePrivate Messaging Not AvailableAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined Jan 2008
Total Posts : 12
 
   Posted 11/3/2009 1:30 AM (GMT -8)    Quote This PostAlert An Admin About This Post.
Thanks guys! Hanno as you say the conduit sends out out a config stream. I can see it over a wired connection. I have never seen it over a the blue tooth.
So I setupo the bluetooth with std fullduplex set the bluetooth to datamode and stop that cog. Then I run share. I modified conduit to use the pins of the bluetooth.
I also tried conduit set for 9600 but still nothing shows up on a normal terminal.
Back to Top
 

Hanno
Registered Member

Email Address Not AvailablePersonal Homepage Not AvailablePrivate Messaging Not AvailableAIM Not AvailableICQ Not AvailableY! Not AvailableMSN Not Available
Date Joined May 2007
Total Posts : 447
 
   Posted 11/3/2009 11:19 AM (GMT -8)    Quote This PostAlert An Admin About This Post.
Hi Chuck,
A while ago I played with a Parallax wireless module, I think it was bluetooth. I'll try to dig it back out and see if I can help. Can you send me what you've done so far by pm?
Hanno


Co-author of the official Propeller Guide- available at Amazon
Developer of ViewPort, the premier visual debugger for the Propeller (read the review here, thread here),
12Blocks, the block-based programming environment (thread here)
and PropScope, the multi-function USB oscilloscope/function generator/logic analyzer

Back to Top
 
[ << Previous Thread | Next Thread >> ]
New Topic Post Reply Printable Version
 
Forum Information
Currently it is Saturday, November 21, 2009 11:35 AM (GMT -8)
There are a total of 393,859 posts in 55,536 threads.
In the last 3 days there were 84 new threads and 710 reply posts. View Active Threads
Who's Online
This forum has 17692 registered members. Please welcome our newest member, old guy.
56 Guest(s), 13 Registered Member(s) are currently online.  Details
Siri, keith_kw, Jay Kickliter, Mike Green, Bob Lawrence (VE1RLL), Dogg, dMajo, hover1, ErNa, Harley, Tubular, Leon, MicroDirk