Any strange behaviour, crashing issues etc, post them here! Problems compiling the firmware should go in the General support section rather than here
By theonewithin
#55445
pazi88 wrote: Sun Feb 20, 2022 5:31 pm
theonewithin wrote: Sun Feb 20, 2022 10:35 am
Maybe just leave the Mega comms alone? Why does it need to be any faster?
Why would you want your car to be faster?

The old comms is still there as option untill new comms is matured enough.
Old comms option doesn't change anything.

Acts the same way.

Your analogy is stupid.

You can use that same analogy to say why even support the Mega when the Teensy exists because it's "faster".

What benefit is there for faster comms in the Mega when it's not required?

Faster doesn't mean better. Especially when all it does is break things.
By theonewithin
#55446
LPG2CV wrote: Sun Feb 20, 2022 2:22 pm @theonewithin

Just listening to some chat on slack, and apparently, you can disable the new coms in project properties

also appears to be impacting clones rather than original Mega2560.
Switching to old comms changes nothing.

Still acts exactly the same.

If it requires real Arduino then may as well dump using the Mega.

$65AUD is not worth.
By theonewithin
#55447
LPG2CV wrote: Sun Feb 20, 2022 11:21 am It would be interesting to know, and add feedback, if re calibrating the sensors resolved the issues. :)
Crank trigger isn't something you calibrate.

So completely irrelevant.
User avatar
By jonbill
#55448
fwiw, it's been fine on my 0.4.3c. Just go back to the version that you were using before until the next release, as you said. Not something to get wound up about.
User avatar
By pazi88
#55450
theonewithin wrote: Sun Feb 20, 2022 6:18 pm

Switching to old comms changes nothing.

Still acts exactly the same.

If it requires real Arduino then may as well dump using the Mega.

$65AUD is not worth.
There are many arduino clones that use 16u2 that genuine arduino uses too, instead the ch340. And those cost virtually same. But ch340 works too with correct drivers.
By theonewithin
#55456
My board has a 16u2.

It doesn't work correctly.

Once I state this on Facebook, suddenly Josh vanished...

The new aerial comms are clearly a problem that for some reason no one wants to admit to.

Still yet to see why they need to be fast on the Mega?

Sure on the other boards to enable extra functionality but the mega isn't going to be able to do. SDcard loggin.
User avatar
By pazi88
#55457
theonewithin wrote: Mon Feb 21, 2022 2:54 am My board has a 16u2.

It doesn't work correctly.

Once I state this on Facebook, suddenly Josh vanished...

The new aerial comms are clearly a problem that for some reason no one wants to admit to.

Still yet to see why they need to be fast on the Mega?

Sure on the other boards to enable extra functionality but the mega isn't going to be able to do. SDcard loggin.
Of course faster is better. The possible issues are being investigated. I just managed to reproduce the new tune burning issue, so that's step forward trying to fix that. The code is same for all mcu's where ever it's possible.
By theonewithin
#55458
How is faster better though...

Once again.

Just because something is faster does NOT mean it is better else Speeduino would have dropped the Mega years ago.

Especially if it's less stable which is what the new comms is showing to be.
blitzbox

12v is unusual. You could probe it using 5v and se[…]

Hello to everyone! I am starting this thread beca[…]

STM32 development

Do you mean the "full clean" com[…]

The Max9926 or A2 , Is there anything else i wou[…]

Still can't find what you're looking for?