I am looking at getting Fusion Brain and connecting it to a carputer to display gauges for very sensors like boost Air Fuel ratio and other things like that. My question is I read that RR updates once every second but then read a few pages back that the screen refresh rate for RR was 100ms or 1/10th of a second which would be acceptable but I would really like something a little faster is that even possible?
After reading a bunch of threads on creating flash gauges I have a few questions that I hope people can answer. I have created and attached one gauge so far and I feel like if I can completely understand what all goes into creating one gauge the rest should be easy as pie. But I do have a few questions
- I know that the gauge says boost on it but for understanding what is all going on I would like to be able to just have it read in cpu temp or cpu usage or just any input that I can use or simulate to understand how everything works until my fusion brain gets here.
- With that being said if I want to take a input between 0-3.3v for the fusion brain how do I convert that to a number, do i do that when im creating the flash gauge in swish or when Im imputing it into RR?
- Also is it better to create gauges in flash or swish?
Is anyone successfully using the latest version of this plugin with a v1 brain? I recently tried to upgrade everything on my system and with the latest version I could connect fine, but every time I toggled a digital output on it would not stay on constantly. Just wondering if the error is on my end or an incompatibility with the original brain firmware.
So after testing on the laptop I see the same behavior. Out of curiosity what timer interval do you use for send/receive and what value do you use for shutoff time (time=1.2^x) when communicating with a v3 brain?
I've been playing with my own plugin solution based on mx270a's work and the low level info document for a v3 brain and while it's significantly better (as far as the connection) than the current version of this plugin it still drops out occasionally. As far as I can tell mx270a's program uses 0 for the shutoff time and I haven't had a chance to test with a higher number yet to see if it fixes my problem.
My v3 code is identical to mx270a's work way back when. And the interval used by default is 1 second, but it can be adjusted in the rrfusion_settings.xml file. I'm away from my dev machine with RRFusion until monday but i can share the read/write code with you then. Kinda odd that i'm using a v3 in the car and have been for years but some people (not just you) have this same issue.
The solution to my problems lied entirely in the shutoff time interval. I increased that to close to a minute (Probably doesn't need to be that high) and everything has been working great since using my kang of mx270a's code converted into a plugin.
I don't really see any negatives to having the timeout value set that high since as soon as the carpc hibernates the fusion brain looses power and everything turns off anyway.