|
Post by rt198p on Jan 19, 2024 16:51:26 GMT
|
|
stuff
Full Member
1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
Posts: 231
|
Post by stuff on Jan 19, 2024 16:59:26 GMT
Might be a computer type issue. Are you downloading the image to the usb or the hard drive to the machine? "it will download it and say remove usb" is kind of vague.
If the chairside is saved to the USB and your system is not set to use the USB as a boot drive then you have a no go situation as the machine does not know where to look and loads default. BIOS settings would need to be changed.
Ours has to be installed from our network and thusly i had to change the bios settings on the computer side of the machine to look on the network to boot up. Otherwise it goes to default linux
You may also need someone specific to your company to give you instructions on how they have this setup to do.
|
|
phillipashleyludlow
Full Member
01001000 01101001 00100000 01010011 01110100 01110101 01100110 01100110 00101110
Posts: 151
|
Post by phillipashleyludlow on Jan 19, 2024 17:33:15 GMT
I'd allow your system to boot up until you get to the treatment selection screen, fn over to the chairside and press cntl, fn,z, when it starts to boot just keep taping Del untill it loads the bios settings menu, under advanced settings your bio's boot menu should look like this: once done save and exit, system should reboot, have USB already inserted at this point *For Fresenius Machines* If you are useing a Gen 1 (32 bit 6.0.56 Chairside image), this is what your boot menu should look like: If you are useing a Gen 2/3 ( 64bit 6.17.17 image) , this is what your boot menu should look like: if it shows the default 7.0.XX usb, your most likely not connecting to the USB correctly, or you have the wrong version.
see my updated post below ----v
|
|
|
Post by Guest on Mar 6, 2024 16:13:18 GMT
Did you ever resolve this issue? I'm having the same problem. User-Phillip; the V.6.17.17 Image downloads to the Machine, with the status reaching 100%, and confirming Completed, but upon rebooting the V7.0.2 shows and goes to the Desktop screen. If anyone has resolved this, please reply with solution.
|
|
phillipashleyludlow
Full Member
01001000 01101001 00100000 01010011 01110100 01110101 01100110 01100110 00101110
Posts: 151
|
Post by phillipashleyludlow on Mar 6, 2024 17:33:56 GMT
@guest are you downloading the image via TCP/IP update or usb? are you sure you have the correct software for the UI board you are useing? the easiest way to identify them is to pull the card cage and check useing this picture as a guide: Another issue that sometimes creeps up is that while the CDX 3 module has 4GB or RAM memory, when booting from a USB memory stick to install an image, only 1.9GB of memory is reported to the installer. This will cause the installer software to fail. All that is required is a simple change in the 2008T BIOS settings. To make the proper setting, perform the following steps: 1. Power on the 2008T machine 2. Using the blue key on the keyboard select the CDX screen 3. As soon as the America Megatrends (AMI) screen appears the <Del> key to enter the BIOS setup. 4. The main BIOS screen appears 6. Using the right arrow key, highlight “Chipset” 7. The line for “North Bridge” should already be highlighted. A. If it is not, use the up and down arrow keys to highlight “North Bridge” 8. Once highlighted, press the <Enter> key. 9. The North Bridge configuration screen will appear. (continued in next post)
|
|
phillipashleyludlow
Full Member
01001000 01101001 00100000 01010011 01110100 01110101 01100110 01100110 00101110
Posts: 151
|
Post by phillipashleyludlow on Mar 6, 2024 17:41:36 GMT
(Continued From The Last Post) 10. At the bottom left of this page is the setting ”Max TOLUD” A. The default setting is 2GB 11. Using the up and down arrow keys, highlight this setting. 12. Press the <Enter> key. 13. A popup menu will appear showing several values for this parameter. 13. Use the up and down arrow keys to highlight the 2.75GB settings 14. Press the <Enter> key 15. The North Bridge configuration page will re-appear 16. Note that the parameter for “Max TOLUD” is now set for 2.75GB 17. Press the <Esc> key once 18. The Chipset configuration page will return 19. Use the right arrow key to highlight “Save & Exit” 20. The “Save & Exit” screen will appear. 21. The “Save Changes and Exit” should be highlighted Use the up and down arrow keys to highlight it, if it is needed 22. Press the <Enter> key 23. The “Save configuration and exit” prompt will appear. 24. Verify that “Yes” is highlighted Use the left and right arrow keys to highlight, it if needed. 25. Press the <Enter> key 26. The machine will save the changes and reboot itself. Ensure USB is plugged into the back of the machine prior to this, and it should bring up the "Install Fresenius Image" page. continue installation.
|
|
|
Post by ThereAreSomeWhoCallMeTim on Mar 6, 2024 19:53:04 GMT
Just an issue that I've had before with trying to re-image machines. For some reason after a few months, it seems like the image on my USB will go bad (corrupted). I've never had it with a new board, but with existing ones. If I try to re-image the machine and it doesn't work I'll typically do what phillipashleyludlow suggested. Ie checking the bios, making sure all the setting are okay and determining which board and image to use. If that doesn't work, I will download the image from known good machine. (the little disk with a USB icon on the bottom row) This will require wired internet access. The time it takes depends on how good your internet is as well. One of my clinics it takes around 20 min to download the image my other clinic it takes over 4 hours. I will also just overwrite my current USB with the new image instead of trying to grab a new USB each time.
|
|
|
Post by Guest on Mar 8, 2024 11:36:27 GMT
The Board in question is brand new, Gen 3. After my initial imaging attempt with my on hand V.6.17.17 USB Stick, I made another Stick, thinking the image I had was corrupted. Using a brand new USB (unopened package), the Image was copied from a known good Machine, while on a Wired Connection. Again, I "Installed Fresenius Image" to the problem Machine and 100% was reached, showing Successful (Remove Stick/ Reboot Machine). Upon reboot, V.7.0.2 still shows, and Desktop screen loads, this happens after a Factory Reset as well. I checked the Bios, and all Settings are Correct. I only Post questions on this Forum as an absolute last resort, when I've done everything that I even think may fix my problem. As much as I appreciate the time taken to try to help me out, I was hoping that someone who's seen this specific issue, and resolved it could tell me how they did so.
|
|
phillipashleyludlow
Full Member
01001000 01101001 00100000 01010011 01110100 01110101 01100110 01100110 00101110
Posts: 151
|
Post by phillipashleyludlow on Mar 11, 2024 16:28:34 GMT
@guest if you work for big f, id reach out to ryan coogan to get fresenius provided tuumbdrives with the installer on it. iirc there is a knwn issue when createing thumbdrives that it doesnt allot swap space on the iso, which can lead to issues. there really isnt a whole lot of ways the installer can go bad.
|
|
|
Post by Biomed1 on Mar 12, 2024 1:49:59 GMT
What you can do in install the older version of chairside and then let the system update to current version on its own. Just make sure the pct is aware and to press update button when the window pops out.
|
|
phillipashleyludlow
Full Member
01001000 01101001 00100000 01010011 01110100 01110101 01100110 01100110 00101110
Posts: 151
|
Post by phillipashleyludlow on Mar 12, 2024 20:32:31 GMT
What you can do in install the older version of chairside and then let the system update to current version on its own. Just make sure the pct is aware and to press update button when the window pops out. @biomed 1 actually there is a company wide project to stop doing exactly this thing. "This message is being sent via bcc to all FKC RTOMs, ATOMs, and SDTs" If you have any questions or issues with your information in the report, please reach out to your manager. FYI - DTI is building a patch for some of the issues we are facing that will be implemented as soon as it is ready. If you have checked your machines and all is good, there is nothing to do but wait. ***This report is automatically generated weekly (Mondays). Any changes you make will not reflect on the report until the Monday following your changes*** All, we have opened visibility to an additional column in order to address a specific problem with Chairside. Column Q will be available to you starting with the attached report. That data field is "Image" and details the version of Chairside software running on each 2008T machine reporting in. The specific problem identified is that the number of machines showing 5.0.376 as current version is increasing over time where it should be decreasing and eventually disappearing. A few weeks ago, it was less than 100 and it is now approaching two hundred. The only way that can occur is if someone is manually sticking the machine with a 5.0.376 USB and downgrading the software version and attempting to upgrade it, which it cannot. There are two things that need to happen: 1. Please collect any 5.0.376 sticks in the field. We need to eliminate the possibility of having the wrong software reloaded and downgrading a machine. a. The attached PDF Guide has the instructions for creating USB sticks for current versions, as well as identifying the most current versions of Chairside in the field. i. 32 bit machines should be on 6.0.62 ii. 64 bit machines should be on 6.17.17 b. If for some reason there is a problem with creating sticks, reach out to Ryan Coogan and he can send some out. 2. Identify any machines in your areas of operation running 5.0.376. Filter column Q to just that version number to review. Update the software via USB drive to the current version. a. Really, you could/should update anything beginning with 5.x but the specific problem here is that 5.0.376 is increasing where the others are not current but also not going up. b. Discuss the correct version with your BioMed’s in affected locations to assure compliance with Step 1. c. Note also that one of the problems with versions beginning with 5 is that the upgrader no longer recognizes those versions and will not schedule an auto upgrade to the current version. It must be done manually. d. Document the update in TMS. Thanks in advance for looking into this and getting it corrected.
|
|
|
Post by Biomed1 on Mar 13, 2024 4:19:03 GMT
phillipashleyludlow, I called help desk and they instructed me to do it this way until it gets figured it out.
|
|
phillipashleyludlow
Full Member
01001000 01101001 00100000 01010011 01110100 01110101 01100110 01100110 00101110
Posts: 151
|
Post by phillipashleyludlow on Mar 13, 2024 18:22:13 GMT
@biomed1 welp, best of luck to ya. im not sure who at the helpdesk would recomend that, but it isnt what was put out by DTI, and thats who i go by. *shrugs*
|
|
|
Post by Biomed1 on Mar 14, 2024 2:46:26 GMT
Thank you. It is all good info as we just want it to work and to make life easier for the Clinical staff.
|
|