#apertus IRC Channel Logs

morning folks!

se6ast1an: added first part of screen description to the README, also started to separate descriptions in "general" and "buttons", as we need to take care of it very soon, not really happy with switch/case, as it produces too much code ans is error-prone

hey panintended, how is it going?

hi

It's going alright, yourself? I played a bit with having a button inside the knob last night

and, has it workeD?

FYI: I have a work meeting that could overrun. I might not make it for tonight's weekly sync, or at least not in time

it sort of worked

but will return around 8:30pm if streets are not that crowded with cars

So initally I tried tricking it into believing that Button 5 was pressed when pressing this "temporary" button

have you committed to your fork? if yes, then i can check it

one of them will be cut away, as only one knob was left in newer versions of the hardware

<BAndiT1983> se6ast1an: what is the latest state there? <- state of what exactly?

https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Firmware/UI/Screens/SettingsMenu.h#L290

ah, button 5 is the same at the moment -> https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/45349601b42de35ee4c215ca98403fd4d8f442ab/Firmware/UI/Screens/SettingsMenu.h#L283

at least in this dialog, when debug painter is fixed and widgets for menu created, then i would start to rework button handling, as switch/case is rather error-prone

se6ast1an: can you do me a favor the next time you flash your remote? could you please run following command: pic32prog -D -D -D AXIOM_Remote_Firmware.hex

sure

thanks in advance

i know, but need a comparison to see if my flash attempt is almost through or not

no, USB hub is not interfering with the pickit, ass i have same behavior when it is directly connected to my laptop

good idea, will grab your lcd test

nope, still the same -> mz: timed out at finish, status = 040a

BAndiT1983: can you upload hex file?

lcd.hex

perfect, thanks

https://pastebin.com/M352Eb6C

thats stderr, do you need stdout as well?

ah, indeed it's also helpful, by the way, am using such a command for output of both -> reset && pic32prog -D -D -D lcd.hex 2>&1 | tee lcd_flash_output.txt

hm, interesting, one of things which looks suspicious is the difference in sending 00 on my side and FF on yours

note, se6ast1an has a pickit2 clone IIRC

so quite different hardware

just saying that it might not compare 1:1

also double check your permissions on the device

you could source a pickit2 and avoid the journey?

as IPE was working properly there is something off with pic32prog, and i would like to avoid to have more devices laying around which is only use for very specific tasks, it would be even easier for me to write the self-flashing bootloader

MEETING TIME!

please pm me now to get put in reporting order!

BAndiT1983: would you do us the honor of starting the reporting phase please

alright, jsut a quick update from the remote side

next steps involve improvements for the visualiser, like knob button and also additional events like "button up" to be closer to the real board behavior

additionally we will check how to make button processing simpler, as switch/case grows exponentially and is not the goal i would see for the future, but function pointers

that would be great, but not sure if metal_dent[m], is present?

he has the conference call still if I am not mistaken...

the lab workboard has been restructured: https://lab.apertus.org/project/view/18/

so everything feels a bit tidier now

looks great, to be honest haven't looked at it for a couple of days

quite a number of git commits, also documentation in the repo directly

anything else from you BAndiT1983?

great

Bertl: any news from your side?

the last week was mostly spent on GSoC preparations on the hardware and software side as well as evaluating the applicants

http://vserver.13thfloor.at/Stuff/AXIOM/REMOTE/remote_shield_small.jpg

and here we have the bottom side of the new remove v0.14:

as well as the rather unspectacular top side (so far): http://vserver.13thfloor.at/Stuff/AXIOM/REMOTE/remote_v0.14_top.jpg

still 2 knob footprints?

Bertl, you offline as well?

great metal_dent[m] ad happy birthday!

se6ast1an: thank you so much!!

last week I did some coding to add the button functionality for the sidebars but BAndiT1983 suggested some changes which I'm working on right now and hopefully will be done in the next few days..

and also I'm reading up about the tasks and hardware related to my gsoc project :)

hm, big netsplit, will restart quickly in the meantime, my usb bus has crashed and not recognizing anymore

metal_dent[m]: great, anything else?

se6ast1an: no, that's it from me :)

everyone who got split away, see logs: http://irc.apertus.org/index.php?day=27&month=04&year=2020

on the Ultra-96 front we are also still waiting on some parts for testing

so we already started testing on a normal PC to establish a baseline

but I dug out all the required bits and pieces to redo the SD card tests on the Axiom Beta

the applicants gave another presentation, this time about JTAG, which was quite informative I'd say

what about the powerboard V1 testing progress?

no change there, as no PCB was selected (pcb probe dependency)

*manually test

ok

vup & anuejn_ any news from your side?

through our PCB contact I got access to another PCB manufacturer or actually to one we had contact with already

I tried to install wechat which is the prefered communication method for chinese companies but after almost a week of trying to register an account gave up

and the qr code needs to be scanned within 5 minutes of registration otherwise it times out

so lots of fun :)

anyone else with any topics?

otherrwise: meeting concluded, thanks everyone!

Currently not home, can give some updates later

yesterday I looked at https://lab.apertus.org/T1184. I did some rough hack to get a button working next to the knob, but it's not in a state that can be merged. I'll revise it.

thanks for the update

please create a PR when we should check it out