DirectX button mappings w/ PHCC

Advanced search

Help us keep Viperpit alive !

[lightning]

Just a little update -- Jay has lent me a PHCC setup so I can write the code to support it in JoyMapper, but it looks like I'll need to order a PIC burner in order to get this thing working, because after attempting to update the PHCC firmware over the serial port, the PHCC is now stuck in a state where both the red and green LEDs are on, and no communications is possible now over the serial port. 

So as far as I can tell from the little information that's actually out there, it looks like I need to update the bootloader on the PIC itself.  Unless I'm doin' it wrong  

Are there any PHCC owners out there that care to comment? 

[idekkers]

what do you get form it when you open a hyperterminal session to it ?

Ido

[Crease-Guard]

Guys, I'm going to move this out of Leo's thread since we are now onto another product.

Jay

[LeoL]

If the bootloader was properly coded, you cannot overwrite the bootloader section. You need to find out if there's a way to force the MCU to "boot" into the bootloader section. Right now it sounds like its trying to execute the code and bypassing the bootloader.

I thought about this scenario when I designed my products and should the update fail, I provide a jumper to force the MCU into the Flash Loader program so you can reprogram the device. Hopefully PHCC has a similar method to recover from a failed update (i.e. ground one of the input pins, etc.) If not then you have no choice but to reprogram the MCU with a fresh bootloader and that just defeats the whole purpose of having the bootloader in the first place.

[lightning]

If the bootloader was properly coded, you cannot overwrite the bootloader section

From what I understand, the original bootloader did not write-disable its own segment, so this was in fact possible.  With the latest bootloader for the PHCC, it's my understanding that this is not a problem anymore, since the newer bootloader code write-disables its own memory area.

provide a jumper to force the MCU into the Flash Loader program so you can reprogram the device. Hopefully PHCC has a similar method to recover from a failed update

On the PHCC motherboard itself, there's a reset jumper, but it's my understanding that that's where you wire up a switch to cause a manual reset of the device, and it doesn't control firmware loading...

On some of the other PHCC stuff (the USB firmware, for example), I believe there's like a "magic combo" it looks for (e.g. two presses of the reset button within 2 seconds) that puts the bootloader into firmware update mode. 

I haven't seen anything that would imply there's such a function on the PHCC motherboard -- so that implies reprogramming the MCU, as you said.  Agreed, it completely defeats the point of a bootloader to have to do that.  An error of omission, I suppose.

[LeoL]

If you don't have one already, head on over to www.sparkfun.com for USB programmers or pick one up on EBAY cheap. I wouldn't waste my time with any of those DIY serial port programmers. They work fine if the moons of Jupiter are in alignment....most of the time! Just get yourself a good USB programmer and save yourself the headaches.

[lightning]

Thx, Leo, for the link!

[lightning]

JoyMapper Alpha 3 is released.  Latest version adds support for mapping PHCC inputs to PPJoy virtual joysticks.

Download from my Assembla project site

[lightning]

There's an update to the PHCC Interface Library code that will be released over the weekend; this solves a problem with the interpretation of the analog input update packets.  Since this will affect JoyMapper, there will be an updated release of Alpha 3 containing that fix.

[bnepethomas]

Busy programming keystrokes into the pit, and then remembered about this little gem.  I could be having a major blonde moment here, but it JoyMapper seems to recognise key presses from MM2s but not GRay.  any tricks of the trade for that?

Ta

Peter

[lightning]

Stand by for the update to JoyMapper -- been busy with other things for a few weeks and have not rebuilt this yet.   

[bnepethomas]

Stand by for the update to JoyMapper -- been busy with other things for a few weeks and have not rebuilt this yet.   

ta muchly

[Doc]

I have some trouble getting started with the PHCC....

I can't get JoyMapper to recognize my PHCC-motherboard when I connect it through USB. 
When I connect the PHCC-motherboard with the null-modem cable to my testcomputer, the PHCC Test Tool software does recognize it, so I don't think the problem is in the motherboard itself.
I did install PPJoy and selected Virtual Joystick...

Can anyone help me please?

Doc

[lightning]

I have some trouble getting started with the PHCC....

I can't get JoyMapper to recognize my PHCC-motherboard when I connect it through USB. 
When I connect the PHCC-motherboard with the null-modem cable to my testcomputer, the PHCC Test Tool software does recognize it, so I don't think the problem is in the motherboard itself.
I did install PPJoy and selected Virtual Joystick...

Can anyone help me please?

Doc

If the PHCC Test Tool software sees your PHCC motherboard, but JoyMapper does not (on the same computer, connected the same way), then there may be an issue with how JoyMapper is doing the autodetection, but at first glance I'd be a bit skeptical of that hypothesis, because the detection routine that is being used by both the PHCC Test Tool software and JoyMapper is nearly identical. 

One thing that would help -- Can you confirm that these tests are both being run on the same machine with the PHCC motherboard connected in the same fashion? 

Also, when switching from one tool to the next, be sure to reset your PHCC motherboard (power off,power back on).  Otherwise the PHCC motherboard's firmware can be left in an inconsistent state.

Lastly, there is a known bug in the serial port drivers for certain USB->RS232 cables containing chips made by Prolific (specifically, the PL2303 chip).  Any of the USB->RS232 adapters based on the Prolific brand chips suffer from buggy drivers, not just under Vista but on all versions of Windows.  Due to the poor driver implementation for these chips, I cannot support them under Windows, as no workarounds exist.  They are, regrettably, junk.  Ask me how I know

Unfortunately, these Prolific cables are private-labelled, and frequently, so are the drivers that ship with the cables.  So there's not always an easy way to tell if you're using one made by Prolific.  The only way is to hunt around in the Windows Device Manager, under Ports, then select the COM port that your PHCC motherboard is connected to, then look on the General tab, you'll see the driver manufacturer and location.  Also check under the Driver tab. 

[Doc]

Hi Lightning,

First of all thanks for your help!!

My set-up is like this, all on the same system:

PHCC connected through COM1.
* The PHCC test tool does see the board. I've connected a pot-meter to test it and it works.
* JoyMapper (v0.3.0.0) does not see the board, even after a power reset of the PHCC-board.
I've tested it with the programms running seperately and and the same time.

Q/ Do I have to use the PPJoy Program "PPJoyCOM"?
I've tried to make a Virtual Joystick in PPJoy, Max amount of axes and buttons. After running PPJoyCOM all the axes and buttons in windows Gamecontrollers are flashing up and down. I did shortcut all the "empty" axis-cennections.

In windows device manager there is a yellow note of exclamation in front of the line "Prolific USB-to-seria Comm Port (COM3)...
So I think my USB-to-serial cable is probably junk....
Fortunately my flightcomputer does have a old fasioned COM-port..

I hope this gives you a bit more information about my problem

Doc

19:40 UTC
September 03,2010

Bones308th (41)

Ka-Bar03 (5074)
AiRdAncE (3955)
Crease-Guard (2725)
Nigel (2387)
Red Dog (2330)
Kneeling Warrior (2326)
Nikolas_A (2148)
lightning (2126)
101-Douxx (2024)
Flareless (1708)