PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : [sparks7162] Problem with vfd in some Amiko Alien2



miciomax
14.03.2014, 16:27
Hi all.

@Bonkel @Santa
In some of the last new Amiko Alien2 produced, we have an issue in every enigma2 image: VFD always display time and "boot", but all tv and dec function works properly.
We asked oSaiYa and seems that commit of Oct 28 2013 of oSaiYa (7eca3d1 [spark7162] add dvfd panle support) has not been implemented in any enigma2 image.

Can we have an HDMU image for sparks7162 with that for test?

arci
15.03.2014, 13:55
Always the same inappropriate rudeness of not responding ... without anyway make a sign !

Although ... we have no problems with the receivers of previous hardware revision ... we are not selfish ... we don't think only of us!

Thanks to others friend, we've made ​​available the new modules aotom.ko (for k211 & k212) ... for those who will need to them !

Thanks anyway and I see with regret .. that your attitude never changes!

Saluti ...

santa
15.03.2014, 14:08
sorry, we try first to push 212 to all of our boxes, then we can test other things.
iīm reading this with tapatalk, so i couldnīt look inside.


can you compare in max-git enigma2 branch, normaly we merge with master tdt, so it must be inside our git.

arci
15.03.2014, 14:26
on max-tdt ... the oSaiya commit is not present !


https://gitorious.org/open-duckbox-project-sh4/tdt/commit/7eca3d17f5cfc9ab236e2008e29016d665b90cc3

https://gitorious.org/open-duckbox-project-sh4/max-tdt/source/de40ec20e2e55dc88b1741890cf2c8dbf9d38194:tdt/cvs/driver/frontcontroller


Probably in the changes of cloning git ... have you lost something?

Ciao ...

santa
15.03.2014, 23:03
TheChip pushed it to max-git, image will be later on our server

if we forget anything, please post it with link to change again.

arci
16.03.2014, 01:34
Thanks ... We are with you ... because the result deserves attention!

Ciao ...

jrodzar
24.03.2014, 11:31
Still not working

kukuia2k
28.03.2014, 20:07
here too...

santa
05.04.2014, 23:12
try image 12421, you will find it on server in max 2hours.
I hope i have found all changes

jrodzar
06.04.2014, 20:47
Thank you very much!! VFD is working ok now!

miciomax
27.06.2014, 01:12
try image 12421, you will find it on server in max 2hours.
I hope i have found all changes

Hi.. I resume this thread because some of our friends with new vfd, say that from last HDMU_12378_E2_spark7162_215_git_2911
vfd has started again not working. Again it displays time and "boot", but all other function works well.
It seems that HDMUcode is gone back in time.
Can you take a look at this? Thks

radog
30.06.2014, 22:37
Hi.. I resume this thread because some of our friends with new vfd, say that from last HDMU_12378_E2_spark7162_215_git_2911
vfd has started again not working. Again it displays time and "boot", but all other function works well.
It seems that HDMUcode is gone back in time.
Can you take a look at this? Thks

The same for me. Has this been fixed with later image? Or should I wait?

itsmearron
02.12.2014, 22:06
Hi thanjs for this great HDMU image works a treat. The only problem i have is the vfd driver / display. Is there a way of fixing this without flashing a fresh image. I want to keep all of my settings.

- - - Updated - - -

Hi thanks for this great HDMU image works a treat. The only problem i have is the vfd driver / display. Is there a way of fixing this without flashing a fresh image. I want to keep all of my settings.

ReWard
02.12.2014, 22:25
This is very old.

Take a look at this. ->1. (http://www.hdmedia-universe.com/board/showthread.php?7979-HDMU-Image-13155-Uhrzeit-im-Display-stimmt-nicht) follow the link to -> 2. (http://www.hdmedia-universe.com/board/showthread.php?906-Uhrzeit-einstellen&p=91070&viewfull=1#post91070)

To keep the settings take a look at Morly's Admin Tool, you here in the Computer section.

itsmearron
03.12.2014, 21:08
hi ReWard i have read through the 2 links but i think that is a very different problem to mine, that is for changing the times on the display my display just shows the word boot.

i have tried to load the morlys admin tool but it keeps giving a libcc_ error and wont load.

ReWard
03.12.2014, 21:49
Perhaps you Image is to old, which version do you have?

@Tool, please open a new Threat in the Admin Tool area, write Tool Version, Win, Mac or Linux, and alittle more information as above.

You can also read in the FAQ about the Admin Tool, but it is so far not yet in English. :(

itsmearron
03.12.2014, 22:21
System kernal 2.6.32.61 stm24 0215
HDMU rev . 13068
GIT REV . 3285

KleinerSchelm
03.12.2014, 23:11
not the new image we have.
now is new > HDMU_13203_E2_spark7162_215_git_3354

itsmearron
03.12.2014, 23:21
Can i update via the online update or will that fail?

miciomax
04.12.2014, 01:13
On HDMU13155 issue on vfd displaying time+"boot" on new spark's vfd was still not solved... See 1st post in this thread to find why

itsmearron
04.12.2014, 20:58
On HDMU13155 issue on vfd displaying time+"boot" on new spark's vfd was still not solved... See 1st post in this thread to find why

OK. ... I don't quite understand it say that it is not supported in and enigma 2 image? But with AopenTV image, the VFD works fine.?

miciomax
05.12.2014, 13:58
OK. ... I don't quite understand it say that it is not supported in and enigma 2 image? But with AopenTV image, the VFD works fine.?

My reply was not for your question, but for who replied to you that this is an old post. Yes. It's an old post for an issue not solved. And in 1st post they can find a way to try to solve it.

openATV work with new alien vfd. They spent 1 week to let it work.

Audioniek
05.12.2014, 15:34
Hello everybody,

everyone is talking about a "new" VFD in the Spark receivers, but nobody has revealed so far what is new about it, or how to identify the new VFD. I am willing to test/modify the aotom VFD driver if needed, but need a way to identify the "new" VFD version from the old one. If new pertains to the displaytype DVFD, the code for that has been in aotom for quite some time now. The two Spark 7162 receivers I have access to both have the VFD displaytype and work absolutely OK.

Regards,

Audioniek.

miciomax
05.12.2014, 17:18
Hello everybody,

everyone is talking about a "new" VFD in the Spark receivers, but nobody has revealed so far what is new about it, or how to identify the new VFD. I am willing to test/modify the aotom VFD driver if needed, but need a way to identify the "new" VFD version from the old one. If new pertains to the displaytype DVFD, the code for that has been in aotom for quite some time now. The two Spark 7162 receivers I have access to both have the VFD displaytype and work absolutely OK.

Regards,

Audioniek.


I don't know if this pic can help. Up new vfd, down old vfd.
I can say that one friend has compiled module aotom.ko with oSaiYa's commit in kernel 215 and sustituting it in HDMU13155 /lib/modules works fine in eachone vfd.

Thanks.


http://miciomax.altervista.org/vfd_aa2.jpg

zdzislaw22
05.12.2014, 17:22
@Audioniek:
It's super easy.
In GIT you have 2 versions of driver:
aotom - works with both
aotom_spark - works with "old" vfd only.

itsmearron
05.12.2014, 17:26
Hi i may sound silly but what is git?

miciomax
05.12.2014, 17:55
Hi i may sound silly but what is git?

git is where developer make the changes...
but now wait.. I think something can happen... and a new image can solve the question...

KleinerSchelm
05.12.2014, 18:10
You can use HDMU_13202_E2_spark7162_215 and test HDMU_13206_E2_spark7162_215_git_3355.

HDMU13155 is to old and have no new VFD driver.

13202 have new audioniek driver

13206 have aotom from Max git.

DboxOldie
05.12.2014, 18:35
Try to replace with this and please Report > the Dot VFD is integrated, but I canīt test it.

Audioniek
05.12.2014, 18:41
Thank you, miciomax!

This is exactly what I was looking for. The "new" VFD has dot matrix characters instead of 14 segment digits, so it is the DVFD displaytype. Will need another Spark 7162 receiver for testing now...

Regards,

Audioniek.

itsmearron
05.12.2014, 18:46
Hi i have the new dvfd display I will test when I get home after shoping ����

- - - Updated - - -

Where do I place this file??

DboxOldie
05.12.2014, 18:48
In Zip there is : aotom.ko
Put it in /lib/modules

Audioniek
05.12.2014, 18:55
13202 have new audioniek driver

13206 have aotom from Max git.

To avoid some possible confusion about the spinner:

The audioniek aotom uses icon 47 to control the spinner.
The max-git aotom uses led 2 to control the spinner. Martii has probably done this to get a spinner on recording without changing neutrino, as led 2 on a standard Spark is the red one.

Controlling the spinning speed is the same in both: fp_control -i 47 speed or fp_control -l 2 speed (-l is minus lower case L)

speed = 0 -> spinner off.
speed <>0 -> on, next spinner state in speed x 10ms (so 100 gives a change every second).

Regards,

Audioniek.

itsmearron
05.12.2014, 20:17
brilliant this works a treat, i now have the channel scroll / channel name on the display, i dont get any icons but at least i now get channel name not just the word boot.

miciomax
05.12.2014, 20:36
brilliant this works a treat, i now have the channel scroll / channel name on the display, i dont get any icons but at least i now get channel name not just the word boot.


What have you tried? 13206 only or 13206 + aotom in /lib/modules?

itsmearron
05.12.2014, 21:01
In Zip there is : aotom.ko
Put it in /lib/modules
I tried the aotom.Ko file kept the image that I was already using and copied the aotom.Ko file to lib/modules and the DVFD works.

DboxOldie
05.12.2014, 22:05
Ok > now we know > it works...
For Information > this aotom was an actually build from ddt-git.
Yesterday I testet with the HDMU build 13206 > and a few icons worked > REC, PLAY, DOULESCREEN, AC3 an the HDD-Level bar.
The rest....it is another part....if you try fp_control on telnet > you will see they works.

itsmearron
05.12.2014, 23:04
Hi DboxOldie I don't have any idea what fp_control on telnet means?

DboxOldie
05.12.2014, 23:46
Two possibilities:
Start Telnet console and type:
fp_control -i 1 1 for switch on the first icon -i 1 0 for switch off, Values from 1 to 46 are possible > 46 switches all icons.
or:
type : vfdctl and you will see in context help what is there possible, eg vfdctl +usb switches usb icon on -usb then to off > see the context help ( if the actually vfdctl is in the image )


PS: fp_control -l 2 1 / 0 activate / deactivate the vfd spinner

itsmearron
06.12.2014, 00:02
Ok i will try this tomorrow And get back.

itsmearron
06.12.2014, 12:43
hi i cant seem to enable any icons, i have tried as you said vfdctl +usb but this does not work for me.

fp_control -i 1 1 only gives
SPARK7162:~# fp_control -i 1 1
fp_control: SW Version 1.04
Model: spark7162
vBoxType: 11
Selected Model: Edision Spark frontpanel control utility
Spark_init
checkConfig
configs: DISPLAY = 1, DISPLAYCUSTOM = 1, CUSTOM = %H:%M:%S
, WAKEUPDECREMENT 300
seticon: : Timer expired

DboxOldie
06.12.2014, 13:55
Well...
First make sure if the right vfdctl is working by typing only vfdctl in Telnet window:

SPARK7162:~# vfdctl
vfdctl v0.7.1 Spark7162 - usage:
vfdctl [[-c] text] [+sym] [-sym] ...
-c centered output
to set symbols use e.g. +usb or -usb
available symbols are fr,plr,play,plf,ff,pause,rec,mute,cycle,dd,lock,ci ,usb,hd,rec2,hd8,hd7,hd6,hd5,hd4,hd3,hdfull,hd2,hd 1
,mp3,ac3,tvl,music,alert,hdd,clockpm,clockam,clock ,mail,bt,stby,ter,disk3,disk2,disk1,disk0,sat,ts,d ot1,cab,all


But the fp_control command should work.....

I'll take a look in the driver if there's any dependency with recognizing the DotVFD and the icon steering.
Other question : with the original aotom.ko the icons work ?

itsmearron
06.12.2014, 15:47
Well...
First make sure if the right vfdctl is working by typing only vfdctl in Telnet window:

SPARK7162:~# vfdctl
vfdctl v0.7.1 Spark7162 - usage:
vfdctl [[-c] text] [+sym] [-sym] ...
-c centered output
to set symbols use e.g. +usb or -usb
available symbols are fr,plr,play,plf,ff,pause,rec,mute,cycle,dd,lock,ci ,usb,hd,rec2,hd8,hd7,hd6,hd5,hd4,hd3,hdfull,hd2,hd 1
,mp3,ac3,tvl,music,alert,hdd,clockpm,clockam,clock ,mail,bt,stby,ter,disk3,disk2,disk1,disk0,sat,ts,d ot1,cab,all


But the fp_control command should work.....

I'll take a look in the driver if there's any dependency with recognizing the DotVFD and the icon steering.
Other question : with the original aotom.ko the icons work ?

hi no the icons dont work with the original aotom.ko or the new one.

DboxOldie
06.12.2014, 16:20
Mhh...
No try this binary > put it in /bin and make rights to 755 executable.
Then type in Telnet : spark_fp -T which tells the type of your display

8892

Also try:
fp_control -l 0 1 <switches red led on
fp_control -l 1 1 <switches green led on ( at 7162 it is the RC recognition dot in vfd )
and:
fp_control -i 46 1 < and tell me what happens

miciomax
09.12.2014, 01:52
You can use HDMU_13202_E2_spark7162_215 and test HDMU_13206_E2_spark7162_215_git_3355.

HDMU13155 is to old and have no new VFD driver.

13202 have new audioniek driver

13206 have aotom from Max git.

However, to make an actualized point in this thread:

No HDMUimage can do the "new" spark's vfd to work (13206 git 3366 too);
HDMUimage 13155 (or 13206) + DboxOldie's aotom.ko let the new spark's vfd to work.

miciomax
10.12.2014, 11:27
How do you think about a plugin from your feed containing DboxOldie's aotom.ko, to be installed by AA2 owners only on demand?

KleinerSchelm
10.12.2014, 23:21
i dont know what DBO have do with his aotom.ko. This is ja finisches buildet .ko

itsmearron
10.12.2014, 23:30
Hi guys working away not had chance to test yet sorry.

DboxOldie
10.12.2014, 23:33
If you are talking about the posted aotom.ko in #29 > it is just an actually build from DDT-Git

KleinerSchelm
11.12.2014, 19:24
Please Test the new spark7162 image

miciomax
11.12.2014, 20:24
Great... It works... Fine, thanks to all...

Antonio Rossi
20.02.2015, 12:01
Hi guys!!!My question to you.I installed HDMU's latest version...(3451)Appears on the display again after a long time "BOOT"Why?
This problem was gone ...THX in advance!!!:o

Antonio Rossi
20.02.2015, 15:56
No one has this problem?A minimum of collaboration wouldn't hurt ...

KleinerSchelm
20.02.2015, 16:05
hello,
older image is working with youre display ? wich receiver 7162 you have ?

in last image we have chance aotom driver to audioniek

Antonio Rossi
20.02.2015, 16:24
Hi!!!Many thx for your reply!!!Ihave Amiko Alien2 Triple+box...To get rid BOOT on vfd,i had to overwrite atom's file...Wasn't fixed the problem?

KleinerSchelm
20.02.2015, 18:53
i dont understand youre problem.

the receiver works but the display dosnīt work ?
or it dosnt boot , not working software ?

is the older revision of the soft working with the display ?

Antonio Rossi
20.02.2015, 20:37
The box works fine.On display also shows the word boot!!!The writing boot is always present!!!Old problem ... In December, had disappeared.Many thanks,man.

KleinerSchelm
21.02.2015, 00:21
Ok thx for response

can you teel me wich box you haven ? brand name and is it 2 or 3 tuner ?

thx

Antonio Rossi
21.02.2015, 00:49
Hi!!!My box is Amiko Alien2 triple +.Thank you very much indeed.[emoji6]

KleinerSchelm
21.02.2015, 00:59
it build new software for spark7162, please test

Audioniek
21.02.2015, 12:37
As far as I know, at least 3 different versions of the Spark7162 exist:
1. DVB/T tuner, 14 segment VFD display (back USB is horizontal)
2. DVB/T2 tuner, 14 segment VFD display (back USB is vertical)
3. DVB/T2 tuner, dot matrix VFD display (back USB probably vertical)

In addition these receivers are also built/sold without a DVB/T(2) tuner, and/or with/without modem and/or with/without RF modulator.

The aotom display driver in my git has been tested with variants 1. and 2. but not with 3. as I do not have access to such a receiver. Although I have carefully taken over Osaiya's changes for the DVFD display , apparently the driver in my git gives problems with dot matrix VFD displays. I am of course willing to fix this, but I do not have a dot matrix VFD receiver. If somebody can help getting me one (I will pay the normal price for it) it would be appreciated.

As far as I can determine, the current situation is as follows:
Audioniek driver: VFD OK, DVFD displays BOOT and nothing else;
Other driver: VFD not OK, DVFD OK but does not update front panel clock properly.

Regards,

Audioniek.

KleinerSchelm
21.02.2015, 13:32
Software HDMU_13497_E2_spark7162_215_git_3460 has now MaxWiesel-Git Aotom from martii

please test

Antonio Rossi
21.02.2015, 14:59
Many,many THX for your support!!!Unfortunately I will not be able to test , because the weekend i will be away from home ...I see if I can tomorrow to test . THX ,again guys!!!Great team[emoji4]

Antonio Rossi
22.02.2015, 11:28
Many THX Audioniek!!!The problem disappeared !!!IMany THX Kleiner!!![emoji6] [emoji4] Good job,guys!!![emoji3]

Qsilver84
25.02.2015, 00:02
Hi,

In 13497, the vfd clock has a diferrent hour (exactly one hour more) than in menu osd, how can i solve?

Thanks

miciomax
25.02.2015, 00:44
Upgrade it...

KleinerSchelm
25.02.2015, 02:34
hello
flash new image

ibero96
25.02.2015, 08:33
Hi,

In 13497, the vfd clock has a diferrent hour (exactly one hour more) than in menu osd, how can i solve?

Thanks

Being exactly 1 hour out all the time sounds a bit weird - almost as though the VFD clock is set to different TZ.....


Try upgrading to latest image by all means but HDMU has had a problem with the time display being randomly out on the VFD for quite a while - try running

/usr/sbin/time.sh

and see if that corrects the time. If not there's something else happening here which doesn't affect my 13497 image (GM Triplex).

Andy

Antonio Rossi
26.02.2015, 12:32
Many THX for your reply!!!

KleinerSchelm
26.02.2015, 20:59
hello
we have changed from time.sh to aotomtd (aotom time daemon) to set VFD Time.

ibero96
27.02.2015, 08:35
hello
we have changed from time.sh to aotomtd (aotom time daemon) to set VFD Time.


Maybe but to reset the VFD time after it goes crazy running /usr/sbin/time.sh is quick and easy.

The problem with the VFD displaying a random time has existed in HDMU for a while now - it's not serious since the system time is still accurate but it is irritating.

Andy

KleinerSchelm
27.02.2015, 09:03
hello
the aotomtd set every minute the time in VFD Panel.

ibero96
27.02.2015, 11:12
hello
the aotomtd set every minute the time in VFD Panel.

Well in 13490 it sets it to the wrong time every so often so it's not working is it?

I'll install the latest image sometime today and see if things have changed but this 'feature' with the wrong time being displayed on the VFD has existed for quite a few versions now.....

The system time is always accurate it's only the VFD time that is wrong - and as I said above the easy way to correct it is;

/usr/sbin/time.sh >/dev/null 2>&1 &

job done until the next time.....


Andy

DboxOldie
27.02.2015, 12:54
I'm astonished....
The aotomtd makes exactly the same thing as time.sh, with the difference :
aotomtd is a binary daemon which sets the system time periodicly ( here every 60 seconds as its call per rcS ) to frontprocessor, while time.sh is a script and sets system only for 3 times and then it close itself.
Try to type in Telnet: ps and have a look in the process list if "aotomtd" is listed.
Also type: date > this will show the actual Linux systen time.
Typing simply : aotomtd > then VFD time will be set once, and all aotomtd processes will be finished.
Typing : aotomtd 30 ( for example ) > then aotomtd runs as a daemon and set VFD time from system every 30 seconds.

ibero96
28.02.2015, 08:42
I'm astonished....

Well it's not part of 13490 - no trace of aotomtd anywhere in that release......

OK, quick search finds the binary in another thread. Installed and hopefully now working. Do I assume that this is included in later releases or is it still an optional add on -?

As before even when the VFD time was incorrect the system time is accurate so no effect on timers etc - it' just annoying when the VFD tells you it's 02:30 at 10:00!.

Anyway - many thanks for the help in sorting this annoyance

Andy

KleinerSchelm
28.02.2015, 08:46
In 13490 is time.sh
use newer image

ibero96
01.03.2015, 08:58
In 13490 is time.sh
use newer image

Thanks -installed 13573 and yep, the time problem seems to be fixed with aotomtd running.

Great work - that's one annoyance gone for good we hope!

Andy