xboxscene.org forums

Author Topic: 360gcProg v1.3 : Add an alternative timing for Trinity  (Read 153 times)

playonlcd

  • Archived User
  • Jr. Member
  • *
  • Posts: 56
360gcProg v1.3 : Add an alternative timing for Trinity
« on: January 23, 2012, 04:42:00 AM »

So any jed for others glitchers that use same xilinx xc2c64a cip?
Logged

warbeast

  • Archived User
  • Hero Member
  • *
  • Posts: 509
360gcProg v1.3 : Add an alternative timing for Trinity
« Reply #1 on: January 23, 2012, 09:02:00 AM »

this will work on other glitch chips ive just used it on a x360glitch
all these groups are just copying each other only the pcb is changed plus a few tweaks they all have xc2c64a at the moment

untill a group smart enuff to build better hardware does so the tools like this should work for all
Logged

jayboy86

  • Archived User
  • Full Member
  • *
  • Posts: 140
360gcProg v1.3 : Add an alternative timing for Trinity
« Reply #2 on: January 23, 2012, 09:25:00 AM »

question is does it make any difference to x360glitch or coolrunner boot times?
Logged

warbeast

  • Archived User
  • Hero Member
  • *
  • Posts: 509
360gcProg v1.3 : Add an alternative timing for Trinity
« Reply #3 on: January 23, 2012, 12:34:00 PM »

from what i understand changing the timings on slim unlike fat most the time it just doesnt help infact most of the time it just makes it worse but anything is worth a shot i guess

my slim with x360glitch has a boot time of 15secs with a 32cm wire thats the best i can do with it being a constant 15secs every time however if i make the wire short as can be i get the 4sec boot time but its not constant and can take up to 1min moving the wire around to find a sweet spot works well to

this new trinity jed didnt help my x360glitch but to be honest i didnt think it would as with my boot time being 15 secs im already on the best timing plus as i said messing about with timing on slim doesnt really help for most  it makes it worse no matter who u bought the SAME hardware from
Logged

geekay

  • Archived User
  • Newbie
  • *
  • Posts: 5
360gcProg v1.3 : Add an alternative timing for Trinity
« Reply #4 on: January 23, 2012, 04:33:00 PM »

I can't say I've noticed any difference yet but most slims seem to have a mind of their own.  Doesn't seem to matter if you have two identical units wired the same and everything you'll still likely see a huge difference in glitch performance.

One big plus is the program runs the one dedicated function we all use rather than installing impact.
Logged

ruciz

  • Archived User
  • Full Member
  • *
  • Posts: 169
360gcProg v1.3 : Add an alternative timing for Trinity
« Reply #5 on: January 24, 2012, 05:41:00 PM »

agreed.

I had more success with a C-MOD for reliability than I had
Matrix
Matrix II
CoolRunner
X360Glitchip
X360glitcher (dx one)

They are all over the place. I had no success with different capacitors, different wire lengths, or different chips.  
It is a combo of them all usually.
I did notice one thing, only with the CoolRunner.
Once the slim was warm it would do a reset chirp.. constantly reset itself for 15-20 sec, then do an attempt, then go back to constant resettting.
putting the CoolRunner in PHAT mode didnt improve boot time but did fix this issue.

QUOTE(warbeast @ Jan 23 2012, 08:34 PM) View Post

from what i understand changing the timings on slim unlike fat most the time it just doesnt help infact most of the time it just makes it worse but anything is worth a shot i guess

my slim with x360glitch has a boot time of 15secs with a 32cm wire thats the best i can do with it being a constant 15secs every time however if i make the wire short as can be i get the 4sec boot time but its not constant and can take up to 1min moving the wire around to find a sweet spot works well to

this new trinity jed didnt help my x360glitch but to be honest i didnt think it would as with my boot time being 15 secs im already on the best timing plus as i said messing about with timing on slim doesnt really help for most  it makes it worse no matter who u bought the SAME hardware from


did 30 so far and havn't seen a reliable 15 sec boot time.
Best I get is 30 sec only on 7/10 attempts. Theres always at least 2 which take over 1.5 min.
Logged