Ok...thanks Rowan.....but I'm 12,000 miles from my PC at the moment, so that will have to wait a couple more weeks☹️.. But I didn't realise that serial to bluetooth was encoded in a different way to 'bog standard' serial (technical term).. I thought 'serial' was 'serial', and that it was just the signal levels(like TTL and RS232) that varied...so I can take some time to research a little more into BT...J
There's no difference in the signal level transmission, but instead of just sending the data as ascii characters in a CSV type format, each value is broken down into an identifier and value and packed into a 5 byte packet. This keeps a very low data rate (in hindsight, far lower than we needed to get it), but has it's drawbacks - such as the data isn't human readable with a standard serial interpreter.
...so just thinking ahead... Going along with your suggestion of 'squirting' out a .csv file....and progressing with caution at this stage....As I only need to transmit, there is a library available for 'Software Serial, Transmit Only' on Github...Can I assume it's ok to 'include' that, and output to (say) Pin 12 (D9)?
....ok...but was just thinking about tying up as few pins as poss...but as the pins are available, I guess it would make more sense to use a well tried and tested library...at least in the first instance.. Thanks again..
Hi Rowan...Hope this finds you and yours well!! Back at the sharp end now...Re: the ramp routine you kindly wrote for me: I wonder if you would have any theory on the following... We (Pods..Chipping Sodbury School) now have the echook completed..When checking the board with the echook sketch, plus the throttle ramp, I noticed that (almost) every time the throttle is opened, for a fraction of a second, just as the PWM is reaching 100%, the output drops to zero, before returning to 100%....It is only for a fraction of a second.(.doing a video frame count, I reckon it's about a fifth of a second)...I first noticed it with the onboard PWM LED.. I reloaded the original stand alone ramp sketch you sent me, and the glitch is there also..I just hadn't noticed before.. I think we can get away with the Mark/Space jitter, but the drop to zero would definitely be noticed in the car... I have a few seconds of 'scope video of the glitch if of any use... Sorry to be a pain, but any help would be appreciated.. Thank you. John
....Just an afterthought...The Nano in the echook is not the one I did the original test with, so I wondered if it could be a problem with the new Nano...but I fired up my original nano..and the problem is there also..J
Last Edit: Mar 24, 2020 19:17:10 GMT by littlejo44