Author Topic: Advice sought on applicability of MoteMega.  (Read 2166 times)

LEDAero

  • NewMember
  • *
  • Posts: 1
Advice sought on applicability of MoteMega.
« on: April 29, 2015, 10:59:20 PM »
We have an autonomous vehicle controller that allows you to input a track and have the vehicle follow it.

We were going to use a Mega with a bluetooth ttl device and an SD card for communicating and logging, but after looking at the specs of the MoteMega, it looks like I can save a lot of assembly hassle and get one device to do it all. Currently we have a prototype shield on test for sketch uploading and logging and it works well. We were already looking at utilising 915MHz transceivers for 'return to base' and 'here I am' functions.

What I am unsure of is how to communicate from my laptop (and more importantly, from customers laptops) to the Mote.

Do I have to set up another Moteino as a gateway, or could I use a 915MHz usb/serial/ttl device?

As it stands now, I can distribute a hex file update and my customers can run a batch/shell script that connects to bluetooth, uploads the new sketch and restarts, with little computer knowledge - they just need to connect to the BT and the script takes it from there, prompting them for the file, etc.

Is it likely I can achieve the same level of user hands off with this, or am I going to have to deal with getting users installing python, knowing what their virtual port numbers are, etc.? (in which case, it's a no-go. )

I am happy to do app packaging (my previous life...) and development, but having to get customers delving into software isn't going to work - we have a lot of elderly modellers (heck, our main developer is 80 next year :) ).

Felix

  • Administrator
  • Hero Member
  • *****
  • Posts: 6866
  • Country: us
    • LowPowerLab
Re: Advice sought on applicability of MoteMega.
« Reply #1 on: April 30, 2015, 08:16:43 AM »
We have an autonomous vehicle controller that allows you to input a track and have the vehicle follow it.

We were going to use a Mega with a bluetooth ttl device and an SD card for communicating and logging, but after looking at the specs of the MoteMega, it looks like I can save a lot of assembly hassle and get one device to do it all. Currently we have a prototype shield on test for sketch uploading and logging and it works well. We were already looking at utilising 915MHz transceivers for 'return to base' and 'here I am' functions.

What I am unsure of is how to communicate from my laptop (and more importantly, from customers laptops) to the Mote.

Do I have to set up another Moteino as a gateway, or could I use a 915MHz usb/serial/ttl device?

As it stands now, I can distribute a hex file update and my customers can run a batch/shell script that connects to bluetooth, uploads the new sketch and restarts, with little computer knowledge - they just need to connect to the BT and the script takes it from there, prompting them for the file, etc.

Is it likely I can achieve the same level of user hands off with this, or am I going to have to deal with getting users installing python, knowing what their virtual port numbers are, etc.? (in which case, it's a no-go. )

I am happy to do app packaging (my previous life...) and development, but having to get customers delving into software isn't going to work - we have a lot of elderly modellers (heck, our main developer is 80 next year :) ).

I must say I'm somewhat confused by the terminology. Are you referring to the Arduino Mega? Then the Mote is a Moteino? Are you saying you find Moteino as a better fit and are asking for clarifications how to use it?
What is a 915mhz usb/serial/ttl device ?
Please explain in short concise and with complete terms so we can better answer. Ie if you include the Mega word, please specify if you mean an ArduinoMEGA or MoteinoMEGA, very different things, etc.

TomWS

  • Hero Member
  • *****
  • Posts: 1930
Re: Advice sought on applicability of MoteMega.
« Reply #2 on: April 30, 2015, 10:12:40 AM »
Just to make sure that I understand:
You currently  have a prototype that uses bluetooth but you are thinking of replacing bluetooth with the RFM69 radio?
The device potentially  communicates with two endpoints (A client  laptop and some kind of monitoring unit)?

What kind of  range do you need to both endpoints?

 Is there any reason the client needs to be on the same wireless protocol?

Tom