Marc S.
100 W
Ykick said:Certified by you is good enough for me, LOL....
+1
Ykick said:Certified by you is good enough for me, LOL....
Look first post, by Justinrhinejuice said:Oh I fear the pilot run won't be the 220/240v plug in the wall option in looking for???
Plug itself is easy to change. :wink:....corrected 100-240V input, 95% efficiency, graphic display screen etc.
justin_le said:(MacOS will have to wait till next week)
BVH said:Well if I can do it wrong, then I will. Using the older version of the editor, I exported my custom profiles then exited the program. Downloaded the new suite and put the S in bootloader mode. Then launched the new suite and hit the green button and I get the message "An error occurred while importing profiles from HEX. Invalid type field. Please try again". So I went back in under the old suite and erased all profiles.
Then I was no longer able to get into bootloader mode until I created 1 profile.
justin_le said:For those wondering about the charge graphics behavior, it works as follows:
Voltage Scaling = Vmax/2 to Vmax, with the max voltage being up to 75% of the screen height
amberwolf said:It's probably just me, but that seems like a wierd way to do it, as it won't have nearly the detail it could have (not like it should matter much, but it seems like a waste of capability, especially if troubleshooting a pack could ever be done from the charging graphs).justin_le said:For those wondering about the charge graphics behavior, it works as follows:
Voltage Scaling = Vmax/2 to Vmax, with the max voltage being up to 75% of the screen height
BVH said:I see what I was doing wrong. After launching the program, I was clicking the green connect icon, and then clicking the big "connect" button instead of going up to FILE/Update Firmware ect, ect process. All is good now.
I remeasured my total cable resistance with my calibrated 4-wire Kelvin benchmeter and leads and got the same as before .161 Ohms (with my added cables and Watt meter in-line) so I set the Satiator at .2 as you suggested a while back. You mentioned in that past post that I could set it a bit higher if I desired a bit shorter time in CV. What would be a good setting?
justin_le said:Has anybody else had issues with this latest software and firmware upload? It would be really great if all those who follow this thread and have a Satiator give it a go so we know that the code is fairly proven before have the V1.0 launch party and all.
For windows:
http://www.ebikes.ca/downloads/Satiator_Suite_Windows_v0.99j.exe
For Linux:
http://www.ebikes.ca/downloads/Satiator_Suite_Linux_v0.99j.tar.gz
Please install!
neptronix said:I have a question about longterm 63v operation.
I want to set up at 15S battery pack and charge it to 62.5v at 5.5 amps indefinitely.
Am i stretching the limits of this charger doing that?
I'm assuming that you're using some components with maximum voltages right around that point..
Preferably, i'd like to run 16S or 18S and am waiting for a higher voltage version of this to come out.. but 15S will do the job.
Well, since you asked...
I updated my two Satiators from 0.916 to 0.99j using the Windows updater on Win7 Pro. But I had two problems.
1) I had a hell of a time getting connected to the Satiator. I'd put the Satiator in "Connect to PC" mode, then press the Connect button, but would get an error about some data being in the wrong format whereupon the Satiator would revert unbidden to normal mode. I finally was able to connect consistently by making sure that I had no Profile list, either default or my own, loaded into the Software prior to connecting. If I had any profiles listed, the software wouldn't connect.
BVH said:Well, since you asked...
I updated my two Satiators from 0.916 to 0.99j using the Windows updater on Win7 Pro. But I had two problems.
1) I had a hell of a time getting connected to the Satiator. I'd put the Satiator in "Connect to PC" mode, then press the Connect button, but would get an error about some data being in the wrong format whereupon the Satiator would revert unbidden to normal mode. I finally was able to connect consistently by making sure that I had no Profile list, either default or my own, loaded into the Software prior to connecting. If I had any profiles listed, the software wouldn't connect.
Just taking a guess here....This sounds close to what I was trying to do if I am reading it right. I'd click the green CONNECT icon in the upper left corner then I would click the big CONNECT button in the window that opened and would get the "wrong format" error. If I had read the word-by-word instruction Justin posted closer, I would have seen that once I clicked the green CONNECT icon, I should have gone to "File" on the upper menu bar, then clicked "check for firmware update" then to "Update Firmware", then the advanced button, clicked delete profiles and finally clicked the big CONNECT button. Maybe this will help others not to make the same error I did.