teklektik wrote:(The default Ti of 0.37v when disconnected seems odd - I would have expected it to be pulled down to 0v, but that's another question not directly related to this situation....)
Joe Perez wrote:I'm going to take a wild guess and say that this may be related to hardware rather than software.
When I was tinkering with my CA3 to accommodate an LM35 temperature sensor (as opposed to the officially-sanctioned LM335 or NTC sensors) I found that even after removing the "NTC" pullup resistor, my Temp input tended to float high and was influenced by the throttle.
Apparently there is some crosstalk between the various analog inputs (or at least between the throttle in and the Temp in) owing the multiplexed nature of the A-D converter. ... In my case, this was solved by placing a ~390 ohm pulldown resistor between the "NTC" pad and ground.
Could it be that in the absence of an actual throttle sensor that the same phenomenon is taking place on the throttle input line? I'll bet you €1 that putting a resistor between the throttle input and ground will make this go away.
Joe Perez wrote:Justin, I have a bit more data on the speedometer issue, but I'll address your question first:
1: If I am already moving forward at a decent rate of speed (pedaling) when I switch the unit on, I don't see the phenomenon as dramatically on the realtime speedo display (it might only get up to 50-100 MPH) however MaxS still records a peak in excess of 400 MPH.
2: If I switch speedo units to Km instead of Mi, the glitch goes away completely. When I switch back to Mi, it comes right back.
MotoMel wrote:Is the v3 coming onto the market any time soon? Thx.
lizardboy wrote:Hi Justin;
I'm setup in miles not Kms sorry. Although I have switched back and forth before
I had a unrelated problem recently where the bike cut out and would only run the motor for a quick jolt. I checked the output signal in the real time menu and it was working perfectly. It seemed exactly like there was a problem with the hall sensor wiring so I checked everything and found nothing wrong.
the odd time that I've tried the throttle button, the system it seems to work after but is a bit jerky in current throttle and will cut out once in a while but can be reactivated by twisting the throttle. Cycling the main power seems to eliminate it. I've still got all the limiting turned off.
justin_le wrote:#1) New Display for showing the diagnostics which should help with some system debugging. The top line shows the reatime input and output throttle voltages. The bottom left has a set of characters showing which if any limits are currently active. Each of the overcurrent current, power limit, max speed, low voltage, and threshold temperature, are represent by their respective letters, and go from lower to upper case when limits are reached.
justin_le wrote:In the meantime, we still have a couple dozen from the Pilot batch which will now be programmed with the Beta16 code and made available again for beta testers. More details on that tomorrow.
justin_le wrote:Some of the minor things changed since Beta15:
* Leading zeros are eliminated for items in the setup menu. I'm not 100% sure about this, the leading zeros always bugged me a bit, but then toggling digits into a 'blank' space has some oddness too.
justin_le wrote:Plus two more significant updates:
#1) New Display for showing the diagnostics which should help with some system debugging...
justin_le wrote:#1) New Display for showing the diagnostics which should help with some system debugging. ... The bottom left has a set of characters showing which if any limits are currently active. Each of the overcurrent current, power limit, max speed, low voltage, and threshold temperature, are represent by their respective letters, and go from lower to upper case when limits are reached.
teklektik wrote:Now that we have these handy limit flags to call attention to internal state, I notice that even with the temp feature disabled, temp limiting is active if Temp->MaxTemp is incorrectly configured less than Temp->ThrshTemp (e.g. limiting is in effect with: 'disabled', apparent temp = 0.0 degrees with no attached sensor, MaxTemp=899 , and ThrshTemp=999 ).
FWIW I vote for leading zeros. Since there is no shorthand available to skip entering them (e.g. enter '10' instead of '0010'), I find the blank space unhelpful for data entry. Mentally measuring the space to get the needed alignment seems less intuitive than simply using the leading zeros as visible place holders.
justin_le wrote:I'll make a note to address this in next firmware so that it will constrain input values that are outside of sensible range. So MaxTemp will always be forced higher than ThrshTemp when you try to change it, and then the above scenario could never manifest.
justin_le wrote:Perhaps the best option might be to hide leading zeros when you are scrolling through the display to look at the values, but then have them appear the moment you hold the button to edit any of them?
Bartimaeus wrote:Will the v3 still have the 5mA limit for powering external circuits via the 5v pin?
Trying to run Sparkfun's OpenLog from the CA, and it just barely works at the 1Hz data rate. Every time it goes to write the screen flickers, and since the peak current draw is listed as 6mA for the OpenLog I was going to look into re-programming it so the indicator LEDs wouldn't flash when writing to the microSD or as a last resort breaking/desoldering the LEDs. But if the new one has more leeway it won't be an issue anymore.
Users browsing this forum: No registered users and 3 guests