Page 10 of 17

Re: Firmware developent status

Posted: Wed Jan 04, 2017 1:20 pm
by AndreyB
Do not follow. We have usbttl chip on both boards?

Re: Firmware developent status

Posted: Fri Jan 06, 2017 8:54 pm
by AndreyB
I am a bit bored on vacation so doing some memory usage clean-up, a lot of "set_smth X" (with underscore) commands are not "set smth X" (with a space) - this would allow a more efficient data structure this would reduce memory consumption.

Flying home tomorrow :)

Re: Firmware developent status

Posted: Sat Jan 21, 2017 1:50 am
by AndreyB
https://sourceforge.net/p/rusefi/tickets/338/ fixed - console flash/erase buttons work again. It was about discovery to f429disc1 transition if you remember the part number change - new board firmware requires newer version of openocd.

Re: Firmware developent status

Posted: Tue Feb 07, 2017 12:05 am
by AndreyB
Just fixed a bunch of defects around event inputs - more pin options for shaft sensors, pin options for VSS and frequency-based MAP. Also better error handling if invalid pin is selected as an input, also some TS options were wrong.

Re: Firmware developent status

Posted: Wed Feb 08, 2017 5:24 am
by AndreyB
Just added v10 and v12 firing orders support.

Re: Firmware developent status

Posted: Thu Feb 09, 2017 6:00 pm
by AndreyB
Blatantly soliciting donations: Build server in my living room is a Dell OptiPlex GX620 running a https://en.wikipedia.org/wiki/Pentium_4 2.8 processor made around 2007.

Anyone has an unneeded desktop or server?

Re: Firmware developent status

Posted: Fri Feb 10, 2017 3:39 pm
by mobyfab
I can give you access to my jenkins+docker instance once I'm done migrating it.

Now again, if you were using github... https://docs.travis-ci.com (free)

Re: Firmware developent status

Posted: Fri Feb 10, 2017 3:54 pm
by AndreyB
mobyfab wrote:Now again, if you were using github... https://docs.travis-ci.com (free)
I will check them since https://github.com/rusefi/rusefi

Ideally it has to be local because I have integration tests with real stm32 hardware but I guess I can live with just arm compiler.

Re: Firmware developent status

Posted: Fri Feb 10, 2017 4:12 pm
by mobyfab
If you need hardware, I have an old server tower i'm not using, 2x Xeon L5420, 8Gb of ram, but it's very heavy and noisy...

Maybe you can do the CI on travis, and still have the other tests on your server.

Re: Firmware developent status

Posted: Fri Feb 10, 2017 7:39 pm
by AndreyB
mobyfab wrote:If you need hardware, I have an old server tower i'm not using, 2x Xeon L5420, 8Gb of ram, but it's very heavy and noisy...
Wrong continent, I am afraid to think about shipping :(

Re: Firmware developent status

Posted: Sat Feb 11, 2017 6:20 am
by tomiata
I have a dual xeon dell 2590 rack server and an hp workstation xeon machine or two, but they are very heavy. Shipping anything seems impractical.
Could you do builds in the cloud and then transfer a release binary via automated script to your local machine for test physical testing?

Or find an ebay deal. I can pitch in some.

Re: Firmware developent status

Posted: Sat Feb 11, 2017 1:02 pm
by AndreyB
Intel® Xeon® Processor E5-2690 v3 this is pretty recent? Can you check shipping?

If not I am starting to shop local like https://newyork.craigslist.org/mnh/sys/5955888346.html

Re: Firmware developent status

Posted: Sat Feb 11, 2017 4:01 pm
by tomiata
russian wrote:Intel® Xeon® Processor E5-2690 v3 this is pretty recent? Can you check shipping?
If not I am starting to shop local like https://newyork.craigslist.org/mnh/sys/5955888346.html
The Dell I have is like this:
http://www.ebay.com/itm/Dell-PowerEdge-2950-III-3-5-Server-2x-3-0GHz-Quad-Core-32-GB-6x-Trays-DRAC-/332040852116?hash=item4d4f2d5294:g:0pgAAOSwDuJWy3v1

Redundant power supplies. 50 pounds, built like a tank. And CPU is Xeon E5450, from Nov. 2007
http://ark.intel.com/products/33083

I think your local craigslist server would be more practical.

Re: Firmware developent status

Posted: Sun Feb 12, 2017 4:25 pm
by mobyfab
russian wrote:
mobyfab wrote:If you need hardware, I have an old server tower i'm not using, 2x Xeon L5420, 8Gb of ram, but it's very heavy and noisy...
Wrong continent, I am afraid to think about shipping :(
I'm afraid so :(

There's also this one: https://semaphoreci.com

Re: Firmware developent status

Posted: Mon Feb 13, 2017 1:22 am
by AndreyB

Re: Firmware developent status

Posted: Mon Feb 13, 2017 7:18 pm
by AndreyB
russian wrote:Intel® Xeon® Processor E5-2690 v3 this is pretty recent? Can you check shipping?

If not I am starting to shop local like https://newyork.craigslist.org/mnh/sys/5955888346.html
I've also scared myself with electricity costs to run a large server with redundant power supplies - my use-case the device would be idling most of the time, but once in a while I need it to awake and burst out some CPU-intense job.

With all that I've ordered another small factor office PC - pretty much replacing 2007 pc with a ~2012 pc, looks like CPU-wise it should be x4 times faster. Will know how much faster it actually turned out later this week :)

$71 dell optiplex quad-core i5 desktop plus a smaller SSD drive i have in my random parts bin.

Re: Firmware developent status

Posted: Mon Feb 13, 2017 8:10 pm
by kb1gtt
Hmmm, I have a PI3 kicking around. Those are quad core, low-ish energy draw and cheap. I believe you can install Windows on them as well.

Re: Firmware developent status

Posted: Tue Feb 14, 2017 11:23 am
by mck1117
kb1gtt wrote:I believe you can install Windows on them as well.
Under some loose definition of Windows, yes. It's a heavily chopped down version that can only run a single app (universal windows apps only) at a time, and has no support for traditional win32 apps (arm-none-eabi-g++, for example will not run).

If you want to do anything of much value it basically has to be x86-64.

Re: Firmware developent status

Posted: Tue Feb 14, 2017 7:13 pm
by AndreyB
Setting up the new box would be a chance to document the setup - see http://rusefi.com/wiki/index.php?title=Internal:Software:Build_Server

Re: Firmware developent status

Posted: Thu Feb 16, 2017 4:48 am
by AndreyB
russian wrote:$71 dell optiplex quad-core i5 desktop plus a smaller SSD drive i have in my random parts bin.
Ship date: July 01, 2011 end of warranty July 02, 2015 so https://en.wikipedia.org/wiki/Ohio_Reformatory_for_Women has no use for this one.

I am reusing state prison junk, what am I doing with my life.

Re: Firmware developent status

Posted: Thu Feb 16, 2017 9:00 am
by puff
big deal :D

Wondering,what's your workflow? You are developing rusefi using your laptop, then there is a schedule to sync the code (or is it done manually?) to the build server?
Why did you need a newer server? Who cares if it takes several seconds more to build the firmware? Or this build server is used each time you make alterations to the code?

What are electricity costs in per kWatt terms? I think running a low-end computer the whole day in Russia would cost somewhat $5 per month. But I'd say, it's somewhat cheaper here than anywhereelse in the world.
In terms of power consumption it might be much more efficient to run a file server on the home router and host all the files there, starting the build server to build the firmware.

Re: Firmware developent status

Posted: Sat Feb 18, 2017 2:44 am
by stefanst
The feature "Cylinder Cleanup" under cranking doesn't really seem to be necessary. It can be handled under "Cranking TPS multiplier".
Suggestion: remove it from future builds.

Re: Firmware developent status

Posted: Sat Feb 18, 2017 2:46 am
by AndreyB
You mean you can set the curve to multiple to zero? You are the 1% who would think of it :)

Re: Firmware developent status

Posted: Sat Feb 18, 2017 11:58 pm
by AndreyB
rusEfi console program/erase buttons are working again.

Re: Firmware developent status

Posted: Sun Feb 19, 2017 12:49 am
by AndreyB
Actually, change log button added to the forum header, I will try to better document important changes, let's see how this goes.

Same file is displayed at https://github.com/rusefi/rusefi nicely but with a one hour delay.

Re: Firmware developent status

Posted: Tue Feb 21, 2017 12:29 am
by AndreyB
I am tired of SF instability - being unable to commit for more than 24 hours at a time is just deal breaker for me.

As of today https://github.com/rusefi/rusefi is the official repository

Re: Firmware developent status

Posted: Tue Feb 21, 2017 1:59 am
by stefanst
The FW is getting pretty darn close to being fully functional for most Miatas as near as I can tell.

Just had it set up with the Jimstim on the bench and it was running for 24 hours straight without any apparent hickups.

Most important punch-list item from my side is idle control. Autotune of VE cells would be nice, but since this possibility is provided by Tunerstudio, it's not really needed.

Some options for soft revv-limit would also be a nice-to-have.

And there are still a few incongruities left in the accel-enrichment tuning arena.

Re: Firmware developent status

Posted: Tue Feb 21, 2017 2:29 am
by stefanst
Real-Time-Clock implementation for proper time stamps on SD-card logs would be nice too.

Re: Firmware developent status

Posted: Tue Feb 21, 2017 2:32 am
by AndreyB
stefanst wrote:Real-Time-Clock implementation for proper time stamps on SD-card logs would be nice too.
I have news for you: http://rusefi.com/forum/viewtopic.php?f=4&t=460
Our brain boards http://rusefi.com/forum/viewtopic.php?f=4&t=381 would have this, there is a chance brain boards would be for sale in March.

Re: Firmware developent status

Posted: Tue Feb 21, 2017 2:35 am
by stefanst
russian wrote:Our brain boards http://rusefi.com/forum/viewtopic.php?f=4&t=381 would have this, there is a chance brain boards would be for sale in March.
I shall order some forthwith!