Subscribe now. Google coming soon.
This was released today. Thanks to ispsupplies.com for forwarding this over.
Announcement and updates on Nova 436
Below is an announcement recently posted by Baicells regarding reboot issues with the Nova 436 units:
As you are aware, our Nova 436 units have been experiencing reboot issues in the US market, with approximately 30% of the units affected. Our engineering teams have spent a significant time investigating, debugging, and analyzing both the hardware and software in the unit. We truly appreciate our customers patience and help throughout this process. Today, I am happy to provide an update to all of you.
We have identified the root cause of these issues to be related to the manufacturing and assembly process of the units, which impacted the quality and reliability of the unit, especially the three batches that were shipped to our US market. With these lessons learned, we will continue to take extra precautions to ensure we spend more time working with our manufacturing partners on quality assurance details for any future products.
As part of our review of these issues, we have decided to make the decision to discontinue sales of the current Nova 436.This will allow us to reallocate resources required for optimizing the supply chain process resulting in production of a more reliable product. As part of this process, we have been actively developing a new 436 version eNB, and are targeting a release date to be the next 90-120 days. Further news and details of the new eNB model will be shared when appropriate.
For any current Nova 436 eNBs which are exhibiting intermittent reboots, we are offering a 2-for-1 trade-in option. In exchange for each Nova 436, we will ship two Nova 233 Gen2 eNBs. For those who are not experiencing any reboot issues, you will have the opportunity to trade in for the next generation eNB once released.
To initiate the trade in, please send an email to email@example.com with the subject “Nova 436 Trade-In Request” and provide your company name, address, phone number, and eNB serial number. A Baicells sales representative will reach out to handle the logistics of the exchange.
My niece Chloe has kicked off her Girl Scout cookie sales for this year. If any of you out there would like to order some cookies please use the link below. Send some boxes to a client or keep them all for yourself.
I recently was able to get a pair of Skullerz Loki glasses from toweroneinc. You can pick up your own pair at https://toweroneinc.com/collections/clothing/products/skullerz-loki-safety-glasses-goggles
So why are these cool? First of all they are a google style. A good friend of mine Michael Pelsor figures out a few years ago if you keep your eyeballs warm in the winter your whole body thinks it’s warmer than it really is. These glasses fit around your eyes like a ski google, without the bulk.
Secondly, these glasses have a headband you can swap out the temple pieces with a stretchable headband so they stay on your head.
I have always been a firm believer in re-evaluating yourself on a regular basis. Take a look at yourself, your behaviors, and your quirks. By doing this, you can uncover weaknesses you. Red to work on, but also build on your strengths.
Case in point. I am in the process of rolling out wiki software for many clients. This software deployment will be a cookie cutter rollout, with customizations for each client after the initial implementation. I am behind on this for one big reason. Fear. Now, this is not Michael Meyers standing over your bed fear. It’s a fear of choosing the wrong platform. I have evaluated several wiki packages and talked to several people deploying each of them. Like most things, they have strengths and weaknesses. The fear breeds indecision. Is there something out there which I haven’t found that is better? Is there a better way or a way I haven’t thought of to accomplish what I am trying? The answer to all of these is probably yes.
How do you not fall into the trap of indecision? Couple of things you can do.
1. Before anything like this sit-down and write out the problem you are trying to solve. In my case with the wikis, I needed something to keep track of not only documentation but the odds and ends notes.
2. Write down what would help solve the issue. In my case an online repository of information.
3. Create a list of ways to solve this problem. This step may involve research. What are the software packages out there to address my issue? Are we utilizing anything today which could resolve this issue?
3. Once you have done some research formulate the must needed features in your solution. From there prioritize them.
4. Many people start to break down during this stage. Whether it is getting overwhelmed from the sheer amount of choices or thinking every feature is needed. The decision process begins to grind to a halt rather quickly. How do you overcome this? First, be realistic, how many of the features do you really need to accomplish your goal? Out of the features left, what does it take to implement them? How many times have you deployed a software tool and are only utilizing a fraction of the tools available? This happens quite a bit.
5.Set a hard time to make a decision. Tell yourself you have ten business days to research and come up with the solution. Once you have made the decision, have a rollout plan in place. This plan should include a timeline of start and finish. This way you don’t start to second guess yourself and drag your feet even more.
This method is not a foolproof way, but it will get you to implement more things than you are now.