[Turtuv]

Today I've received an email from hasbro where they communicate to me that have sended a "replacement part" for my two in the Box after I opened a support ticket back in December for volume problem etc. I really don't know what to expect but I'll let you know

[Broccoli]

Today I've received an email from hasbro where they communicate to me that have sended a "replacement part" for my two in the Box after I opened a support ticket back in December for volume problem etc. I really don't know what to expect but I'll let you know

Did you have to send them anything in? They had me send in the trap and holster (i have a volume issue too). This was back early January. I got an email from them about a week ago that they got it and are waiting on parts to fix it so it will be sent back out in early 2025. No idea on how this will all shake out but hoping for the best.

[Turtuv]

Today I've received an email from hasbro where they communicate to me that have sended a "replacement part" for my two in the Box after I opened a support ticket back in December for volume problem etc. I really don't know what to expect but I'll let you know

Did you have to send them anything in? They had me send in the trap and holster (i have a volume issue too). This was back early January. I got an email from them about a week ago that they got it and are waiting on parts to fix it so it will be sent back out in early 2025. No idea on how this will all shake out but hoping for the best.

no, they didn't asked for anything. in fact, they told me back in december that they let me know after talk with the responsible and now i've got the email directly where they told me about this. i've received the package and they sent me another trap, without pedal and cable, the trap only but i hadn't the time to try it. i hope to do it soon tho

[Broccoli]

Well, that is frustrating. Not that I had to send the broken trap in, but the inconsistency of Hasbro's costumer service. Part of me is concerned that I will get screwed over with this, but I am going to remain hopeful that it will work out.

[Nomake Wan]

Inconsistent is right. I know a user in Europe who had a defective trap out of the box (it wouldn't even power up), and contacted Hasbro about it. After some back and forth they shipped him a PKE Meter without any warning. After further back and forth clarifying that it was his trap that was defective, they insisted that he send the entirety of his Two in the Box (everything!) back, and they would ship him another complete set once they received it.

[Turtuv]

Inconsistent is right. I know a user in Europe who had a defective trap out of the box (it wouldn't even power up), and contacted Hasbro about it. After some back and forth they shipped him a PKE Meter without any warning. After further back and forth clarifying that it was his trap that was defective, they insisted that he send the entirety of his Two in the Box (everything!) back, and they would ship him another complete set once they received it.

Hey Nomake! Any news about the mod for the trap?

[One time]

Are you guys sure you have volume issues?

The trap is generally a whole lot more quiet than the wand or the pack (I compared a few traps, they all have the same volume). The only thing loud on the trap is the beeping.

[thedevilsrobot]

I need some help understanding if "No Ghost Mode" is working correctly on my trap, because my trap plays ghost audio every few moments regardless of which mode it is in.

I understand one of the dials switches between "Ghost Mode" (long trap opening) and "No Ghost Mode" (short trap opening). The trap opening aspect works correctly. However, regardless of whether the trap is in Ghost Mode or No Ghost Mode, ghost audio stills plays at regular intervals. This occurs both before and after any "successful trap" via use of the pedal.

Basically, no matter what I do, ghost audio plays at regular intervals. Is this the intended behaviour? I assumed "no ghost mode" meant ghost audio wouldn't play.

[hawkbatsquadron]

Pretty useful mod from Dirt Farmer Industries on ETSY: It's a great place to store your extra rods and caps when not in use, and there's even room for an extra set mounted on the side slots.
It bolts directly to the stand with the included screws and is non destructive and reverseable.




Sent from my Samsung Galaxy using a hacked pirate satellite in a decaying orbit

[edspengler]

Check out his pedal kit to add the Afterlife style feet without having to modify the pedal, it looks really cool.

[Nomake Wan]

Hey Nomake! Any news about the mod for the trap?

If there were, you would likely already know about it. If you want to be on the bleeding edge of GPStar news, please join our FB group! https://www.facebook.com/groups/gpstartechnologies

Basically, no matter what I do, ghost audio plays at regular intervals. Is this the intended behaviour? I assumed "no ghost mode" meant ghost audio wouldn't play.

Yep, that's by design. The mode change is just for changing the trap sequence itself, not the idle program.

[Turtuv]

Check out his pedal kit to add the Afterlife style feet without having to modify the pedal, it looks really cool.

link?

If there were, you would likely already know about it. If you want to be on the bleeding edge of GPStar news, please join our FB group! https://www.facebook.com/groups/gpstartechnologies

thank you! do you have a ETA pheraps??

[Nomake Wan]

thank you! do you have a ETA pheraps??

We do not. Or I suppose to be more precise, "When it's finished." For an even more detailed answer as to why there is no ETA, you could look at the development process to see where in the timeline we are:

1. Reverse engineer original components, identify space constraints and I/O requirements.
2. Perform bench tests of original peripherals to confirm control loops. <--WE ARE HERE
3. Select microcontroller which satisfies I/O requirements set out in step 1 and control methodology from step 2.
4. Create proof-of-concept code for dev board using microcontroller selected in step 3. Confirm functionality is as expected.
5. Design hardware board to satisfy constraints identified in step 1 using microcontroller from step 3.
6. Confirm prototype batch fitment and functionality. Design peripheral mounts as necessary.
7. Refine software for initial release. Create documentation for end user installation.
8. Mass production run.
9. Distribution.
10. Post-release long-term support.

These steps don't take a fixed amount of time each, and sometimes steps can overlap a bit. But the point is you're asking about step 9 and we're on step 2. It will be a while, so enjoy your gear for now and feel free to hang out in the GPStar FB group if you want work-in-progress sneak peeks as they become available.

[zeta otaku]

thank you! do you have a ETA pheraps??

We do not. Or I suppose to be more precise, "When it's finished." For an even more detailed answer as to why there is no ETA, you could look at the development process to see where in the timeline we are:

1. Reverse engineer original components, identify space constraints and I/O requirements.
2. Perform bench tests of original peripherals to confirm control loops. <--WE ARE HERE
3. Select microcontroller which satisfies I/O requirements set out in step 1 and control methodology from step 2.
4. Create proof-of-concept code for dev board using microcontroller selected in step 3. Confirm functionality is as expected.
5. Design hardware board to satisfy constraints identified in step 1 using microcontroller from step 3.
6. Confirm prototype batch fitment and functionality. Design peripheral mounts as necessary.
7. Refine software for initial release. Create documentation for end user installation.
8. Mass production run.
9. Distribution.
10. Post-release long-term support.

These steps don't take a fixed amount of time each, and sometimes steps can overlap a bit. But the point is you're asking about step 9 and we're on step 2. It will be a while, so enjoy your gear for now and feel free to hang out in the GPStar FB group if you want work-in-progress sneak peeks as they become available.

I am SO HYPED for this trap kit. Thanks for the breakdown on your development process, really helps put things in perspective.

[Ryusui]

thank you! do you have a ETA pheraps??

We do not. Or I suppose to be more precise, "When it's finished." For an even more detailed answer as to why there is no ETA, you could look at the development process to see where in the timeline we are:

1. Reverse engineer original components, identify space constraints and I/O requirements.
2. Perform bench tests of original peripherals to confirm control loops. <--WE ARE HERE
3. Select microcontroller which satisfies I/O requirements set out in step 1 and control methodology from step 2.
4. Create proof-of-concept code for dev board using microcontroller selected in step 3. Confirm functionality is as expected.
5. Design hardware board to satisfy constraints identified in step 1 using microcontroller from step 3.
6. Confirm prototype batch fitment and functionality. Design peripheral mounts as necessary.
7. Refine software for initial release. Create documentation for end user installation.
8. Mass production run.
9. Distribution.
10. Post-release long-term support.

These steps don't take a fixed amount of time each, and sometimes steps can overlap a bit. But the point is you're asking about step 9 and we're on step 2. It will be a while, so enjoy your gear for now and feel free to hang out in the GPStar FB group if you want work-in-progress sneak peeks as they become available.

You and your team are a treasure for this community. Thank you so much for your work!

[Turtuv]

thank you! do you have a ETA pheraps??

We do not. Or I suppose to be more precise, "When it's finished." For an even more detailed answer as to why there is no ETA, you could look at the development process to see where in the timeline we are:

1. Reverse engineer original components, identify space constraints and I/O requirements.
2. Perform bench tests of original peripherals to confirm control loops. <--WE ARE HERE
3. Select microcontroller which satisfies I/O requirements set out in step 1 and control methodology from step 2.
4. Create proof-of-concept code for dev board using microcontroller selected in step 3. Confirm functionality is as expected.
5. Design hardware board to satisfy constraints identified in step 1 using microcontroller from step 3.
6. Confirm prototype batch fitment and functionality. Design peripheral mounts as necessary.
7. Refine software for initial release. Create documentation for end user installation.
8. Mass production run.
9. Distribution.
10. Post-release long-term support.

These steps don't take a fixed amount of time each, and sometimes steps can overlap a bit. But the point is you're asking about step 9 and we're on step 2. It will be a while, so enjoy your gear for now and feel free to hang out in the GPStar FB group if you want work-in-progress sneak peeks as they become available.

thank you. i didn't meant to make any rush, sorry if it sounded like that. i'm just excited to install the kit and enjoy the trap fully.

[Broccoli]

I got my replacement trap and the sound is working great!

However, they originally asked for the belt holster to be sent back as well. I did so. They didn't send it back to me. Now, I have no belt holster.

I guess i am calling them on Monday to get this fixed.

[Giangieto]

I told them about my problem with low audio and they only told me if I wanted to return the product..but what problem did you have?

[Broccoli]

I told them about my problem with low audio and they only told me if I wanted to return the product..but what problem did you have?

Low audio issue.

[Nomake Wan]

I wonder if Charlesworth's upcoming speaker fix would solve the problems for people experiencing the "low audio" problem? In fact I wonder what the true culprit of that issue even is.

[Giangieto]

I wrote to Hasbro about my problem and they advised me to change batteries or return my item without having a replacement.

[Broccoli]

I wonder if Charlesworth's upcoming speaker fix would solve the problems for people experiencing the "low audio" problem? In fact I wonder what the true culprit of that issue even is.

I was wondering if somebody in the community would make an upgraded speaker. However, as collectors we shouldn't have to rely on someone else fixing something that should have been done correctly in the first place.

I wrote to Hasbro about my problem and they advised me to change batteries or return my item without having a replacement.

That is odd that they wouldn't offer a replacement/exchange of some kind, but if go back through this thread, you see that Hasbro has been giving different responses to different people. The customer service has been inconsistent at best.

[Nomake Wan]

Apparently the Charlesworth design is not just a replacement speaker but some sort of system. For a very, very short time he offered a different speaker but quickly took it off of his store. The latest item he showed off in a video demonstration is a replacement for that, but the way he described it made it seem like there was more to it.

As someone who is helping with reverse-engineering efforts, I can say that merely replacing a speaker--or even using an amplifier--is not going to get you good quality audio. Loud audio sure, but not good quality audio. The sounds on the Hasbro trap are bitbanged via PWM, similar to how you would generate sound using a cheap Arduino board. While it's awesome that Hasbro provided the raw PWM signals as pins on the board--and this is why I think Charlesworth is doing more than just a speaker--these are still really choppy waveforms. If anything, the poor quality speaker on the stock trap is helping to mask the poor audio signal quality.

[One time]

It's weird. I have a few of these Haslab traps and the sound volume and quality is very similar in all of them. There is a (perceived) difference between the ghost sounds and the "beeping" though. On one the Ghost sounds are a bit lower (I'd say between 2-5%) than the others. (barely noticeable unless you have a decibel meter).

The beeping levels seem the same (or I'm just imagining things).

On the whole, while the trap (ghost sounds) are a bit quieter than the Haslab proton pack (about 60% of the pack I would say in terms of volume) they are not totally quiet. You can clearly hear the ghost sounds from the trap in a quiet room. On all of my Haslab traps it's the same. I suppose the speaker is smaller in the Haslab traps as opposed to the pack, so it makes sense.

[Giangieto]

I wonder if Charlesworth's upcoming speaker fix would solve the problems for people experiencing the "low audio" problem? In fact I wonder what the true culprit of that issue even is.

I was wondering if somebody in the community would make an upgraded speaker. However, as collectors we shouldn't have to rely on someone else fixing something that should have been done correctly in the first place.

I wrote to Hasbro about my problem and they advised me to change batteries or return my item without having a replacement.

That is odd that they wouldn't offer a replacement/exchange of some kind, but if go back through this thread, you see that Hasbro has been giving different responses to different people. The customer service has been inconsistent at best.

Hasbro basically told me that they couldn't do anything about it and were sorry for my audio problem.

[One time]

I wouldn't worry too much about it in that case. I've done some mods to the Haslab trap that I'll post soon.

It's very easy to take apart (if you use a very thin and long screwdriver you can get into the "plugs" and unscrew the screws without taking the plugs off). The boards and speaker are so very easy to replace. You'll have a trap that's way louder than the normal stock ones people have if you download some parts off etsy.

And the brighter hat lights and the flat switch are a must anyway.

All relatively easy to do.