Origenae s10v with vf310 issue

[spirosgr1979]

I have an origenae s10v caseand I bought vf310.the system has windows 7 ultimate.the problem is that it takes commands without given eny.the most common is keyboard arrow up command given by it's self.enything I tryied to fix the problem did not work!I tryed older version of imon and the very new but nothing! Any help is aprisiated.

[The_Iceman]

I have an origenae s10v caseand I bought vf310.the system has windows 7 ultimate.the problem is that it takes commands without given eny.the most common is keyboard arrow up command given by it's self.enything I tryied to fix the problem did not work!I tryed older version of imon and the very new but nothing! Any help is aprisiated.

I've exactly the same problem with my VF310 inside OrigenAE M10!!

Help would really be appreciated because the key which is sometimes "magically" pressed is "8" ... Thats annoying while watching Blu-Rays the chapter is jumping to Nr. 8!

Sometimes the "magical" pressed key is ALSO the power button... and this really ....

Whatever... I hope someone can help!

Best Regards
The_Iceman

[E-4]

Hi,

I have the same problems as described above. My OrigenAE S14V case came with a VF310 module build in and the Philips RC197 remote. The VF310 frequently misinterprets commands sent by the remote. When using notepad you can clearly see it happening. I alternated between keeping the key down and repeatedly pressing and releasing it:

- Pressing a number on the remote (like 1 or 2) will result in a row with a lot of the number you pressed and other random numbers in between. Sometimes a “left arrow” action is even mixed in causing the cursor to move one character back. Example; when pressing the “1” key on the remote repeatedly or keeping it down notepad shows: “1111111111111111111111211111111111011111111111115 11111”
- Pressing the volume up and down buttons repeatedly or keeping them pressed will eventually result in a stuck “8” character: it will keep repeating until you press another key on the remote like “enter”.
- Pressing the channel up and down buttons repeatedly or keeping them pressed will eventually result in a stuck “9” character: it will keep repeating until you press another key on the remote like “enter”.
- I’ve had the PC shutdown automatically while testing this in Media Center and in notepad. I think this only happens when pressing the “back” key repeatedly.
- Character repeating isn’t smooth which you can clearly see in notepad; use the remote and the characters will repeat fast – then stop – then repeat fast again. When entering the characters using the computer’s keyboard repetition is smooth (as it should be).
- Volume up and down isn’t smooth; when you keep the volume button on the remote down you can see the volume slider move – stop – move – stop. Also; when you repeatedly press volume down because you want to go from i.e. volume 95 to 90 the volume will suddenly drop a random number of steps on its own. The same goes for volume up.
- Any key press quickly followed by the “volume down” key will make that key repeat endlessly until another key is pressed. So if I press 1 and immediately after that press the “volume down” key then “1” is repeated endlessly. Works in notepad but in Media Center too; just press the “up” key for instance, release it and then immediately press “volume down” and watch the Media Center scroll through its menu endlessly.

So far I’ve tried the following to make the remote behave like it should:
- Changed the brand new batteries of the remote for even newer ones: no change.
- Changed the distance between the remote and the case (receiver): no change.
- Reinstalled the OS (Windows 7 RC build 7100) on my PC completely: no change.
- Changed the USB settings in the BIOS to every combination possible (USB 2.0 enabled-disabled, Legacy mode on-off-auto, USB speed full speed-hi speed) and ran the notepad test in between. Changing the USB settings didn’t make any difference.
- Added another USB card to my system with a completely different chipset than my on-board USB and connected the VF310 to that: no change.
- Connected the display to a another PC (with very different hardware), running Windows 7 Ultimate (retail version): problem remains the same.
- I used different versions of the iMon software: makes no difference. Even with the iMon software completely uninstalled (or never installed in the first place) the problem is there.
- Used my Logitech Harmony remote as a MCE remote: the problem remains.

In light of the above findings I don’t think my system specs (hardware or software) really matter but please let me know if you need them anyway.

It looks like this is a VF310 firmware issue rather than anything else. I cannot use the remote control to control my Media Center system this way; the VF310 makes too many mistakes for the remote to be usable.

Please put this on your high priority list and let me know if you want me to test anything. Until this is solved I cannot use my brand new Media Center PC – not for what it is intended for anyway.

Spirosgr1979 & The Iceman: can you possibly run the same tests I did and report if you get the same results? I think that would be valuable information for the Soundgraph team.

Kind regards,
Ivor.

[The_Iceman]

Hi,

I have the same problems as described above. My OrigenAE S14V case came with a VF310 module build in and the Philips RC197 remote. The VF310 frequently misinterprets commands sent by the remote. When using notepad you can clearly see it happening. I alternated between keeping the key down and repeatedly pressing and releasing it:

- Pressing a number on the remote (like 1 or 2) will result in a row with a lot of the number you pressed and other random numbers in between. Sometimes a “left arrow” action is even mixed in causing the cursor to move one character back. Example; when pressing the “1” key on the remote repeatedly or keeping it down notepad shows: “1111111111111111111111211111111111011111111111115 11111”
- Pressing the volume up and down buttons repeatedly or keeping them pressed will eventually result in a stuck “8” character: it will keep repeating until you press another key on the remote like “enter”.
- Pressing the channel up and down buttons repeatedly or keeping them pressed will eventually result in a stuck “9” character: it will keep repeating until you press another key on the remote like “enter”.
- I’ve had the PC shutdown automatically while testing this in Media Center and in notepad. I think this only happens when pressing the “back” key repeatedly.
- Character repeating isn’t smooth which you can clearly see in notepad; use the remote and the characters will repeat fast – then stop – then repeat fast again. When entering the characters using the computer’s keyboard repetition is smooth (as it should be).
- Volume up and down isn’t smooth; when you keep the volume button on the remote down you can see the volume slider move – stop – move – stop. Also; when you repeatedly press volume down because you want to go from i.e. volume 95 to 90 the volume will suddenly drop a random number of steps on its own. The same goes for volume up.
- Any key press quickly followed by the “volume down” key will make that key repeat endlessly until another key is pressed. So if I press 1 and immediately after that press the “volume down” key then “1” is repeated endlessly. Works in notepad but in Media Center too; just press the “up” key for instance, release it and then immediately press “volume down” and watch the Media Center scroll through its menu endlessly.

So far I’ve tried the following to make the remote behave like it should:
- Changed the brand new batteries of the remote for even newer ones: no change.
- Changed the distance between the remote and the case (receiver): no change.
- Reinstalled the OS (Windows 7 RC build 7100) on my PC completely: no change.
- Changed the USB settings in the BIOS to every combination possible (USB 2.0 enabled-disabled, Legacy mode on-off-auto, USB speed full speed-hi speed) and ran the notepad test in between. Changing the USB settings didn’t make any difference.
- Added another USB card to my system with a completely different chipset than my on-board USB and connected the VF310 to that: no change.
- Connected the display to a another PC (with very different hardware), running Windows 7 Ultimate (retail version): problem remains the same.
- I used different versions of the iMon software: makes no difference. Even with the iMon software completely uninstalled (or never installed in the first place) the problem is there.
- Used my Logitech Harmony remote as a MCE remote: the problem remains.

In light of the above findings I don’t think my system specs (hardware or software) really matter but please let me know if you need them anyway.

It looks like this is a VF310 firmware issue rather than anything else. I cannot use the remote control to control my Media Center system this way; the VF310 makes too many mistakes for the remote to be usable.

Please put this on your high priority list and let me know if you want me to test anything. Until this is solved I cannot use my brand new Media Center PC – not for what it is intended for anyway.

Spirosgr1979 & The Iceman: can you possibly run the same tests I did and report if you get the same results? I think that would be valuable information for the Soundgraph team.

Kind regards,
Ivor.

Tested the buttons you mentioned in your tests also...

You are right it is EXACTLY the same behaviour!!!!!!

It must have something to do with the firmware, because it can not be an Software Issue, because I've tested an alternative to IMON Manager (IRServerSuite) and it is exactly the same problem there...

PLEASE Fix this annoying issue...

Best Regards
The_Iceman

[E-4]

Thanks for that Iceman!

I wonder if this issue exists in all the VF310 modules. I cannot imagine this is the case as I had a hard time finding anyone with similar issues. That would mean that there are different versions of the VF310 module (with different firmware probably) out there. I've seen firmware updates for the VF210 module (on OrigenAE's website I think) so chances are that the VF310 modules' firmware can be user upgraded too.

Soundgraph: please respond and let us know what you are doing to help us out, we've paid good money for our OrigenAE cases (and thus for the VF310 module) and should get flawless performance.

The firmware version of my VF310 (according to the version/update tab of the iMON manager):
--------------
iMON Firmware ver 0x3602
VFD HID OEM
--------------

Thanks,
Ivor.

[athan]

Well guys, I have exactly the same issue using VF310 of my new Origen. The "phantom commands" problem makes me mad and I was going to return it, the second one actually, first got RMA'd because of this nasty issue.

@Soundgraph: As other folks said, it looks like either a serious firmware issue, or an RFI/EFI electrical interference problem of the IR sensor circuit due to some design fault. I'm monitoring forum for weeks but since this topic first appeared I haven't see anyone of your support team responding to user complaints; may I ask why this? I don't like to sound negative but you know directly or indirectly we paid for one of your products and it's not working correctly. I hope you understand that the least we deserve is some kind of support.

Anyway; do you plan to address this annoying issue anytime soon or at least help us fix it ourselves?

Thanks,
Athan

[The_Iceman]

I've had some response from the guys over at OrigenAE ...

Here's their answer for our Problem :

Dear Sir,

Sorry for inconvenience.

Could you please connect the 4pin USB cable of VF310 module to another USB
port of M/B?
We had had a similar problem and solved as mentioned above.
We have tested in same environment, I was working perfectly and we don’t
think so it is firmware problem.

Thanks & best regards,
Support team.
Origenae

Could someone please Test this ?
I don't think that this will solve our issue ...

Best Regards
The_Iceman

[E-4]

I wish they would read my post; I've already tried other USB connections on my mainbord, even added a separate USB card and also connected the VFD to a completely different computer: the problem stays exactly the same. I'm at work now but I will e-mail soundgraph tonight.

Ivor.

[athan]

OrigenAE knows nothing about computing electronics, they're good mechanics and that's all. Their advices are always based on the amateurish "try-and-error" methodology thus useless.
The problem is due to VF310 itself, probably a firmware or hardware fault. So let's concentrate on the actual cause and Soundgraph's suspicious silence.

[The_Iceman]

Ok after some testing of other USB Ports on my mainboard I've finally given up...

It has nothing to do with those ports...

So it must be something else (firmware?!) (hardware defekt)?

Best Regards
The_Iceman

[athan]

Could you please try something different?

Remove everything that emits RF (radio frequency) from inside your computer (e.g. WiFi card, Bluetooth, wireless mouse/kbd adapter etc.)
Also, move far from your computer or turn off any nearby RF source, such as WiFi routers, wireless phones, cell phones, wireless mice or kbd

Then try to reproduce this issue. During my experiments I've noticed a lot of improvement after doing that.

[spirosgr1979]

I found out that when I don't have enything connected to the front panel USB it works better.ghost commands stops.the only thing it does is that when I give command "next" the command keeps going.when I connect an external hhd it gets crazy.check it out.

[athan]

I found out that when I don't have enything connected to the front panel USB it works better.ghost commands stops.the only thing it does is that when I give command "next" the command keeps going.when I connect an external hhd it gets crazy.check it out.

In my case, panel connection is not the case because there is no front panel at'all. Theoretically, when external devices connected via front panel cause such problems is an indication of USB power voltage drop due to excessive consumption.
I did some further testing, powering vf310 from an external lab PSU. I've noticed some improvement though not significant. Ghost commands still interpreted by IR circuit. My next step is adding some RFI LC passive filtering to both vf310 power line and sensor input stage. I'll keep you informed of my findings.

PS: I'll ask once again; where is Soundgraph's support? Two pages of talking, a month old topic but no response. Thanks for nothing folks! :mad:

[The_Iceman]

The VFD is the only thing that is connected to my USB connector onboard...
I dont have a front panel connected...

For testing I disabled bluetooth and disconnected ALL USB devices from the rear USB Ports...
Ghost commands are still there.,, so I dont think this is a power consumption problem....

Even if this would be a power problem... Soundgraph OR OrigenAE has to deal with it, because they build this thing into the M10 case,,,

Best Regards
The_Iceman

[E-4]

Could you please try something different?

Remove everything that emits RF (radio frequency) from inside your computer (e.g. WiFi card, Bluetooth, wireless mouse/kbd adapter etc.)
Also, move far from your computer or turn off any nearby RF source, such as WiFi routers, wireless phones, cell phones, wireless mice or kbd

Then try to reproduce this issue. During my experiments I've noticed a lot of improvement after doing that.

I've got no Bluetooth, WiFi or any other RF enabled devices in my HTPC or any other PCs in the vacinity. I do have a WiFi router in the same room so I switched that off completely plus I switched off my mobile phone: the problem remains exactly the same (no improvement). Also; I've got other IR controlled equipment in the same room which never showed any problems, with or without the WiFi router switched on or mobile phones nearby.

I've posted a link to this threat in the "Me & Soundgraph" forum asking Soundgraph to respond. They claim they will do so within 2 working days.

It would be interesting to know which firmware version you guys have in your VF310. You can find this in the iMon manager under Option > Version / Update. Mine is version 0x360201 or 0x3602, depending on what the iMon manager feels like: it changes when I look again (how weird is that?) :confused:

Thanks,
Ivor.

[athan]

I've posted a link to this threat in the "Me & Soundgraph" forum asking Soundgraph to respond. They claim they will do so within 2 working days.

It would be interesting to know which firmware version you guys have in your VF310. You can find this in the iMon manager under Option > Version / Update. Mine is version 0x360201 or 0x3602, depending on what the iMon manager feels like: it changes when I look again (how weird is that?) :confused:

Thanks for trying, Ivor.
I hope Soundgraph people will respond this time, although I'm very disappointed with their non-existent support so far. Anyway, about the firmware version mine shows 0x3602.

[spirosgr1979]

My firmware is 0x360201

[The_Iceman]

Just have had contact with OrigenAE again.

They requested this problem to soundgraph and will contact me when they have a logical solution for our problem!

[E-4]

No news from SoundGraph so far but I had a brainfart yesterday and found a workaround, although this might not be usable for everybody:

I added the iMon PAD remote to my Logitech Harmony and switched the iMon software to that remote. This seems to solve a lot of the problems: the VF310 responds much better to the PAD IR signals; no wrong numeric characters, no more stuck '8' or '9' key when using the volume or channel up/down buttons, no 'magic' shutdowns and key repetition is smooth.

One problem I found when using the iMon PAD remote is when you press two numeric buttons quickly after each other then the second button you pressed will repeat endlessly, until you press another button. This can be annoying when selecting TV channels like 13, 24, etc. This might however be solved with some tweaking of the IR settings of the Harmony Remote - I haven't had time to test this yet.

Another thing I noticed: when you completely switch off the computer (unplug it) and then plug it in again you cannot power it on using the RC197 remote; this only works when the computer hasn't been unplugged. With the iMon PAD remote this does work. A small thing but interesting never the less.

I will definitely keep chasing Soundgraph for a solution for the RC197 issues as the iMon PAD thing is only a workaround, not a solution! The RC197 came with the case and it should work as expected.

Ivor.

[athan]

Thank you both, guys!
Now let's hold our breath waiting to see if Soundgraph techs will ever stop ignoring us.

[Multi Media PC]

We also have the same problem with all new OrigenAE cases with the VF310 inside.
The biggest problem is the repeated input of the last number.
So if you would like to zap from channel one tot 7 instantly you normaly pres the 7 button. In most of the cases that goes well but sometimes you recieve about 10 times the number 7 and its in some kind of loop.

An other problem is that in many cases the complete input doensn't work anymore for a couple of minutes or an complete reboot.
First we tought it was only at our demo system but now we get more reports from customers with the same problems.

They all use an VF310 made for OrigenAE and the RC197 remote witchs comes with the case.

[athan]

Welcome to the ...club! Seems we all share exactly the same problems.
Did you contact OrigenAE or Soundgraph's tech support regarding this issue?

[The_Iceman]

We also have the same problem with all new OrigenAE cases with the VF310 inside.
The biggest problem is the repeated input of the last number.
So if you would like to zap from channel one tot 7 instantly you normaly pres the 7 button. In most of the cases that goes well but sometimes you recieve about 10 times the number 7 and its in some kind of loop.

An other problem is that in many cases the complete input doensn't work anymore for a couple of minutes or an complete reboot.
First we tought it was only at our demo system but now we get more reports from customers with the same problems.

They all use an VF310 made for OrigenAE and the RC197 remote witchs comes with the case.

Yepp that's exactly the same behaviour I have on 2 different VF310 here with RC197...
Seems that now more and more users are reporting this problem!

Marvelous... :o

[athan]

Seems that now more and more users are reporting this problem!

And still no comments from Soundgraph. Great! :mad:

[Matt]

Hi,

I'm coming to join this funny group as i have the same problem with my new S14 chassis. The Origen support team pointed me to this forum.

I've read this thread and i'm dissapointed, that nobody seems to care. I don't know how much the other customers paid for the origen chassis, but it should be enough for them to get this right. After all, origen has to care. They have chosen to use the VF310, so they have to talk to Soundgraph, if it's not working.

I won't wait very long (as some of you did), since nobody even officially commented the situation yet.

Matt

[athan]

Welcome Matt,
We all paid premium prices for Origen + VF310 bundles. Personally, I will take every legal action available against Origen if they will not do something regarding this issue really soon. I don't care if it's Soundgraph's fault or not; After all it's Origen who decided to bundle this cr*ppy hardware with their cases.
I wont comment Soundgraph's non-existed support again. As you see their "support" team systematically ignore our complaints although they're around answering on other topics. I bet they wont like it when we post our not-so-great experience on other related websites.

[dk.jung]

Dear Customers,

Sorry for the late reply on this issue. For the OrigenAE VFD products, this hardware is different with our standard ODM/OEM products. And OrigenAE asked us to provide the Chipsets only with our application. We checked with OrigenAE today and it seems like that they made some mistake during the production in some lot of production. First production, we supplied our chipset (USB controller) with IR sensor but we just supply USB controller to them from next shipments.

Normally, our ODM/OEM customers do not manage a User Forums or do not make response about this kind of issues so we need some time to check what happening. Now we got a notice from OrigenAE that they will do RMA for their users. Please contact the following email address for it.

I hope that you may understand our position in this market. We supplied solution and help the end users instead of our ODM/OEM customers. But this kind of issues does not come from ourside and even we know it...but sometimes it is little bit difficult for us to talk and solve this issue with our ODM/OEM customers if they do not help it instantly.

support@origenae.com.

Thanks a lot...

[athan]

This make sense! However you would save us a lot of time, trouble and aggravation if you replied earlier.

[Matt]

Hi,

i received an email from origen today. I believe they really want to make us happy now!

Thanks!

[The_Iceman]

I immediately wrote to Origen after reading this posting...

I hope this new VF310s are shipping fast ... and RMA will work flawlessly...

[Matt]

My shop actually did the exchange of the VF310 via vendor and it works finally! What about you?

[The_Iceman]

My shop actually did the exchange of the VF310 via vendor and it works finally! What about you?

I've received my exchange display last week and tested it over the weekend...
No more ghost commands! finally everything works!

The exchange was also really fast (I live in germany)...

:D

[The_Iceman]

After using the "new" Display for a while Problems are there again ... seems that I've gotten the same faulty device back ...

That Display seems to get reaaally annoying...

Update:
Right now I'm in contact with the german main distributor of origenAE cases...
They're saying, that there is absolutely no error in Production and that OrigenAE is clueless where the error is coming from. Also they say that there are NO new displays from a new production series, all they can do is change the display and hope that it will work.

It seems that it happens only under some special circumstances or hardware combination...

For the record here are my hardware specs:

OS: Windows XP Pro 32bit (Tested the display on Vista32/64 Windows 7 32/64 also...)
Mainboard: Asus AT3N7A-I
Display: Philips 42PFL7403 connected via HDMI
Mouse/Keyboard Combination: Microsoft Wireless Entertainment Desktop 7000
Stock DVD Drive delivered by OrigenAE
Stock Remote delivered by OrigenAE
Using NO WLAN Stick or card only OnBoard NIC for Networking
Soundcard: Xonar HDAV 1.3 Slim (with or without makes no difference for this error)

Best Regards
Chris

[athan]

Right now I'm in contact with the german main distributor of origenAE cases...
They're saying, that there is absolutely no error in Production and that OrigenAE is clueless where the error is coming from. Also they say that there are NO new displays from a new production series, all they can do is change the display and hope that it will work.

That's exactly what I've been told by the same source.
Since this issue first appeared, I've returned two OrigenAE cases (both suffered) and now I'm awaiting a brand new M10. I hope for better luck this time. In any case, it's a shame such mechanically great products using these cr*ppy electronics. :rolleyes:

[The_Iceman]

At least I'm not alone with this problem!
Please give me a feedback how well the new case (or better the display) works...

I'm changing my Mainboard after Work for testing if this problem is MoBo related before I send it in for replacement (...again).

[athan]

I don't know yet how well the new case works; I've ordered it but not yet delivered. I'll keep you informed when it's on my hands.

BTW Chris, did you try the testing procedure to check whether your VF310 module is defective? I dunno if it's the same one E-4 posted a few weeks ago, or if it works as I don't have access to a VF310 right now; This procedure was sent to me from OrigenAE techs and I pasted here as-is. Give it a try and tell me your experiences.

Personally I'm deeply disappointed from VF310 and my only hope is to have better luck with my new M10 case. If not, I definitely never buy again a VFxxx equipped case, especially an OrigenAE, although I love their product design and mechanical quality. :(

1. Pressing a number on the remote (like 1 or 2) will result in a row
with a lot of the number you pressed and other random numbers in between.
Sometimes a “left arrow” action is even mixed in causing the cursor to move one character back. Example; when pressing the “1” key on the remote repeatedly or keeping it down notepad shows:
“11111111111111111111112111111111110111111111111 1511111”

2. Pressing the volume up and down buttons repeatedly or keeping them
pressed will eventually result in a stuck “8” character: it will keep repeating until you press another key on the remote like “enter”.

3. Pressing the channel up and down buttons repeatedly or keeping them
pressed will eventually result in a stuck “9” character: it will keep repeating until you press another key on the remote like “enter”.

4. I’ve had the PC shutdown automatically while testing this in Media
Center and in notepad. I think this only happens when pressing the “back”
key repeatedly.

5. Character repeating isn’t smooth which you can clearly see in
notepad; use the remote and the characters will repeat fast – then stop – then repeat fast again. When entering the characters using the computer’s keyboard repetition is smooth (as it should be).

6. Volume up and down isn’t smooth; when you keep the volume button on
the remote down you can see the volume slider move – stop – move – stop.
Also; when you repeatedly press volume down because you want to go from i.e.
volume 95 to 90 the volume will suddenly drop a random number of steps on its own. The same goes for volume up.

7. Any key press quickly followed by the “volume down” key will make
that key repeat endlessly until another key is pressed. So if I press 1 and immediately after that press the “volume down” key then “1” is repeated endlessly. Works in notepad but in Media Center too; just press the “up” key for instance, release it and then immediately press “volume down” and watch the Media Center scroll through its menu endlessly.

[The_Iceman]

Yeah tried that already with my replacement display:
Opened up notepad and tried different keys.... here is the copy and paste:

111111111111110111111011111111111111 <- Key 1
222222222222212222222222222222222212 <- Key 2
3333333333333333333333333313313333333 <- Key 3
444444444244444444444444244444244444 <- Key 4
55555555555555555555555555552255555 <- Key 5
666666666666666666666666666666666666666666366666
77777777777777777777777777777777777777777777777777 777777777777777777773777
88888888888888888888888888888888888888888888888888 88888888888888888488888888888
99999999999999999999999999999999999999999999998999 999994999
00000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000 <- "0" works...
8 -> Volume up got stuck with 8
The Back button repeately pressed enables the "Power" Button... -> PC Shuts down....

[athan]

Do you know what really bothers me? OrigenAE techs say what we already know, that they've found a design flaw and offer replacement modules. On the other hand, their official distributor in Germany insists that there is no production problem and no "fixed" parts have been sent from Korea.

I tried asking OrigenAE for more technical details on this issue and proposed fix implementation. I even offered to apply the fix myself if they give me more info on circuitry changes. They never replied to this...

Now who to believe? :mad:

[PHT]

Hi Guys

M10 is shipped with RC153 remote. Do you experience the same problems?

Regards

[The_Iceman]

Do you know what really bothers me? OrigenAE techs say what we already know, that they've found a design flaw and offer replacement modules. On the other hand, their official distributor in Germany insists that there is no production problem and no "fixed" parts have been sent from Korea.

I tried asking OrigenAE for more technical details on this issue and proposed fix implementation. I even offered to apply the fix myself if they give me more info on circuitry changes. They never replied to this...

Now who to believe? :mad:

Exactly ...
Yesterday after work I changed my MoBo just for the sake of testing...
SAME problem persists....

I ALSO tested different remotes (Philips SRM5100, Original MCE Remote V2, OrigenAE MCE Remote...) ... so this MUST be an issue with the display...

[athan]

M10 is shipped with RC153 remote. Do you experience the same problems?

Who knows? My M10 hasn't arrived yet so I cannot tell. I think it shares exactly the same vf310 design so probably it suffers from the same problems as any other OrigenAE case.

[The_Iceman]

Who knows? My M10 hasn't arrived yet so I cannot tell. I think it shares exactly the same vf310 design so probably it suffers from the same problems as any other OrigenAE case.

My case is an M10 with this remote... as I said... it doesn't work

[athan]

My case is an M10 with this remote... as I said... it doesn't work

Chris, try asking OrigenAE themselves to send directly to you the replacement and supposedly fixed module. That is what I'm going to do this time if my new M10 has same issues.

[The_Iceman]

Chris, try asking OrigenAE themselves to send directly to you the replacement and supposedly fixed module. That is what I'm going to do this time if my new M10 has same issues.

Tried that... And here are some lines from the answer :

"...As you knew well, the IC Chips(included firmware) of VF310 is from
Soundgraph and we already reported to them for solving to the problem by
firmware updating or another ways and they going to investigating & analysis
at the moment.

Soundgraph will try to do best to give us the best solution ASAP for our
valuable users of VF310 module and we will get back to you as soon as we
find a solution to it... "

So the ball goes over to Soundgraph again... Before I don't get a working solution I'll not send my Display in again :o

[athan]

Great! First they say they've found a design flaw and offer replacement parts, now we have to wait a few more ...months before getting a comment from Soundgraph's nonexistent support. :mad:

Sometimes I really miss the old days when tech market was free from far eastern products...

[The_Iceman]

For Quick solution use the IMON Remote NOT the Media Center one... this one works without a problem!

[athan]

For Quick solution use the IMON Remote NOT the Media Center one... this one works without a problem!

Do you mean the remote that comes with iMon retail products?
I thought it wasn't any different from other RC6 remotes. Are you sure it works without any "ghost" command issues?

[The_Iceman]

Do you mean the remote that comes with iMon retail products?
I thought it wasn't any different from any other RC6 remote. Are you sure it works without any "ghost" command issues?

That's what OrigenAE said via Mail...

[athan]

That's what OrigenAE said via Mail...

Since first noticed the ghost command symptoms, I tried quite many different MCE compatible remotes without any success. Anyway, I have no problem getting a SoundGraph remote, after all it's just a few bucks.
However it's very hard for me to take serious or even listen to OrigenAE. So far they said much but did nothing to address the problem. How to believe 'em now?

[justinteractive]

Hi guys,

i am pretty sure there is no fix available from Origaen yet. As some of you already stated, they (or their chinese supplier) are complete amateurs when it comes to electronics.
I remember when they had to fix the USB Bus powered problem on their media-bays two years ago. It took them 6 months to figure out the problem (since then you see a little SMD resistor soldered on one pin of the USB chip)

Anyway back to our new VF310 issue.
The problem definitely appears only on some configurations. I have tested 4 VF310 modules on three different Mainboards. They all do not work on two boards (GA EP45 UD3LR und GA P35 DS3) and do work on a GA EP35 DS3R.

I dont know if its really related to the MB. I would doubt it, but it must be something with the USB configuration. On the P45 Chipset MB the remote works a little better when the VF310 is connected to the media-bay USB port then directly to the MB.

Hope these guys find the issue quick and not take 6 months again.... :mad:

and YES I am sick of this far east crap as well !

[dk.jung]

Dear all...

We tried to find out the solution of OrigenAE product, VF310 and we found that there is compatibility issue with RC197 remote control that is used for OrigenAE VF310 and iMON VFD firmware. Normally iMON firmware can decode MCE signal well but this RC197 remote control signal is not as same as normal MCE remote control. If user use iMON PAD remote control or other MCE remote control, this problem can be solved. Also please contact support@origenae.com to get the customer support from OrigenAE on this issue.

Thanks and regards...

[athan]

Dear all...

We tried to find out the solution of OrigenAE product, VF310 and we found that there is compatibility issue with RC197 remote control that is used for OrigenAE VF310 and iMON VFD firmware. Normally iMON firmware can decode MCE signal well but this RC197 remote control signal is not as same as normal MCE remote control. If user use iMON PAD remote control or other MCE remote control, this problem can be solved. Also please contact support@origenae.com to get the customer support from OrigenAE on this issue.

My dear friend dk.jung,

I wish it was so simple but it's not! You and OrigenAE have to digg deeper to track this nasty issue.

During the last three months I tried more MCE remotes than in my whole life, without success. Ghost - stuck commands were always present even using Microsoft original MCE remote, XBox 360 official one, Hauppauge's A415 and RC6 remotes and a few others I had access to. :rolleyes:

[The_Iceman]

Dear all...

We tried to find out the solution of OrigenAE product, VF310 and we found that there is compatibility issue with RC197 remote control that is used for OrigenAE VF310 and iMON VFD firmware. Normally iMON firmware can decode MCE signal well but this RC197 remote control signal is not as same as normal MCE remote control. If user use iMON PAD remote control or other MCE remote control, this problem can be solved. Also please contact support@origenae.com to get the customer support from OrigenAE on this issue.

Thanks and regards...

I think that's not correct... I also tested original MCE Remote V1/2, Philips SRM5100 and they all behave the same...

[paulyx]

Hi guys,

unfortunately I've the same problem with my new HTPC (S14V & VF310). I'll contact my german dealer in hope to get a viable solution.

[adidino]

What's the bottom line on the issues with the Origenae vf310? I received my M10 case a couple of weeks ago. Started to notice random characters appearing when a browse my music and movie titles. Example.. "@" then "1". Media Center translates these characters as commands from the remote and tries to search for titles starting with these characters. Very annoying... Then it works fine for a while... Is this similar to some of the issues on this thread?

[athan]

Is this similar to some of the issues on this thread?

Enjoy the club, adidino. This is one of the symptoms we're talking about.
Unfortunately neither Origenae or Soundgraph have a clue. :)

[adidino]

Enjoy the club, adidino. This is one of the symptoms we're talking about.
Unfortunately neither Origenae or Soundgraph have a clue. :)

I'm surprised to hear they don't have a clue. I can't be sure but it would appear it translates the direction pad from my remote as a random character (the "@" being the most popular). That seems to be the only time it happens (for me at least). Again, it's not consistent. It may not have an issue for days.. other days it gets pretty annoying.

[feederz]

It appears I'm also having this issue with my Origen AE S10v and remote. Has anybody tried the Imon Pad Remote control? If so does it work perfectly?

I'm wondering if I should get one of these although am reluctant to do so having paid a premium price for the otherwise quality case.

[adidino]

It appears I'm also having this issue with my Origen AE S10v and remote. Has anybody tried the Imon Pad Remote control? If so does it work perfectly?

I'm wondering if I should get one of these although am reluctant to do so having paid a premium price for the otherwise quality case.

I haven't... and I don't plan on trying it. They need to get this resolved. It's pretty silly that no one from Sound Graph or OrigenAE has nailed this down yet...

[The_Iceman]

Imon Pad works really good and without issues on the 310...

But this is a workaround and not a solution...
Hope a firmwareupgrade or fix for the hardware will come up soon...

[feederz]

I tried installing 7.85.0222 last night from here and after doing so my remote seems to be behaving a lot better. I still wouldn't say it's perfect (the volume now increases/decreases as you hold down the buttons but the increase/decrease is a little jerky as it does so).

Still no VFD output when running WMP though, anybody got this working with Win 7?

[adidino]

Can't say for sure but I suspect the random character issue may be linked to the keyboard driver. I replaced my rf keyboard and dongle with a logitech blutooth kb and this issue suddenly got worse. The "@" character appeared about 10 times in a row in Media Center while scrolling titles. It seems the VF310 translates the Dpad on my remote as "@". My Origen dealer is sending me a soundgraph remote. We'll see..

[The_Iceman]

Can't say for sure but I suspect the random character issue may be linked to the keyboard driver. I replaced my rf keyboard and dongle with a logitech blutooth kb and this issue suddenly got worse. The "@" character appeared about 10 times in a row in Media Center while scrolling titles. It seems the VF310 translates the Dpad on my remote as "@". My Origen dealer is sending me a soundgraph remote. We'll see..

Yeah.... this can be right...

Just switched from Microsoft Wireless Desktop to Logitech with this new Unifying technology and after reading your post I tested my MCE Remote again!

With Logitech I've less errors than with MSFT Bluetooth...
Tested a few times with different keyboards... and this is definitive related...

Great Find!

BTW: Any news on this Soundgraph?! Over 3000 views on this thread already and nothing new ?!

[adidino]

Iceman - do you still have the issue when using the Imon pad as well?

Yeah.... this can be right...

Just switched from Microsoft Wireless Desktop to Logitech with this new Unifying technology and after reading your post I tested my MCE Remote again!

With Logitech I've less errors than with MSFT Bluetooth...
Tested a few times with different keyboards... and this is definitive related...

Great Find!

BTW: Any news on this Soundgraph?! Over 3000 views on this thread already and nothing new ?!

[The_Iceman]

No... IMON Pad works flawelessly...

[adidino]

No... IMON Pad works flawelessly...

Interesting.. do you think if I teach my universal remote to learn the imon pad ir commands that I will get the same positive results from the universal?

[The_Iceman]

Interesting.. do you think if I teach my universal remote to learn the imon pad ir commands that I will get the same positive results from the universal?

If this works... sure why not ;)

[adidino]

Any ,more reports or news on this issue? I haven't received my imon remote from my dealer but I'm now noticing issues with the "ok" button not responding while I naviagte and the D-pad will not respond either. A reboot of the system resolved it but this is getting pretty annoying. Are we confident the imon remote is the answer?

[detoxb1]

Looks like I'm suffering from the exact same issue... Any success from anyone?

I'd like to keep the RC197 remote as it looks nice and looks more appropiate for Windows Media Center than the iMON remote.

[The_Iceman]

Looks like I'm suffering from the exact same issue... Any success from anyone?

I'd like to keep the RC197 remote as it looks nice and looks more appropiate for Windows Media Center than the iMON remote.

No Chance ... There seems to be no Support on this issue ... The only Chance is to use the imon remote

[zicoz]

My setup atm is a Harmony One that is programmed as an Imon remote, and then I have created my own translations in the Imon manager. This works on an old case that I have, but I'm looking at the v10 or s10 atm, will the same setup work on those versions of Imon?

[waltermalter]

@Iceman, (or who ever has an answer at hand)

can you tell me what Vendor/Device/ I must chose in the harmony-setup-software to add the iMon Pad to my Logitech Harmony?

Cheers,
Walter

[The_Iceman]

I finaly found a working solution for this nasty "remote" Problem...
I don't wanted to use the imon Pad because It was ugly as hell and not so snappy and fast reacting like the mce Remote....

So I tried to use the VCD in combination with an external mce Remote ir Sensor...
But that was not good, because you can't disable some commands (like up,down,Left,right, ok....) received by the imon ir...
The trick with using tape over the sensor did not give me the abbility to power on the htpc with the Remote.... so I removed it again. Also switching to IMON Pad inside the IMON manager DOES NOT disable those keys... so it WAS impossible to use the MCE Remote IR Receiver...

Then I tried this:
Inside the device Manager are 2 USB Input Devices:
One for the Imon VFD & One for the receiver...
You can recognize them, because you can't disable them by right click...
You just have to Test which one is for the receiving, by deleting it...
After a rebot IT reappears again...
Now Write down the location id of this Device, Start up regedit and Search for it...
My ID goes like 0000.0006.0000.001000.000. and so on....

When you found the String change "ConfigFlags" to 1 and after a reboot you keep the ability to Power on the pc via Remote but the imon ir doesn't accent ANY signals anymore...
And I'm happy with the mce ir Receiver, can use the VFD Display and have snappy and fast results with my MCE Remote AND the best at all NO Ghost Commands...

If you can't Change the string to 1 try taking ownership of the Folder with right click....

[mentaliss]

Dear Sir,
The transmission range of iMON is about 10m and we have tested without problem under our office environment.
You might try to check if IR receiver on board is not bending or other issue.
Sorry if it doesn’t help to you.
__________________________________________________ ________
My question put to Origenae regarding my new build with the remote not working once distance exceeds 5-6 ft from PC !

[buggerlugs]

id just like to add my voice to this discussion and say that ive got the same issues with my s10v case.

what id like to ask is - is it possible to replave the module with one of imons retail products? because id be happy to do that to get it working without errors, but i dont know if the displays are a generic fit and size

[johnny.hur]

Dear bugglerlugs,

VFD module in S10V is a very unique product for us. It is little bit different with our ODM/OEM VFD model. We don’t supply the whole VFD unit, but only a chip.
And it seems that VFD module in S10V is much bigger than VFD module in normal ODM/OEM VFD model. Please check the link below.
http://www.soundgraph.com/oem-vfd-specification-en/

We can support SW issue with this product. But for HW issue you should contact with OriginAE.

Regards,
Johnny Hur

[buggerlugs]

Dear bugglerlugs,

VFD module in S10V is a very unique product for us. It is little bit different with our ODM/OEM VFD model. We don’t supply the whole VFD unit, but only a chip.
And it seems that VFD module in S10V is much bigger than VFD module in normal ODM/OEM VFD model. Please check the link below.
http://www.soundgraph.com/oem-vfd-specification-en/

We can support SW issue with this product. But for HW issue you should contact with OriginAE.

Regards,
Johnny Hur

So i cant even replace this buggy piece of hardware with another working unit?
Crazy!

Ive already told origen ill never buy anything from them again because this is a fiasco.
I bought their case - and its a very expensive case - primarily because the ir and display were built into the case.
Had i known the hardware was faultly at best i wouldnt have bothered.

I appriciate you say its not your problem but all i see is that this unit doesnt work and its featuring your chip and using your software, therefore I think you have a responsibilty somewhere down the line.
Maybe you could produce something that will fit this case and offer it as a purchasable replacement - at the very minimum you need to be restrictive to what oem partners are allowed to do, because this gives you a bad name too.

[mentaliss]

with all the complaints seen here in the posts Origen are at fault as they bought and installed a VFD product that NOT FIT FOR PURPOSE, is'nt it time we all signed into a online petition demading that ORIGEN and iMON got together and sorted out the CUSTOMER'S concern

[odin568]

damn, same issue with M10... Anything I can do?

[Jomi]

Hi,

I am having the same issue with my S16V with an VF310. My case is actually 1 year old and I never got it to work so I just wanted to check if anyone has a working solution now? Is there a online petition going on?!

regards,
Jomi

[Fosphatic]

Hi all,

I have an origen ae s16t case and bought me the IR310 Replacement Kit for my dead IR210 board. After I connected the IR310 Board to my case I could start up the system with remote again. But after few Minutes of testing I had the same ghost input commands like you described here in this thread. So it must be not a problem with the VFD itself, because my case has no VFD. It has a touchscreen but the same issue like you description. Now I'm a little bit angry that I haven't found this thread before I ordered the replacement Kit. :(

And it seems that we never will receive a solution for our issue, right?

Best regards,

Fosphatic

Edit: *phew* I had luck and could solve my problem. The IR Receiver was not running well because I had also my FingerVU 706 with separate IR Receiver inside plugged into my HTPC. It seems to be that even when Imon Manager has a function tab for multiple Hardware and I had choosen the right one it was reproducing strange signals like you described here. When I opened a notepad and hold the a button of my Harmony Remote it was sending something like 11115411112111311115. This problem was gone when I plugged off the FingerVU. But I like this touchscreen more then the Origen AE's build in device.

So what's next? I removed my OEM Touchscreen out of the case and instead of this I've integrated the FingerVU 706 inside my S16T. As the IR Receiver of this touchscreen is on the top left corner of the device it was now covered by the frontplate and of course not receiving signals any more after I closed my case and my problems were gone since this procedure. But it's definetely a bug that it's not working like it should when VingerVU 706 is also plugged in to the same Case. Like I can remember SG was making advertisement some time ago, that is definetely possible to run more then one SG Device on one machine...

The s10v that I had build last year for my mother is strangely working well withought any problems. Is it possible that you just had a very bad luck to get a faulty hardware also maybe bad luck² when you had received your replacement? In fact it seems to be an issue that is not depending on the chip of SG. I have the same Firmware version on my chip like you do and I checked the firmware version of my mother's s10v it was the same like my. So i would guess that it went something wrong with your devices when it was produced in china...

I hope all of you will get you problem fix somehow. -_-

[polarie]

where is my Post gone?

had written that antec elite veris made the same problems -
bought a new one (spare-part) - same thing happend after a few hours ...

tried serveral combinations with lots of differnet mITX bords 7 or so.

also 4 or 5 differnet HDDs - also winXP and Win7 ...

no combination change brought a solution.

(just the short form - couse i don't want to write again all the stuff i wrote yesterday and which is deleted now)