Всякие глупые вопросы, терзающие меня

Это оффтопик или флудилка или курилка
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

зондирую вопрос: нужно тут выводить напряжение от 0,5 до 4,5В в определенной зависимости от MAP датчика. насколько сложно мне будет такую хотелку добавить в код? и как это в железе лучше сделать: pwm с фильтром или цифровой потенциометр типа такого?
http://www.farnell.com/datasheets/1928908.pdf
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

да, упустил про pwm
что вкл-выкл в flexible logic можно - знал.
но как и у 960, не уверен, что зависимость будет прямая - возможно, потребуется какая-то табличка.
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

Таблички там тоже то ли есть, то ли очень близки и надо просто доделать или додокументировать.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

к прошлогодним вопросам:
подключил смартфон на вход платы lm1815 (VR)
осциллографом вижу на выходе пятивольтовый сигнал (то есть на входе в дискавери)
а в файле msi в логах rpm нулевой.
прошивка прошлогодняя.
попробую сейчас свежачок залить и еще раз проверить.
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

зацените лог с сегодняшнего запуска (стоит только датчик колена)
как-то странно выглядит?
Attachments
MAIN_rfi_report_2019-06-22_19_05_33.csv
(4.56 MiB) Downloaded 623 times
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

почему вот тут оно не показывает обороты?
Attachments
Снимок экрана 2019-06-24 в 21.20.51.png
Снимок экрана 2019-06-24 в 21.20.51.png (90.57 KiB) Viewed 31722 times
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

Ага, про N/C я сам запутался :) Раз запутался, то сделал чтоб теперь там было слово LOG в режиме просмотра логов.

Почему оно не синхронизирует по фотография понять непросто. Нужно смотреть в динамике в message при включённом подробном логгировании синхронизации. Я только что добавил новую галочку "Verbose trigger Sync" вниз Engine Sniffer, но такая галочка была давно в TS и можно того же эффекта добиться командой enable trigger_details
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

хм. решил подключить уже датчик температуры, тюнерстудию для этого пробую подключить (новый проект, указываю ini файл, что шел в комплекте) - а тюнерстудия не хочет к порту подключаться.
консоль подключается, а тюнер-студия - нет. (test port - failed)
snapshot_20190616_2308_stm32f407_rusefi
TunerStudio MS (2.9)
через консоль тоже можно попробовать датчик температуры настроить?
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

вот свежий лог, с галочкой.
не очень понятен момент с < 1/7 >
это семь страниц? за последний момент? или с момента старта?
Attachments
MAIN_rfi_report_2019-06-25_16_16_27.csv
(4.6 MiB) Downloaded 625 times
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

вот еще один лог - оплетку кабеля ДПКВ зацепил за землю у корпуса (на датчике ДПКВ экран в воздухе вроде)
что не хватает для синхронизации?
Attachments
MAIN_rfi_report_2019-06-25_17_17_37.csv
(6 MiB) Downloaded 578 times
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

словил такое:
Снимок экрана 2019-06-25 в 17.28.16.png
Снимок экрана 2019-06-25 в 17.28.16.png (60.59 KiB) Viewed 31692 times
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

а при ресете плате вот такое некрасивое:
Attachments
Снимок экрана 2019-06-25 в 17.30.19.png
Снимок экрана 2019-06-25 в 17.30.19.png (60.1 KiB) Viewed 31692 times
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

упс. не заметил, что в messages надо смотреть.
вот (хз как спрятать под кат):
019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.01 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.03 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.02 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.01 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.98 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.98 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.52 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.98 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: error: synchronizationPoint @ index 1399 expected 70/0/0 got 1400/0/0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.08 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.52 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.98 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.69 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.08 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.52 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.69 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.08 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.52 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.69 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.08 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.69 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.01 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.02 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.06 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.02 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.06 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 14.11 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.05 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.07 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 14.11 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.01 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.07 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 14.11 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 0.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.04 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 1.07 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 2147483647.47 expected from 14.11 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 0.06 to 1.50 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.04 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 210 0: cur 0.00 expected from 1.07 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 16.19 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.04 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.18 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 16.19 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.04 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.14 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 16.19 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.10 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.14 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 16.19 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.03 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.10 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.14 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.98 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.10 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.14 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.98 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.10 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.06 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.98 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.18 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 1.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.98 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.03 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 51.18 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.06 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.01 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 51.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 67.62 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 51.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.03 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.01 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 67.62 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 51.18 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 101.68 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 67.62 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.00 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 101.68 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 0.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 2147483647.47 expected from 67.62 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 126.69 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 101.68 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.01 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.00 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 126.69 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 101.68 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.00 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 126.69 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.99 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 126.69 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.00 to 1.50 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.99 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 1.00 to 0.00 error=0
2019-06-25 17_33: EngineState: 211 0: cur 0.00 expected from 0.00 to 0.00 error=0
2019-06-25 17_33: EngineState: engine has STOPPED
2019-06-25 17_33: EngineState: templog engine has STOPPED [8][5C7B3312] [8][443E5AFD] 406640661
2019-06-25 17_33: EngineState: Template Rvrv8 (10) trigger TT_TOOTHED_WHEEL_36_1 (9) useRiseEdge=Yes onlyFront=No useOnlyFirstChannel=No tdcOffset=0.00
2019-06-25 17_33: EngineState: trigger#1 event counters up=10754/down=10695
2019-06-25 17_33: EngineState: expected cycle events 70/0/0
2019-06-25 17_33: EngineState: trigger type=9/need2ndChannel=No
2019-06-25 17_33: EngineState: expected duty #0=0.48/#1=0.00
2019-06-25 17_33: EngineState: synchronizationNeeded=Yes/isError=Yes/total errors=24 ord_err=60/total revolutions=25/self=No
2019-06-25 17_33: EngineState: gap from 1.50 to 2.50
2019-06-25 17_33: EngineState: primary trigger input: PC6
2019-06-25 17_33: EngineState: primary trigger simulator: PD1 OM_DEFAULT freq=1200
2019-06-25 17_33: EngineState: trigger error extra LED: ext:(null).-1 OM_DEFAULT
2019-06-25 17_33: EngineState: primary logic input: ext:(null).-1
2019-06-25 17_33: EngineState: secondary logic input: ext:(null).-1
2019-06-25 17_33: EngineState: zeroTestTime=16 maxSchedulingPrecisionLoss=442234
2019-06-25 17_33: EngineState: advanceLookupTime=509 now=1551839308 fuelCalcTime=11662
2019-06-25 17_33: EngineState: ignitionSchTime=7703 injectonSchTime=0
2019-06-25 17_33: EngineState: mapTime=28547/hipTime=0/rpmTime=241/mainTriggerCallbackTime=12962
2019-06-25 17_33: EngineState: maxEventCallbackDuration=13866
2019-06-25 17_33: EngineState: hipLastExecutionCount=0
2019-06-25 17_33: EngineState: hwSetTimerDuration=460
2019-06-25 17_33: EngineState: totalTriggerHandlerMaxTime=188836
2019-06-25 17_33: EngineState: maxPrecisionCallbackDuration=184047
2019-06-25 17_34: SerialManager: Restarting serial IO
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

puff wrote:
Tue Jun 25, 2019 2:30 pm
а при ресете плате вот такое некрасивое:
Вот это починил - https://github.com/rusefi/rusefi/commit/6b1edd9e299806d34faec9198cf52d4e4d489107

Остальное пока не успеваю ответить, но я очень постараюсь ответить сегодня-завтра.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

puff wrote:
Tue Jun 25, 2019 2:29 pm
словил такое:
Снимок экрана 2019-06-25 в 17.28.16.png
"Доктор, где вы берете такие картинки?.."

Эту странную ошибку буду теперь обрабатывать без fatal, но вообще природа явления мне пока не понятна :( https://github.com/rusefi/rusefi/commit/50bf018fe998174fa2c8190ccb6b934745d73195
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

в общем, проблемы две:
1. осциллографом вижу иногда помехи, частота которых на два порядка выше (и по амплитуде тоже меньшие), чем нормальный сигнал. причем не единичный сигнал, а всплески с последующим затуханием. по идее это железная проблема, какова ее природа - не ясно.
как с ней бороться - тоже не ясно. пока освежаю в памяти - может там lm1815 умеет бороться с такой фигней.
2. когда помех нет в снифере - когда по три-четыре раза видна стабильная картинка по зубьям - почему-то про обороты пишется na - то есть обороты считаются не после каждого цикла?
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

И третье улучшение - прошивка будет явно писать про шум, и консоль будет писать более точные отметки времени

https://github.com/rusefi/rusefi/commit/23fe25268ae6b13f54aee37b329e995a9e5efbbd

Но все эти улучшения это лишь более красивая обработка твоей очень необычно шумной ситуации, как мне кажется.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

feature request: насколько сложно сделать штуку, которая бы позволяла по имени пина (pd6, pa0, pc1 и т.д.) выводить его текущую привязку к той или иной функции? чтобы понимать, занят ли этот пин, и чем именно он занят - такую бы приблуду заиметь либо в тюнерстудии, либо в консоли.
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

Это команда консоли pins?

Вопрос, что эти команды очень плохо задокументированны :(
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

то есть можно в консоли написать pins pa0 и оно скажет либо функцию в текущей прошивке, либо скажет, что пин pa0 не используется?
надо будет попробовать!
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

не совсем так. В консоли надо написать просто pins и будет список, отсортированный по пинам.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

а.. ну хоть отсортированный - уже хорошо.
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

а вот еще глупый вопрос: при триггере на плате дискавери светодиод должен возникать при любых импульсах, или только когда распознает нужный диск?
вместо lm1815 воткнул чип max. но сигнал вообще видеть не смог :-( никакой.
думаю попробовать со смартфона подать синусоиду.
может там для этих двух нужно по-разному конфигурировать входы?
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

На дискавери кажется нет лаипочек напрямую завязанных на триггер. Это хорошая режима сделать такой режим. Но сейчас такого нет.

Команда triggerinfo покажет счётчик. Я занииаюсь добавлением в formulas информации о триггере, но пока не готово
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

в смысле мигает только при синхронизации?
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

образовалося свободный вечер, и сложилось, что под рукой БП и электронный дроссель от ситроена.
который на пружине. интересно, его можно подцепить на один из ключей форсуночных на франкенштейне, а потенциометр - на свободный АЦП канал?
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Всякие глупые вопросы, терзающие меня

Post by AndreyB »

Дроссель можно вероятно открывать просто форсуночным транзистором и закрывать пружиной - первая версия rusEfi управления работала только в одну сторону. Сейчас прошивка рассчитанна всё-таки на два канала, но прошивку можно обмануть наверное.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

та же фигня с оборотами на чипе max
а что означает set_int 944 1?
(оно у меня как будто за мкеня введено - остается только нажать go)
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Всякие глупые вопросы, терзающие меня

Post by puff »

вот еще пара видосов со свежей прошивкой

теперь вообще фигня какая-то - не видно зубьев..
прошивалось следующей командой:

Code: Select all

MacBook-Pro-red:snapshot_20190704_040308_stm32f407_rusefi red$ dfu-util -a 0 -D rusefi_no_asserts.dfu -R
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Match vendor ID from file: 0483
Match product ID from file: df11
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash  "
file contains 1 DFU images
parsing DFU image 1
image for alternate setting 0, (1 elements, total size = 302336)
parsing element 1, address = 0x08000000, size = 302328
Download	[=========================] 100%       302328 bytes
Download done.
done parsing DfuSe file
dfu-util: can't detach
Resetting USB to switch back to runtime mode
вот еще одно видео
Post Reply