openXsensor test version

[jhsa]

What current sensor are you using?
VFas is the correct field to display the voltage.. check with a voltmeter and confirm that the measured voltage is correct.. if not, you have an offset option in the code and you can correct it there

I hope you recover quickly..

João

[ethebee]

What current sensor are you using?
VFas is the correct field to display the voltage.. check with a voltmeter and confirm that the measured voltage is correct.. if not, you have an offset option in the code and you can correct it there

I hope you recover quickly..

João

Hi João,

Yes - I checked with a voltmeter and also adjusted the offset. The voltage reading I get looks good!

Current sensor is the ACS712 bi-directional 30A type. So it did not matter which way round I soldered the wires. If necessary I will cut off the shrink tubing and re-solder them the other way round to correct the display - just hoping I could make a simple code adjustment to turn it positive again (similar to what was provided in the original openXVario).

Cheers

Eric

[jhsa]

can't help you much in there. I'm sure Rainer will jump in with a solution

[pwarren]

Had some fun getting openxsensors to compile on debian, so I have a patch, I think it'll help on any case sensitive OS.

svn diff on rev 193

Hope that helps

[pwarren]

Although, now that it's compiling, it doesn't seem to be working correctly when loaded on to the arduino. Using the openXvario branch, with debug mode, I get real time changes to the data coming out the serial port. With openXsesnor, the data coming out only changes when I reset the arduino. So, my patch may have broken something.

Also, nothing seems to be coming out of pin 3 (the serial out to the RC receiver), on both branches, should I be seeing something when I hook that pin up to the RX port of an FTDI?

[jhsa]

On my openXsensors is pin 4 that outputs the serial for the receiver not pin 3 as far as I remember..
Unless you changed that of course, but I post this just in case

João

[pwarren]

Ah, that would explain that part of things, thanks! Soldered the wire to the wrong pin! Will attempt to modify the code to output on pin 3, at present, that'll be easier than resoldering

[jhsa]

I'm not sure but I think you just have to change the pin number in the code. config.h tab..

João

[Andrewjfernie]

I think that arduino code is a "easier?" version of the C code.. And it can only be compiled by the arduino IDE?
For other stuff I would use the AVR Studio software, but I guess it won't compile arduino?
Anyway, I find the arduino IDE easy enough to work.. Note that for example on other applications you select the chip you want to program. with arduino you select the arduino board you want to program. It's not quite the same..

Try Visual Micro (www.visualmicro.com). It is a plug-in for Visual Studio 2008-2013 and Atmel Studio 6.1 that lets you build and load Arduino projects. There is an option for a debugger that can be purchased, but the build/load is free. Atmel Studio 6.1 is free, so no issue there if you are not already using Visual Studio. It won't work with the free ("express") versions of Visual Studio as they don't support plug-ins.

[pwarren]

I'm not sure but I think you just have to change the pin number in the code. config.h tab..

João

Well, on closer inspection, my serial out is in fact on pin4, but I get nothing from it via my FTDI usb thingo, but I suspect that it's the problem, not my vario!

[Kilrah]

Frsky uses _inverted_ serial, so if your FTDI does TTL level you need to either invert the signal or reconfigure the FTDI chip to invert line polarities.

Sent via mobile

[ReSt]

In openxVario and openxSensor you can define the polarity of the output signal as positive or negative

Reinhard

[pwarren]

Ah, that would make sense then, I should read the code more often