Simply all I'm looking for is for a team that uses MoTeC telemetry with the remote logging option that would be happy to provide me with one of your telemetry images. Thanks.

Shameless bump. I'm hoping there's a team out there in FSAEland that runs this kinda setup otherwise I'll have to look somewhere else.

I'm not aware of any teams using the Motec Telemetry option (too expensive). We accomplish remote monitoring (not logging) by connecting our Motec ACL to a wifi router.

We thought about using it this year...but then we learned the price! You could use a CAN to WiFi module, something like this...

http://www.berghof.com/multime...Ntrol_iCAN_PT_en.pdf

or

http://www.rmcan.com/index.php?id=1149&L=1

Hope it helps!

I don't have any experience with the Motec telemetry, but we have a lot of teams that just use a wireless router with our PE3 ECU. It is very easy and inexpensive since the ECU already communicates via Ethernet. We even have guys hacking routers to increase the power and get very wide ranges. It is pretty simple to do.

Yeah, I've heard of the wireless router option. What we're doing at the moment is using an Ardupilot + IMU board to take a custom dataset from our M400 over serial, add in IMU data and translate it to the MoTeC Telemetry protocol which we then transmit with 900MHz Xbee Pro's to a computer with Telemetry Monitor. Dirt cheap in-house solution. All serial data that goes into Telemetry Monitor is dumped into telemetry images and I was keen to tear some others apart just to learn a bit more about the stream than I could from the demo images that come with Telemetry Monitor.

Is the RS232 active b default? Doesn't it require the telemetry option to be enabled for which you need to pay for??

We have a M800 and I had earlier tried to implement the same method that you suggested, but the folks at Motec convinced me otherwise. I haven't checked if the RS232 works without the option exclusively enabled, but feed-back would on the same would be appreciated.

RS232 works just fine on a non-Telemetry enabled MoTeC hundred series ECU. The difference is the output is not the telemetry protocol, it's CRC32. The problem is that MoTeC won't give you the specifications of their telemetry protocol because they'd like you to buy their telemetry option. So instead I reverse engineered it and used a programmable board to translate from CRC32 with a custom dataset into the telemetry protocol.

As far as I can tell this is completely legal because Telemetry Monitor has no EULA specifying that it cannot be used with non-MoTeC hardware. But I'm going to have a bit more of a look around to make sure I don't get my arse kicked for releasing their telemetry protocol I reverse engineered.

I had a chat to my team about it and they'd rather hold off releasing any details of the telemetry protocol for two reasons. Firstly we figure that it's probably not a good idea to piss off a company like MoTeC and secondly we feel that our own MoTeC compatible telemetry system gives us a leg up on the other teams in design. One day I may have a chance to release it, but it won't be any time soon unfortunately.

MoTeC M800 Set 3 Data Protocol

Maybe this can help?

Achieving telemetry over the CAN network is ridiculously easy if you approach from the right direction. Understanding the protocal and CAN opens up the ability for large storage data logging but that's a different story

The protocol you've posted is the dataset you can get from any Hundred Series ECU. The one they're asking about is the Telemetry Protocol that Telemetry Monitor uses. It's a very different protocol and what we've been doing is taking a CRC32 input and translating to a Telemetry Protocol output. Telemetry Monitor won't do anything with a Dataset 3 stream.

Probably a good idea to keep this to yourself.

Jamie@MoTeC

Figured as much.

So isn't possible to connect telemetry via CAN ??

You can plug a UTC into a router running OpenWRT with the USB/Ip add on and transmit from the router to your computer, should work fine for viewing ECU monitor wirelessly.