TP3244 Software

[Tabor]

Version 3.1 is in first post.

fixes:
Output 4 offset issue.

[ɟɐsʇǝppʎ]

Sorry

Thanks to Matt, who realised there was no difference in the files That were posted.

The new one is there now.

You will see some flicker with some colours and/or effects using the 2801 without changing the resistor on the TP. If using the 2801 it is definetly worth while changing the resistor. The 6803 are a bit better and work well with the pixel close to the controller if not changing the resistor on the TP

[CRPerryJr]

Help!
 
I know this is probably a silly question, but what are you using to push the firmware?  I've updated firmware for Renards, and for the Triks-c, and have the hardware and software for both of them.  (JDM programmer for PIC which looks like it has an ICSP connector as well as ZIF socket using WINPIC800 & USBTINYISP AVR Programmer using AVRDUDE)  It doesn't look like WINPIC800 supports the PIC32MX chip.  Any recommendations?
 
TIA!

[chicken]

pickit3 for me.  worked fine. 

[Wombat]

I use pickit3 as well

[Wombat]

Hi Tabor,

Does that lastest update 3.1 fix the reverse issue we discovered this morning as well?

[AussiePhil]

Pickit2 will also work.

Tabor thanks for all the hard work

Phil

[chicken]

You will see some flicker with some colours and/or effects using the 2801 without changing the resistor on the TP. If using the 2801 it is definetly worth while changing the resistor. The 6803 are a bit better and work well with the pixel close to the controller if not changing the resistor on the TP

I just swapped all 4 1500 resistors and am still having the same flickering problems.  My setup is 50 of Ray Wu's new "waterproof" 12x8mm RGB 2801 Pixels off of output #1 on the TP.  The TP is connected via an RPM DMX dongle to the latest version of LSP.  To test I created a ramp up that fades from blue to red over about 15 seconds.  You see intensity flickering as the ramp up is occurring.  Anything else I can try to fix this?  Thanks

[Wombat]

Another Question.

If you have previously configured the TP3244 using the jp1 jumper on 3.0 and then load new firmware 3.1 do you need to set the jumper the first time again to configure it again?

Keep up the great work Tabor

Wombat

[Tabor]

No

[Tabor]

Chicken

Have you tried Vixen?

[dmoore]

Question - does it really matter if you don't put the actual universe number in?  Is Universe only used for HyperDMX?
The universe number is used if you have the TP3244 connected to a different universe on the ECG. So for example if you have 4 TP's connected to a DR4, instead of changing cables you can just send the config to a different universe and the TP on that particular circuit will update.
Nothing to do with HyperDMX.

Tabor -
There are two universe listings - one labeled "EtherConGateway Universe:" which I understand to be the "programming output" slave you are sending the TP3244 config to.  My question is about "Universe" listed in each output.  I read, then re-read and read again the description and it seems like it is describing the EhterConGateway Universe instead of the Universe in the Output boxes.

My question is - what is the Universe box used to designate?  If I have a TP3244 that I've programmed with universe 1, would it still work when I hook it up to a ECG on slave 2 setup as universe 2? 

It seems like the universe option would be there to "listen" for data destined for a given output on a TP3244 if you were using something like HyperDMX, since you can only get one universe of data on a single cable (485..technically speaking I guess.)  How else could the TP3244 be "listening" for more universes than the one it is on since there is on a single universe per cable.

Thanks!
david

[dmoore]

I'm wondering if anyone else with 6803 pixels with the 3.1 update have their TP3244 working properly.  When I did all my build and testing in the shop, the TP3244 with the prior firmware/setup was working as expected.  I am now unable to get it to work.  I've tried:

* Output from LSP using the ECG (works on other universes, including an element that has the old TP3244 firmware)
* Output from a Lynx dongle using the startpattern program (confirmed working with other elements in the display)
* Made sure to do the power down, JP1, config, power up after the firmware flash (done twice now)
* Tried hooking up only one output
* Tried supplying power all from the same power strip (ground loop issues?)
* Tried switching the strips around (I have 8, 42 pixel strips all setup the same) on two different TP3244's
* Tried every combo I could resonably think of in the TP3244 software (setting all to None, just one output, different universe, etc, etc)
* Taken a laptop with Lynx dongle outside for testing to remove any cable length issues

I'm at a loss now.  The reason I'm leaning toward firmware issue is that it was working on the old firmware and my other element that has the old config and firmware works fine still, with the same ECG/LSP setup.  I updated the firmware to resolve the 3+ output issue.

Anyone have any other ideas for me to try?

[Tabor]

David the Universe in the output boxes is used for Hyper DMX.
That universe box will only ever be 1, 2, 3 or 4.

On the side of 6803, there shouldnt be any reason why its not working, I have to run up some more boards tonight I will check it with 6803.

[Tabor]

Hello David

I have just run up two boards with V3.1, there doesnt seem to be any problem with the actual output.
This leads me to think that the configuration of flashing of the firmware is not taking.

When you flash the PIC with V3.1 after the flash and before you put the jumper on, does led 6 flash a 1 Hz?
If it does just try doing the config again, make sure you see Led 3 flash.
If it comes on and stays solid then you need to use the JP1.

I noticed just then when sending a lot of data to the TP, led 3 did not flash when sending config, I hit send again and it did.
If possible use the ECG for config.