Cycle Analyst V3 preview and first beta release

that did help a lot. i desoldered the SP pad and it still shows 0.6-0.7V. the reed switch as such closes with a magnet moving by. i guess i'll need to contact justin. fortunately i have a spare v3 lying around - it's just that all wires are customized by me and i have to do a lot of soldering.
 
So - no arrow flipping when you shorted the unsoldered pad?

This seems like an odd out-of-the-blue failure. When did this occur? What firmware were you running?

Yep - my first bike has a radically customized CA installation and I hate to touch it. The only plus side is that everything is connectorized so I can pull the CA and reattach all the short custom cables on the bench - I hate soldering and crimping in free air standing over the bike...
 
Hmm - okay. Justin is in France just now, but Robbie and the guys can address your issue. It does sound like it took a static hit and something went south. Maybe you could get Justin to stop by for a consult on his Sun Tour excursion...
 
gronph said:
are there any news with the Bluetooth/Android thig?

I have no idea who is working on it or what it is.

I have an implementation of BlueTooth that I developed for a Google team (around an Arduino) that provides a framework for an Android Phone. It is implemented using MIT APP Inventor 2. Data is passed bi-directionally in ASCII between the Android Phone and the Target. There is a heartbeat. You can send commands from the Android and collect state data with verification (CRC).

Key is keeping the BlueTooth alive.... at least in my implementation... as I specified the $10 jank dongles you can buy on Amazon.

Happy to share it if I can - MIT App Inventor 2 is a purely graphical language like LabView and the compiler is free to use. Anything that runs on Android can be ported over to the CA by a professional in half a day.

Once the data is moving back and forth... users (the community) can move legos around to make the front end look however they like. There are tons of tools for buttons and displays.

It requires little to no programming experience... but then... without understanding of programming paradigms most folks wont get too far with it.

-methods
 
teklektik said:
Hmm - okay. Justin is in France just now, but Robbie and the guys can address your issue. It does sound like it took a static hit and something went south. Maybe you could get Justin to stop by for a consult on his Sun Tour excursion...
justin and team are AWESOME! i still have to find a company that can beat grin's support! those guys (an you tek!) rock!
 
izeman said:
justin and team are AWESOME!

Can confirm. Here's Justin making a house call at my workshop last month, hacking an analogger to work with the new solar firmware.

Justin hacking analogger.jpg
 
Justin is Unreal...

He came to my house and split a cord of wood, then built a chicken coup from scratch. :shock:
The guy is 120% legit and so are the tools that he provides.

Whatever needs to be solved will be solved -
And...

I recommend the CA to Teachers who are looking to do any kind of classroom work in this ethos.
I try to spec the CA on any project I work on (and have... there are evil robots roaming around with CA's on them :mrgreen: )

-methods
 
Close... but more like this:
.
.
.
IMG_0024.jpg
source: EM
.
.
.

Thats not the "evil one".
The Evil one was 4 hub motors on 10" custom machined omni-directional wheels running 60V autonomous/remote control
We chased Astro Teller out of the lab with it- literally.

The machine would move in the most creepy way... it could swing and pivot and had no preference forward, sideways.. :shock:
(Hard to describe in words - no longer have the videos)

Suffice to say... it was a terrifying implementation of what future security robotics could end up being.
No escape if one gets after you.

Justin was hesitant to support our project :mrgreen:
We gave him assurances that we would "kill it" if it got out of control.

(All the robots had a remote kill which required physical human boot-strapping to bring back up. Rule #1 to autonomous beings)

-methods
 
Hey izeman-
Looks like you got a CA that has the calibration firmware that is used by manufacturing to calibrate each device. This is supposed to get re-flashed with the current production release after calibration, but yours looks to have missed the last step (interrupted during lunch break?).

Just set up to flash your firmware of choice and power cycle the CA to get the download underway.
 
v3.11b3 Released

Thanks to Marc S. sleuthing out a display bug, we have 3.11b3 available via the CA Setup Utility. Press 'Get New Firmware' on the toolbar and select the 'Download beta firmware' checkbox.

This fixes a battery 'hot swap' display issue and improves the PAS start time a bit as well.

If you are still using 3.1, we strongly recommend that you upgrade to this release to address a couple of significant bugs in 3.1.

This 3.11b3 release is a Release Candidate for the 3.11 production release, so we would appreciate a good thrashing by beta testers. We would like to get 3.11 formally released at end of next week.

So, download away and give it a workout!
 
Thank you for your service teklektik!

-methods
 
Justin is a special and unique guy.
Every time he comes around I am inspired to create the positive change that I want to see in the world.

The CA is my favorite tool... and I have convinced our Accountant that we need THREE for our current builds :wink:
(plus one for my test bench, and one for each DCS Power supply, and... :mrgreen: )

-methods
 
i need to raise that topic once again. i still don't fully understand all this limiting gain stuff. quite impressive to still have lack of knowledge after using the stuff for over 5 years now.
i programmed the newly received CA from grin with 3.11b3, which by the way did not work under windows7. worked flawlessly with linux ubuntu though. some serial issues i guess.

but back to the limiting stuff. i got 3 setups. legal 600W-25km/h, 2000W, and 3500W.

i set my throttle to "pass-thru". when riding the W limiting flag comes up. the controller COULD deliver (slightly) more amps/watts then 3500W, set to 60A battery @62V hot from the charger.
the "power settings" are 99A and 3500W. what GAINS are relevant in that case? Amps gain AND Power gain? or just the power gain, as the AMPS are never reached? does one of them influence the other?
only thing relevant to me is POWER, as this is constant over depleting battery, and can stay constant from full to empty battery.

the tip to raise GAIN until surging happens, and lowering it afterwards by 30% is a very long process, and i'm never sure that i got the optimum setting.
 
next questions: while replacing the CA i wanted to use the "new" digital aux switch feature as well, which is not covered yet in the unofficial CA guide afaik.
i once bought these little switches as a direct replacement for the 3pos switch, and would like to use it, but i haven't found a schematic. read something about diodes and stuff, but am unsure how to wire it exactly.
maybe tek can help? :)


Screenshot from 2018-06-23 17-06-43.png
 
Sure -
I pulled down the DigiAux HowTo document when we switched to Schottky diodes and haven't had the time to update the doc. But since this is the second request in a week or so, I'll get on this. Should be able to post up the stuff after the weekend.

Those switches look good and they should snap right into a standard 3-position-switch mount. :)
 
My Roxim X4 light is fed from my CA3. On it's first night use it wouldn't light up completely, as in my testing. Am I missing something with my CA3 settings? I changed nothing, just turned it on the night before last and it's really dim. The rear LED lights up completely form the same CA3 source. Sound like a light problem, but I find that odd....
 
could it be that there are still (again?) issues with shunt values that are ignored by the CA setup (3.11b3)?
my shunt is 1.43mOhm. whenever i enter it it jums back to 0.9mOhm. no matter if i choose high/low current shunt.

tek, maybe you've overseen it, and you could make this gain stuff more clear. three posts above. it drives me crazy not to understand how this works :lol:
 
izeman said:
my shunt is 1.43mOhm. whenever i enter it it jums back to 0.9mOhm. no matter if i choose high/low current shunt.
I believe your issue is caused by bogus protected settings for Hi/Lo amplifier gain. I think that when you were manipulating the Calibration firmware on your new CA you may have inadvertently pushed the gain settings to some bad values.

We are talking about these settings that are enabled in Setup Utility with the Preferences menu:


CA3_protectedCalibrationSettings.png


There are a couple of ways to do this, but since I know this is a new CA with no old settings files, let's go with the simple shotgun approach to get things working quick and easy: Reflash 3.11b3 but select both checkboxes on the pop-up window. This will clobber everything in your CA and restore it to generic factory defaults. If you wish, you can recalibrate your voltage as you did before.


CA3_calibrationReset.png


General Note to CA Users: The unique per-device factory calibration is read by Setup Utility whenever you do a 'Read CA' even if the protected settings aren't displayed. It is a good idea to read a new CA first thing and store away that file in case you ever get in this situation. The original file can be written to the CA to restore the unique calibration settings and then you can flash the currently interesting firmware over them.
 
and i'm back again :)

though i already adjusted my throttle handling to my mid drive (always applying a little throttle to put strain on the chain and drive train), i must say it would be fine to have this applied all the time.
i can't remember how far we discussed this feature suggestion, but i could think of it that way: if speed > 0, apply a pre-defined amount of current. maybe raise this current related to speed?!
i think this is something to be implemented quite easily - sure i have no idea how much precious memory would be needed for it.
 
Back
Top